Calendar identity checks for real estate teams

The decision to make first

An integration may connect to a valid calendar that belongs to the wrong agent or represents internal time rather than public appointment availability. Verify calendar identity and its intended appointment purpose before testing availability or enabling any booking action.

What the handoff should contain

Record account owner, calendar name and ID, timezone, permitted appointment type, staff visibility and the person approving public use.

Suggested wording to approve

Example wording: “This workflow can use only the calendar approved for this appointment type. Listing access and other agent schedules remain separate checks.”

Test the difficult case

Test two calendars with similar names and confirm that a fictional appointment appears only in the intended schedule with the right owner. Do not assume the first calendar returned by a provider is the correct one or that an agent’s personal free time is available for showings.

Worked example

Fictional example: Two calendars have similar names, one for internal agent tasks and one for approved consultations. A test appointment must appear in the intended consultation calendar with the right timezone and owner. Successfully logging into the provider or seeing free time in the internal calendar does not establish permission to offer those slots publicly.

Review it in operation

Review calendar ownership after staff changes and retest permissions before relying on a connection that previously worked.

Check before you launch

• Verify calendar identity and its intended appointment purpose before testing availability or enabling any booking action.
• Record account owner, calendar name and ID, timezone, permitted appointment type, staff visibility and the person approving public use.
• Test two calendars with similar names and confirm that a fictional appointment appears only in the intended schedule with the right owner.
• Review calendar ownership after staff changes and retest permissions before relying on a connection that previously worked.

Related guides