Start real estate automation with one connected job: take a property inquiry, answer from checked listing facts, offer an eligible tour, and give the assigned real estate agent the full history and next task.
The inputs are simple: the buyer's question, a listing ID, approved property facts, the agent's calendar, and an existing contact record if there is one. The useful output is a correct answer or human handoff, followed by an accurate booking and follow-up record. A person still checks property status, access, advice, and the tour outcome.
AI can help interpret varied questions and draft replies. Calendar bookings and CRM updates often work better as fixed rules based on confirmed events. You do not need three autonomous agents to connect three tools.
This guide covers that inquiry-to-tour workflow. It does not cover tenant screening, transaction management, or every part of running a brokerage. Provider instructions were checked on 5 October 2026. Cedar Lane Realty, buyer Maya, listing H-204, and all messages below are fictional examples, not measured customer results.
1. Define the pilot before choosing a tool
Imagine Maya asks at 9:02 p.m.: “Is H-204 still available? Could I see it after work?”
A fast reply helps only if the next morning's CRM record shows her question, the facts used, the booking state, and who must act. Otherwise, the agent may send a second booking link or arrive without checking the property.
Start with one listing, one intake channel, one assigned agent, and one tour type. Write a brief the team can use:
Scroll sideways to see all columns.
| Decision | Illustrative pilot |
|---|---|
| Intake | Website form for listing H-204 |
| Reply source | Approved listing record and brokerage FAQ |
| Automation may do | Draft a factual reply, share an approved tour link, and record confirmed events |
| Human must check | Unclear status, price, showing access, advice, and unusual requests |
| Live tour | Video walkthrough hosted by the assigned real estate agent |
| Record system | Existing customer relationship management system, or CRM |
| Handoff owner | Named agent; office coordinator covers unassigned requests |
| After-hours promise | State actual office hours and how follow-up will arrive |
| Pause rule | Stop the affected flow after a wrong property fact, lost handoff, or booking linked to the wrong person |
Replace the roles and rules with what your office can deliver. Agree when staff will check the exception queue. Do not promise an instant human response outside their coverage.
Begin with a person approving every property reply. Allow automatic replies only for questions whose sources and failure paths you have tested.
Choose the kind of tour explicitly
Scroll sideways to see all columns.
| Tour type | What the buyer receives | What you record |
|---|---|---|
| Recorded or self-serve 3D tour | Approved viewing link | Link shared |
| Live video walkthrough | A meeting with an agent and a join link | Booking plus property and host checks |
| In-person showing | A confirmed visit with separate access arrangements | Booking plus showing authorization |
Sending a recording does not book a meeting. An open calendar slot does not grant access to a property. Keep these differences in the message and the CRM.
In this article, AI assistant means software. Assigned agent means the real estate professional responsible for the inquiry.
2. Decide which system owns each fact
The listing source owns property facts. The scheduling tool owns the booked time. The CRM holds contact history and follow-up work. A reply should not become a new source of truth just because the AI wrote it confidently.
Scroll sideways to see all columns.
| Information | Approved source | If it cannot be checked |
|---|---|---|
| Status, price, and features | Listing system or the assigned agent's approved record | Explain the gap and ask the agent to confirm |
| Recorded tour URL | Approved listing page | Omit an unverified or broken link |
| Permission to host a live tour | Assigned agent and showing rules | Offer human follow-up |
| Free time | Connected calendar and scheduling rules | Do not confirm a slot |
| Contact and inquiry history | CRM and original submission | Hold an unclear match for review |
Store the time of the last successful check. A failed refresh must not make an old fact look newly verified. Agree how old status or price data may be before a person must check it. That limit depends on your brokerage and data source; it is not a universal number.
If you cannot read a reliable current source, automate the acknowledgement and create an agent task. Keep the availability answer human-reviewed.
Check facts at two points: before answering and before offering a live tour. If the booking happens later, the agent must review current status and access again before the walkthrough. A home can be listed as active without being available for the requested showing.
For U.S. REALTORS®, Article 12 of the 2026 NAR Code of Ethics requires truthful communications and advertising. Standard of Practice 12-8 addresses keeping website information current. A timestamp helps explain the check; it does not excuse knowingly sharing outdated information.
3. Capture the question and send a useful reply
Use one website form or approved inbox for the first pilot. Capture:
- A unique inquiry reference and the listing ID.
- Name and reply address.
- The original question, source channel, and arrival time.
- Tour type and preferred timing, if the buyer gives them.
- Contact preference and any separate marketing permission.
Keep the original wording. “Interested buyer” loses Maya's two actual questions: availability and an after-work tour.
A HubSpot form can capture information into contact properties. Test an existing contact as well as a new one. Keep a separate dated inquiry activity so a later property question does not erase the earlier one.
When the listing check succeeds
Suppose the approved record returns active status, the agent allows video tours, and a tested booking page has suitable slots. An illustrative AI reply is:
Hi Maya, I'm Cedar Lane's AI assistant. Our record showed H-204 as active when checked on 5 October at 9:02 p.m. Eastern Time. The agent will confirm current status and showing access before the tour. You can choose a time for a live video walkthrough using the booking link below. If you would prefer to speak with the agent first, reply here.
Attach the real, tested booking link. Sending it means tour offered, not tour booked.
When the check fails
After a handoff task has been successfully created, the reply can say:
Hi Maya, I'm Cedar Lane's AI assistant. I can't confirm H-204's current status. Your question and after-work preference are now with our office for the assigned agent to review. The office will follow up through this email thread during its published opening hours.
Use actual hours and a reply route the office monitors. If the task failed, do not claim the agent received it. Explain the failure and provide a verified office contact instead.
Set a narrow instruction for AI replies
Adapt this example to the tool's supported settings:
Work on one inquiry and listing ID at a time.
Use only approved property facts with a successful check time.
Answer the buyer's question first. Identify yourself as an AI assistant.
If a fact is missing, stale, or conflicting, say it needs confirmation.
Do not equate active listing status with permission to show the property.
Share a tour link only when that tour type is approved.
Confirm a booking only from a successful scheduling result.
Save the original question, sources used, reply, and handoff result.
Route requests for a person without another troubleshooting round.
Do not promise prices, terms, access, or actions beyond the approved facts.
An instruction cannot create a missing connection. Test that the assistant can retrieve the approved record and send the handoff, not just repeat these rules in a preview.
4. Separate a booked slot from a tour ready to happen
For a live video event, connect the assigned agent's calendar, set working hours and buffers, select the video location, and carry the listing ID into the booking. Use a required booking question if the tool cannot pass the ID from the inquiry.
Calendly checks connected calendars for availability. When a supported video account is connected and selected as the event location, it can generate video details for confirmations and calendar events. Video conferencing setup
The booking page should show duration, time zone, and cancel or reschedule options. Check the confirmation from the buyer's side. It should contain the full date, time, time zone, property, host, and working join link.
Use distinct states for your office's workflow:
Scroll sideways to see all columns.
| State | Evidence needed | Next job |
|---|---|---|
| Tour offered | Booking page was sent | Wait for the buyer's choice |
| Slot booked | Scheduling tool returned a booking reference and reserved the time | Verify the details and CRM link |
| Needs review | Video details, property eligibility, or host access are unresolved | Named person fixes the gap |
| Tour ready | Required meeting details and the agent's property checks are complete | Host prepares the walkthrough |
| Completed or no-show | Agent records what actually happened | Send the appropriate follow-up |
These labels are an example design, not default states in every tool. Record the reservation even if video details fail. Give the agent a repair task and tell the buyer that joining details still need attention.
Calendly's Zoom troubleshooting guide covers missing links and connection problems. Changing a setting is not proof that an existing invitation was repaired. Open the actual event and the buyer's notification before closing the task.
When listing status or showing permission changes, find its active bookings and alert their owners. Have the assigned agent tell each affected buyer what happens next. Keep a record of that contact. Do not let an old invitation stand as the only update.
5. Keep contacts, inquiries, and bookings separate
Maya can ask about two homes and reschedule one tour. A single contact status cannot describe all of that history.
Use four references:
Scroll sideways to see all columns.
| Reference | What it identifies |
|---|---|
| Contact ID | The person or existing CRM record |
| Inquiry ID | One submitted question or conversation |
| Listing ID | The property being discussed |
| Booking ID | The scheduling tool's reservation |
A small pilot can use a dated activity for the inquiry and a meeting activity for the tour. A custom database is not required. The records still need clear links.
Email is a possible matching key, not proof that two records belong to the same person. A shared address, typo, or changed address may need review. Avoid merging uncertain matches automatically.
Update records from events that actually happened
Scroll sideways to see all columns.
| Confirmed event | Record change | Guard against |
|---|---|---|
| Inquiry received | Add an inquiry linked to the contact and listing | Creating it twice on a retry |
| Reply sent | Save the message, fact-check time, and sent state | Treating a draft as delivered |
| Booking received | Link the booking, time zone, host, and current video details | Using the wrong contact or property |
| Booking changed | Update the current reservation and keep its history | Leaving the old slot active |
| Booking canceled | Mark it canceled and decide whether follow-up is needed | A late notice reopening it |
| Agent finishes the tour | Record attendance, open questions, and next task | Marking it completed because the time passed |
Process repeat notices once. If a booking notice arrives twice, find the existing booking before creating a second meeting or sending another confirmation.
Keep inquiry progress separate from tour status. Maya's availability question can still need an agent even after she reserves a slot. Booking should not erase it.
Check the limits of your integration
Calendly's HubSpot integration can create a contact and log meeting activity. For an existing contact, it adds the activity without changing contact details or owner. Custom answers appear on the activity; mapping them into contact properties can require HubSpot workflows.
Access depends on the Calendly plan and admin permissions. Calendly also documents duplicate meetings when overlapping calendar or Zoom syncs are enabled. Check which integration writes each event before adding another.
For this pilot, test the listing ID, owner assignment, cancellation, and reschedule history. A successful connection does not prove that these fields are mapped.
Recover when only part of the workflow succeeds
Suppose Maya books a slot, but the CRM update fails. Keep the real booking. Do not book her again to repair the missing record.
Send the failed update to a review queue with the booking reference and error. The office coordinator should:
- Confirm the reservation in the scheduler.
- Find the correct contact and inquiry.
- Retry the missing update or repair it manually.
- Check for duplicate activities and messages.
- Close the exception only after the CRM matches the current reservation.
A reschedule may have a replacement booking reference. For example, Calendly documents a canceled event and a newly created event, with references connecting the old and new invitee records. Reschedule event guide
Preserve that link to the earlier reservation and inquiry. If notifications arrive out of order, check the scheduler's current state. Do not let an old booking event reverse a later cancellation.
During the pilot, compare the next day's bookings with the CRM each working day. This catches missing updates that never reached the error queue. Give this check a named owner.
6. Give the agent a handoff they can use
The assigned agent should be able to prepare without searching three tools. A useful handoff might look like this:
Buyer: Maya | Listing: H-204 | Inquiry: INQ-081
Question: Is it still available? Can I see it after work?
Reservation: Thursday 8 October 2026, 5:30 p.m. America/New_York
Calendar and video details: Verified; booking reference attached
Listing: Active when checked 5 October, 9:02 p.m. America/New_York
Still needed: Agent confirms current status and showing access
Owner: Assigned Cedar Lane agent
Next task: Review property and access; update Maya if either changed
These dates and details are illustrative. Use the full date on the listing check so it cannot be mistaken for today's check. Show the buyer's local time clearly in their confirmation.
After the walkthrough, the agent records attendance and the facts actually discussed. AI can draft a follow-up from those notes for human approval:
Hi Maya, thanks for joining the H-204 tour. You asked about the roof's age. I'm checking the property documents and will send the confirmed answer. Please reply if there is another part of the home you would like to see.
The next CRM task is “Verify roof age and reply,” with an owner. It is not “Ready to make an offer” unless Maya said that. Keep buyer intent, property facts, and AI guesses separate.
7. Build with the tools you already have
One possible stack is a listing source, HubSpot intake and CRM, and Calendly with a supported video tool. This is an example, not a tested ranking or required purchase list.
Scroll sideways to see all columns.
| Need | Start with | Add more only when |
|---|---|---|
| Capture a listing question | Form or existing inbox | More channels can preserve the same IDs and history |
| Ask fixed questions and share a meeting link | Rule-based chatflow | Varied questions need more flexible interpretation |
| Answer open questions | Human-approved AI draft | Current facts and handoffs pass the pilot checks |
| Reserve a time | Scheduler and connected calendar | Team routing or other tour types need extra rules |
| Save events | Native integration plus specific field mappings | A required event or field is unsupported |
HubSpot's rule-based chatbot can ask questions, set properties, and use meeting actions. Available templates and actions depend on your subscription. Its AI customer agent answers from connected content and requires an eligible Professional or Enterprise subscription, an assigned seat, permissions, and HubSpot Credits for deployment.
Neither feature makes an old property feed current. Connecting a general help page does not establish that the assistant can check live listing status.
Before paying, budget for subscriptions, seats, AI usage, workflow access, setup, and ongoing review. Price the whole job, including the person maintaining the listing source and repairing missed updates.
Apply your brokerage's communication rules
For U.S. housing, use the same factual information and tour rules consistently. Do not use protected characteristics to exclude or steer buyers. HUD's Fair Housing Act overview explains the federal protection against housing discrimination.
HUD's 2024 digital advertising guidance discussed discrimination risks in automated ad delivery: original PDF, HUD archive copy. That document concerns advertising; it is not a complete rulebook for this inquiry workflow. HUD's April 2026 statement also explains that agents can share school and crime information equally and consistently.
Have the brokerage review the workflow for its location and services. Route advice, offer terms, access exceptions, and sensitive requests to the right professional. Keep inquiry replies separate from marketing enrolment, and record marketing permission separately. An inquiry alone should not trigger an unrelated campaign.
8. Test the buyer view and the office record together
Run sample inquiries before involving real buyers. For each case, inspect the reply, booking, CRM record, and receiving person's task.
Scroll sideways to see all columns.
| Pilot case | What must work |
|---|---|
| Approved facts and eligible tour | Correct answer, suitable link, linked inquiry |
| Stale status or price | No guessed fact; human review has an owner |
| Listing changes after booking | All affected booking owners receive a task to update buyers |
| Recorded tour requested | Approved link shared; no meeting falsely marked booked |
| Live booking succeeds | Contact, listing, reservation, time zone, and video details agree |
| Video link fails | Reservation retained; repair task created; accurate buyer message |
| Different buyer time zone | Full date and correct local time on the buyer's confirmation |
| Reschedule or cancellation | Current state preserved; no active old slot or duplicate reminder |
| Repeat inquiry | No duplicate contact or repeated automatic reply |
| Same person, second property | New inquiry keeps its own listing and tour history |
| Unclear contact match | Update waits for a person's review |
| Buyer requests a person | Handoff reaches the named recipient with the full question |
| Duplicate or late booking notice | No duplicate meeting or reversal of a cancellation |
| Booking succeeds; CRM write fails | Reservation survives and missing update is repaired once |
These are suggested checks, not proof that every future case will work. Start live with a small audience and a person checking every reply and booking. Expand after the team can recover from failures as well as complete the happy path.
Measure complete results
Track correct property answers out of reviewed answers, bookings with usable joining details out of booked video tours, and bookings linked to the right CRM contact, listing, and owner out of checked bookings. Include the sample size.
Also record missed handoffs, duplicate records, unresolved exceptions, and time spent fixing them. Compare the same channel and work before and after the pilot. Fast replies or more booked slots alone do not show that the full workflow improved.
Start with one inquiry and follow it all the way through
Choose one listing. Write its pilot brief, check its source, and assign the human owner. Send a test inquiry, book a tour, change it, and cancel it. Inspect the buyer messages and CRM after each step.
The first useful milestone is a buyer who knows the next step and an agent who can see the question, checked facts, current booking, and follow-up task in one place.