Property showing scheduling

Showing requests arrive while agents are driving, meeting clients, or already conducting a tour. The caller may name an address loosely, ask for a time that is not available, or need information before deciding whether to visit. A calendar entry alone is not enough: the team needs the correct property, contact details, requested time, and any access or representation questions that require a licensed person.

Property showing scheduling gives buyers and renters a consistent phone path to available appointments. The AI phone agent identifies the listing, collects the approved scheduling fields, checks connected availability, and books only when the configured rules allow it. The workflow applies across property businesses; the real estate industry page covers the broader set of real-estate call needs.

A concrete showing request

Consider a caller who found a listing online and wants to visit after work.

Agent: I can help request a showing. What is the property address or listing reference?

Caller: It is the two-bedroom listing on Harbor Avenue.

Agent: I found more than one active listing on that street. Can you give me the street number or the listing reference shown on the page?

Caller: I have the street number. I would like the latest available appointment tomorrow.

Agent: The connected calendar shows an eligible evening slot for that property. Before I book it, may I collect your name, phone number, email address, and whether you are already represented, using the questions set by the brokerage?

Caller: Yes. I also need step-free access.

Agent: I will record that request for confirmation rather than promise that the property is accessible. Would you like me to reserve the available slot while the team reviews the access question?

The agent resolves the ambiguous listing, uses real availability, and distinguishes booking from a property-specific assurance. If the caller wants to change an existing tour instead, route them to the rescheduling and cancellations flow.

How to configure it on ThunderPhone

Write the prompt around the brokerage’s actual showing rules. A practical outline is:

identify the listing by exact address or listing reference and ask a clarifying question when the match is ambiguous;
collect the contact and representation fields the business requires;
state only approved public listing information;
check availability for the correct property, tour type, and assigned staff member;
confirm the selected date, time, location, and contact details before writing the booking; and
escalate access needs, occupied-property questions, same-day exceptions, offer discussions, or anything requiring licensed judgment.

Connect Cal.com or Google Calendar for approved availability and booking actions. Keep separate calendars, event types, or rules where properties have different access windows. The agent should treat a failed calendar write as a failed booking, not tell the caller that an appointment exists. This is a narrower version of appointment scheduling by phone, with listing identification and property rules added.

Use HubSpot or Salesforce when the business wants the inquiry and appointment attached to a lead record. A custom listing or lead platform can be exposed through a limited REST action, and a remote Zapier MCP server can provide an approved workflow. Remote MCP servers are added by URL, synchronized for automatic tool discovery, and attached to agents; static HTTP headers are supported. Give the agent only the listing, availability, booking, and lead actions the call requires.

For downstream records, webhook endpoints can subscribe to call events and use separate secrets, HMAC-SHA256 request signatures, and exponential-backoff retries for non-blocking delivery. Capture the matched listing, requested and booked time, contact fields, representation answer, special request, booking result, and final disposition.

Connect the agent to the showing line. Inbound demo U.S. numbers are useful for testing but are inbound-only and not intended for production. If a high-intent or unusual request should reach an agent, configure a transfer target and fallback. On an eligible production number, warm transfer can place the caller on hold, privately brief the recipient, and connect after acceptance. If the recipient does not accept, the AI agent returns to the caller with the outcome. Demo numbers and browser calls support cold transfer only.

Test available and unavailable slots, ambiguous addresses, duplicate contacts, occupied listings, access requests, failed calendar writes, and unavailable human recipients. Graded scenarios should verify that the agent never invents a slot or treats a request as a confirmed appointment.

What to measure

Useful measures include:

listing-match success and clarification rate;
required contact-field completion;
requested showings that become confirmed bookings;
failed or duplicate booking attempts;
reschedule and cancellation rate;
special requests routed for human review;
transfer acceptance and fallback completion; and
reviewed calls with an inaccurate availability or property statement.

Track what happens after the call as well as call completion. A short call that creates the wrong appointment is worse than a longer call that clarifies the listing and time.

Honest limits

The agent cannot inspect a property, confirm an accommodation that is absent from approved data, evaluate a prospect, give legal or financial advice, or answer representation questions that require a licensed professional. It should not reveal private seller or occupant details, bypass showing instructions, invent availability, or imply that a calendar request is confirmed after a failed write. Staff should handle safety concerns, fair-housing-sensitive judgment, complex access needs, offer strategy, and disputed appointments.

Use a separate lead qualification call when the purpose is to assess fit rather than book a specific property. Define an explicit human handoff for every question the scheduling flow cannot safely resolve.

Create your ThunderPhone account to configure and test property showing scheduling.