A viewing slot can look available in the agent's calendar and still be impossible. The tenant may require notice, the owner may control the keys, and the agent may need travel time from another property. Coordinating these constraints is a suitable administrative workflow when the agency defines which participants are required and who verifies access. AI is optional: a clear record and deterministic scheduling rules often matter more than a conversational interface.
The proposed procedure here creates a coordinated viewing plan. It does not establish a right of entry or override a tenancy, building rule or agency policy. Those matters belong with the responsible people and the agency's approved process. The customer should receive a confirmed appointment only after the agent checks the complete arrangement.
Record each participant's constraint separately
Create a viewing request with a stable listing ID and property record. Name the buyer or prospective tenant, the assigned agent, the access coordinator and any other participant who must attend or approve. Do not assume the owner and access coordinator are the same person.
For each participant, record available windows, timezone, required notice and the source of the information. Keep unknown values explicit. Usually home on Fridays is not a confirmed Friday window. An agent's free calendar interval is not enough if they are travelling between branches or carrying out another task that was not represented in the calendar.
Access constraints should include the agreed notice, key or entry arrangement, building restrictions, pets or other relevant instructions supplied through the proper process. Collect only what the viewing coordinator needs. Do not distribute occupants' contact details or private notes to every prospective viewer.
Build feasible windows before asking anyone to confirm
Use the agreed viewing duration and any required setup or travel buffer. Compare full intervals rather than start times alone. A participant free at 14:00 may still be unable to attend a viewing that ends after their available window. Apply buffers under the agency's approved rule, not a model's guess about traffic.
Source: Microsoft Graph calendar resource lists calendar views, free/busy and meeting-time suggestions. These can supply scheduling information where permissions and calendar types support the operation. They do not establish property access or promise that a suggested meeting time meets all external constraints.
Choose a small number of proposed windows that satisfy the known requirements. If no common window exists, explain the conflict to the agent: for example, the access coordinator is available only after the agent's last accepted window. Do not send apparently available options that rely on a participant making an unrecorded exception.
Reusable coordinated viewing schedule
Use the following proposed record to move from request to confirmation. A hold is a temporary scheduling reservation under the agency's rules, not a promise to the customer.
| Stage | Record to keep | Gate for the next stage |
|---|---|---|
| Identify | Viewing request ID, listing ID, assigned agent and participants | Correct property and required roles confirmed |
| Collect constraints | Windows, timezone, notice, travel rule and access requirements | Missing constraints resolved or assigned for review |
| Propose | Candidate interval, duration, buffers and supporting availability | Full interval fits all known constraints |
| Hold | Hold ID, owner, expiry and calendars/resources affected | Hold can be respected by staff and integrations |
| Confirm participants | Reply or acceptance evidence for every required party | Agent verifies all necessary arrangements |
| Commit booking | Accepted appointment ID, interval and current record version | Definitive booking result is returned |
| Notify | Exact appointment details and approved access wording | Message matches the recorded appointment |
| Reconcile | Calendar, property task and participant state | No unaccounted hold or conflicting appointment remains |
Before sending confirmation, the agent checks:
- The listing is still eligible for the proposed viewing.
- Each required participant has accepted the exact date and time.
- The access coordinator has confirmed the appropriate arrangement through the agency's process.
- Travel, duration and resources still fit the current calendars.
- A stable appointment record exists and corresponds to the accepted slot.
- Earlier alternatives and expired holds are closed or clearly marked inactive.
If a required check is unknown, the customer-facing state remains proposed or being arranged. The completion check is one verified appointment or one assigned unresolved conflict, with every hold accounted for.
Understand tentative holds and competing changes
A proposed slot should not occupy calendars indefinitely. Record its owner and expiry under an agreed policy. Staff need to see whether the hold is still active and which request owns it. If the booking system cannot make other booking paths respect holds, use agent-assisted coordination rather than pretending exclusivity exists.
Source: OpenAI function calling distinguishes a model requesting a function from the application executing it. A booking request must still pass the application's availability, identity and permission checks. Asking a model to book the slot does not establish that the record was created successfully.
If the booking write times out, retain an uncertain state and check for the appointment using the stable operation reference. Do not release the hold and repeat the booking immediately. The first write may have succeeded. Similarly, a participant who changes availability after accepting creates a new coordination task; their earlier acceptance is not permission to choose another time automatically.
Walk through a shared window and an access conflict
Consider a hypothetical 30-minute viewing. The agent is free from 14:00 to 15:00, the tenant has agreed an access window from 14:15 to 15:00, and the buyer is available from 14:00 to 14:45. A proposed 14:15–14:45 viewing fits those intervals. Any required travel or setup buffer must also be checked. The agent verifies the arrangements, records the appointment and only then sends confirmation.
Now suppose the owner says any afternoon is fine but the tenant's availability is missing. The workflow records the owner's statement and an unresolved tenant constraint. It does not infer access from the owner's broad reply or use the agent's free time as a replacement. The agent contacts the proper coordinator and keeps the request unconfirmed.
A duplicate notification of the buyer's acceptance should return the existing decision for that offer. A new reply changing the buyer's available window should update the request history and invalidate the affected proposal. Matching text does not justify discarding a genuine change. Keep message identity and scheduling intent distinct.
If a manual booking consumes the agent's interval before confirmation, recheck the candidate and stop the confirmation. Offer another mutually accepted window through the usual process. Do not silently shorten the viewing or remove a travel buffer to force the old proposal to fit.
Assign unresolved coordination to a person
Every failed constraint needs a useful handover: which party is affected, what evidence is missing and who should resolve it. A task saying scheduling failed is less useful than one saying the tenant has not confirmed the proposed access window. Include the original reply and proposed interval without exposing unnecessary private material.
Source: n8n human review supports pausing selected agent tool actions for approval or denial. A team could use that mechanism before external confirmation. Its presence does not prove that the access and calendar controls are complete; those require implementation and verification in the agency's systems.
Pilot the procedure with staff-labelled synthetic requests before sending customer messages. Include no common window, unknown access, calendar permission failure, simultaneous manual booking and uncertain booking response. Check whether every case finishes in the expected confirmed or unresolved state. Assess effort and errors from the actual pilot, without assuming a time-saving result.
Questions about viewing coordination
Can we confirm once everyone appears free in a calendar?
No. Free time is only an availability input. The agent must verify the required access arrangement, resources, full interval and accepted appointment record. If the agency's calendars do not represent all relevant constraints, collect those separately instead of treating calendar availability as a complete answer.
What should happen when a tentative hold expires?
Close that hold according to the approved policy, retain its history and recheck the request before proposing another window. A late reply must not overwrite a later valid booking. Staff should resolve contested timing or delivery evidence while the workflow keeps the current slot ownership visible.
Should we send the tenant's details to the buyer to arrange access directly?
Only when the agency's approved process permits that sharing and the relevant people have agreed. The workflow can coordinate through the agent without distributing private contact information. An easier scheduling path is not sufficient reason to disclose additional occupant details or bypass the established access coordinator.
If your business needs help defining this process, explore AI agents for estate agencies, the wider AI automation services, and our custom-agent workflow guide. The agents and automation comparison and custom AI agent glossary explain the terms. To discuss your records and approval rules, get in touch.