Guides / AI in practice

Schedule a Bangkok property viewing without inventing availability

An empty calendar does not mean a condo can be viewed. Build the appointment around verified access and a real listing record, then distinguish a proposed time from a confirmed viewing.

By DLVX · 5 min read · Published 20 October 2026

Read the worked guideCheck the sources

An empty calendar is one check

  1. Listing

    Correct unit and current status.

  2. People

    Agent available with travel buffer.

  3. Access

    Permission and entry arrangement verified.

  4. Agreement

    Customer accepts exact slot before confirmation.

A teaching sequence. This diagram does not run an AI tool or connect to your business.
On this page

Four approvals hide inside one calendar slot

A fictional prospect sends an old listing screenshot and writes: “Can do tomorrow after 5. Is this still available? Need to move next month.” A reply of “See you at 5:30” is premature even if the agent's calendar looks empty. The property may no longer be available, the screenshot may identify the wrong unit, and someone still needs to arrange access.

Treat the viewing as a small coordination job. First establish the listing and intended unit. Then check current availability for the relevant move-in plan, permission to show it, and the calendars of the people needed for access. Finally obtain the prospect's agreement to a precise date and time. Those checks may happen quickly, but none follows automatically from the others.

This guide uses fictional records and names. It gives a workable scheduling pattern for a property team; it does not imply any named building permits a particular viewing process or that DLVX operates these records.

Turn the screenshot into a question, not a match

AI can read a listing reference or identify visible clues, but a similar photograph should not silently become a verified listing match. Buildings reuse layouts, advertisements get copied, and old images can remain in circulation. Record candidate matches separately from the confirmed property reference. Ask for the listing link or another identifier when the evidence doesn't distinguish units.

In the example, the screenshot suggests listing BKK-214 but contains no unit number. The current record says that listing has a pending offer. A second unit in the same building is available, but it has a different floor plan. The right draft explains that the original unit needs a status check and offers to send the second unit's details separately. Substituting the second unit and calling it “this one” damages trust before anyone arrives.

Resolve “tomorrow” against the timestamp of the customer's message and show the resulting calendar date in the reply. A colleague opening the queue after midnight shouldn't shift the viewing by a day. Ask for a move-in date if “next month” changes eligibility or availability. Don't turn that phrase into the first of the month.

What a calendar can and cannot prove

Google Calendar's official free/busy endpoint returns busy intervals and can return errors for individual calendars; it also allows a response timezone. Checked 20 October 2026. A missing or failed calendar lookup must not be interpreted as a free afternoon.

Even a successful empty interval says nothing about keys, tenant permission, building access or travel time. Put those constraints into the scheduling record explicitly. A viewing at 17:30 may need the agent available from 17:00 for travel and the access contact available at 17:20. Use your team's actual buffers rather than a universal Bangkok travel estimate. Rain, location and the preceding appointment can make a default buffer unsuitable.

A safe internal status might read: “Candidate: 21 October 2026, 17:30 Asia/Bangkok. Agent free with travel buffer. Access contact not confirmed. Prospect has not accepted this slot.” That is already useful. The customer draft can ask whether 17:30 would suit, while clearly saying the team is checking access before confirming.

Copy the viewing card

VIEWING REQUEST
Conversation reference and original timestamp:
Customer's exact date/time wording:
Resolved date, local time and timezone:
Listing reference and match evidence:
Unit availability source and checked time:
Move-in requirement:

REQUIRED CHECKS
Agent availability, including agreed travel buffer:
Property access permission and responsible contact:
Keys or entry arrangement:
Customer acceptance of exact proposed slot:
Current appointment record:

DRAFT RULE
If any required check is unknown, call the slot proposed.
Do not substitute a different unit without saying so.
Do not expose tenant or owner private contact information.

CONFIRMATION
Property reference:
Date and time:
Approved meeting point:
Agent contact route:
Access verified by and at:
Appointment record reference:

The prompt should return missing questions before a suggested reply. That order lets the coordinator catch a bad assumption without searching through polished prose. Keep the current status on the card even after generating a calendar invitation; creating an event is not equivalent to obtaining every participant's agreement.

A changed time should cancel the old intention

Imagine access becomes available at 18:00 and the prospect accepts. The earlier 17:30 proposal must become superseded. Otherwise an automatic reminder may send the wrong time, while the agent acts on the new one. Store one active appointment version linked to the conversation and keep the earlier proposal as history.

Recheck the needed resources immediately before committing the appointment, according to the team's booking process. If two coordinators can reserve the same agent simultaneously, a prompt cannot prevent the race. The system that owns scheduling needs a conflict control or a human final coordinator. If a calendar write times out, look for the intended event before retrying.

The confirmation message should include the exact property reference, date, local time and an approved meeting point. Don't send a tenant's private phone number because it happened to appear in the internal access note. If the prospect later cancels, update the appointment and notify the people whose access arrangements changed. A canceled customer reminder alone doesn't free everyone's schedule.

Review the awkward cases with an agent

A useful test set includes two units with the same photos, a calendar the integration cannot read, a tenant withdrawing access, a customer changing the day in a voice note, and two prospects asking for the same slot. Test an old screenshot after the advertised unit has gone. The expected output is often a precise clarification, not a booking.

Have the agent score whether the card saves coordination time and whether the eventual visit matches what the customer understood. Track incorrect confirmations separately from harmless wording edits. A low number of bot messages proves nothing about a successful viewing; the useful outcome is an appointment that can actually take place.

For a small agency, a shared sheet and one coordinator may outperform a connected assistant. Start there if access arrangements live in people's heads. Use AI to extract the request and draft the question once the process is legible. The broader DLVX workflow guide, checked 20 October 2026, covers that choice; this card makes the property-specific dependencies visible.

Sources and dates

Sources checked on 20 October 2026. Worked examples are teaching examples unless explicitly attributed. Provider documentation describes product behaviour; the operating recommendations are DLVX editorial judgement.

Have a workflow in mind? Talk through the job with DLVX.