A real estate chatbot should identify itself, answer only from current property information, ask two or three useful questions, then pass the full conversation to an agent when someone wants a viewing, valuation or advice. Give every visitor an easy human route. Test the notification and agent response, not merely the bot's final message.
The most expensive failure is a lead that looks captured in the chat window but reaches nobody. A bot can collect a name and contact detail perfectly while routing the transcript to an unmonitored inbox. Decide who owns each kind of enquiry before writing the greeting, and make the promised reply time match that person's actual cover.
Check the greeting against the visitor's real task
The opening should tell the visitor that they are speaking to an AI assistant and offer a small choice: ask about a property, arrange a viewing, request a valuation, or speak to an agent. An open text box can follow, but the choices give the conversation a useful shape. A greeting that says only “How can I help?” leaves a buyer to guess whether the bot knows live availability or can actually arrange a visit.
- Identify the assistant. Use plain wording such as “I'm the agency's AI assistant. I can collect your question and pass it to an agent.” Do not imply a human is typing.
- State the boundary. If the bot cannot confirm a viewing slot or make an offer, do not display buttons that promise either outcome.
- Keep the human exit visible. “Speak to an agent” should remain available after every question, including a failed answer.
- Match the page. On a listing page, carry the property reference into the chat. On a valuation page, begin with the seller's reason for contacting the firm.
Illustrative greeting for listing P-214: “Hello. I'm the AI assistant for this property team. Are you asking about P-214, looking for a viewing, or seeking something else? I can pass the conversation to an agent at any point.” If P-214 has been withdrawn, the bot must say its information may be out of date and offer an agent. It must not quietly substitute a different listing and describe it as equivalent.
Keep public listing facts in a reviewed source with an owner and an update routine. Price, availability, viewing arrangements and included features can change between the first visitor and the tenth. A bot that remembers a stale listing page is a poor source of truth. For the broader work of keeping bot answers tied to approved information, see training a chatbot on current FAQs and policies.
The Complete Excel Course with AI Integration
From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.
By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner
Buy nowAsk for intent before asking for contact details
Qualification means collecting enough information to route a conversation and make the first human reply useful. It does not mean making the visitor complete a long form in chat. Start with intent. A buyer asking for a viewing needs a different handover from a seller wanting an indicative valuation. A landlord's maintenance question should not be forced into either sales branch.
For a buyer, ask which property or property type they mean, whether they want a viewing or information, and their preferred contact route. Timing can be an optional fourth question. For a seller, ask whether they want a valuation appointment or an answer about the selling process, then ask what kind of property they own and their broad timing. Do not ask for sensitive financial documents, identity documents or a detailed household profile in the chat.
Example: a visitor says, “Does the flat in the listing have step-free access?” The bot should treat that as a property fact requiring a verified source, not as a cue to ask whether the visitor has a disability. If the listing does not state the access details, a safe answer is, “I can't confirm that from the current listing information. May I send this question and the listing reference to an agent?” This preserves the enquiry without guessing.
A visitor may refuse every optional question and still have a legitimate enquiry. Offer “Skip and ask an agent” after a qualification prompt. Distinguish a missing field from a negative answer in the handover record. Otherwise an agent may read a blank timing field as “not ready” and delay a reply that should have been immediate.
Record permission and the source of the enquiry
Before asking for a phone number or email address, explain what it will be used for: an agent's reply about this enquiry. If marketing messages are a separate choice, keep that choice separate. Do not treat the visitor's request for a viewing as permission to receive a newsletter. The precise legal wording depends on the firm's applicable requirements, so have a qualified adviser review the final notice and retention settings.
A useful lead record contains the page URL or listing reference, the visitor's own request, the questions answered, the contact channel they chose, the permission captured, the time and the assigned owner. Store the conversation link or transcript where the agent can access it. Do not silently copy the chat into several systems if nobody knows which record controls deletion or correction.
Illustrative before and after: the old alert reads “New chatbot lead: [first name], email supplied.” The improved alert reads “Viewing enquiry, listing P-214, available this week, prefers email; asked whether the second bedroom fits a desk; agent answer required; transcript attached.” The second alert gives the agent a reason to reply and a question to answer. It does not invent a score or declare the visitor “qualified”.
If you already have a site form and inbox, compare them with the bot. A chatbot is useful only if it captures context that your existing route loses or helps the visitor reach a person sooner. The general setup choices sit in adding a lead capture chatbot to a website; this checklist concentrates on property enquiries and their handover.
Write handover rules before writing clever answers
Map each intent to an owner, a backup and an acknowledgement. A viewing request for a specific listing can go to the listing team. A valuation request can go to the seller enquiry owner. A complaint, a request about an existing transaction, an accessibility question, an offer, or a question involving contractual terms should go straight to a human queue. The bot may collect context, but it should not negotiate, assess eligibility or promise a transaction outcome.
| Trigger | Bot's next action | Agent's first task |
|---|---|---|
| Viewing request with listing reference | Confirm preferred contact route and hand over the transcript | Check current availability and offer real times |
| Seller asks for valuation | Collect property type and broad timing, then route | Explain the appraisal process and book a conversation |
| Offer, price negotiation or contractual question | Stop giving advice and request human contact | Review the full wording before replying |
| Fact missing or listing information conflicts | Admit uncertainty and send the exact question | Verify the current record, then answer |
| Visitor says “person” or expresses frustration | End qualification and route immediately | Read the chat so the visitor need not repeat it |
Make the handover message honest. “I've passed this to the property team; they will reply through the contact route you chose” is appropriate only after a task or inbox record has actually been created. If the integration fails, the bot should show a fallback contact method or ask the visitor to try the site form. A cheerful success message on a failed transfer is worse than an obvious error.
Some chatbot builders offer question actions, conditional branches, meeting links and routing to team members. HubSpot's rule-based chatbot documentation, for example, says its team-member handover checks whether the chosen people are available before the conversation starts and shows an away message when they are not. The same page notes that this handover needs an assigned Sales or Service seat and that custom if/then conditions need a Professional or Enterprise subscription. So these are implementable patterns, but not every plan or product includes every action. Test the selected tool's actual subscription, seats, hours and fallback behaviour before promising an instant handover.
For a more general decision tree about when any customer bot should hand over, read the human handover tutorial. In property work, the trigger list should be shorter and stricter because a confident invented fact about a listing can send someone to the wrong viewing or misstate an offer.
Apply a fair housing screen to every branch
Property chat needs a specific guardrail against unequal treatment and steering. Do not ask about protected personal characteristics to decide which listings to show, which visitor receives an agent, or how quickly to reply. Avoid prompts that infer household composition, background or identity from a name, writing style or browsing history. Keep the same route to public listings and an agent available to comparable enquiries.
Fair housing rules treat steering as discrimination: restricting someone's choices by word or conduct, discouraging them from viewing a home, or directing them to a particular part of a neighbourhood because of a protected characteristic. A chatbot that sorts visitors can do the same thing quietly and at volume. One regulator withdrew its 2024 guidance on automated housing advertising in September 2025, but its withdrawal notice says conduct that breaks the statute remains subject to enforcement, so the withdrawal changes nothing about how a bot should treat visitors. A practical rule for a small firm is to route on the request, not the person. Listing reference, stated budget, required access features and desired move timing can help an agent understand an enquiry. They should not be transformed into an opaque score that quietly hides a visitor from the team.
Example of a prompt to reject: “Show family friendly areas to this couple and avoid areas that won't suit them.” It asks the bot to infer and steer. A better response is: “I can share the public listings that match the property features and price range you choose. Which features matter to you?” If the visitor asks about schools, transport or access, provide neutral, verifiable information on the same terms to anyone who asks, or pass the question to an agent.
Example of an agent audit: send two otherwise identical viewing enquiries with different names and compare the transcript, available choices, routing owner and response time. This does not prove legal compliance, but it reveals obvious differential treatment. Repeat the test after changing prompts, data sources or scoring rules. Ask a qualified property or legal adviser to review any screening or allocation process; this operational checklist is not a legal opinion.
Work through a six-agent team with actual numbers
Consider an illustrative six-agent property firm receiving 80 website chats in a month. Forty ask about a specific listing, 18 request a viewing, 12 ask about selling, and 10 ask something else. The team sets up four intent buttons and one common human exit. A listing page supplies its reference to the chat. The bot asks at most three questions before offering transfer. Those choices are design assumptions for this example, not industry averages.
The 18 viewing requests go to a shared viewing queue with a named duty agent and backup. The 12 seller enquiries go to a separate owner. The 10 “something else” chats remain in a monitored general queue; nobody deletes them as unqualified. During a two-week pilot, the team manually reviews all 80 chat records against the original visitor messages. Suppose 76 have the correct intent and four are misrouted: two maintenance requests were mistaken for viewing requests, one valuation question went to the general queue, and one visitor's “speak to someone” request stayed in the bot.
That gives 76 correctly routed chats out of 80, or 95% for this illustrative pilot. It is not a quality verdict. The team examines each of the four failures, changes the intent labels and makes “speak to someone” an immediate trigger. It then runs the same four messages again. A bot that classifies 80 of 80 after those fixes can still fail if its notification does not reach the duty agent, so the next test checks delivery and reply times separately.
For response timing, the firm sets an internal target of a first human action within 30 minutes during monitored hours. In the pilot, 24 chats request human help while the queue is staffed; 19 receive a human action inside the target. The measured result is 19 divided by 24, about 79%. The owner should investigate the five late cases before publishing a “reply in 30 minutes” promise. This is an illustrative operating target, not a recommended universal standard.
One of the late cases arrived when the duty agent's notification was muted. Another was assigned to a person on leave. Those are staffing and routing defects, not model accuracy defects. The firm adds a backup queue and a daily review of unassigned conversations. It tests the same scenario outside monitored hours and changes the bot's acknowledgement to give the next staffed period rather than pretending that someone is online.
Test the conversation as a visitor, then inspect the inbox
Write test messages in the language real visitors use. Include short and long messages, spelling errors, requests for a person, unavailable listings, ambiguous property references, and a question the bot cannot answer. Run each test in a private browsing session so an existing contact record does not supply hidden information. If the tool's preview creates test contacts or meetings, clean those up after inspecting the record.
- Open a live listing and ask for a viewing. Check that the correct reference appears in the agent record and that no time is described as booked until a booking exists.
- Ask a seller question from a listing page. Check that intent overrides page context and the record goes to the seller owner.
- Type “agent” at the first question, then again after two questions. Both should lead to the human route without making contact details compulsory.
- Ask about a withdrawn listing. Check whether the bot admits it needs verification and avoids presenting stale details as current.
- Disable the primary notification in a safe test environment. Confirm that a backup sees the conversation or that the visitor receives a truthful fallback.
- Send two equivalent enquiries with different personal cues and compare the options, queue and reply treatment.
A short sample output audit is useful too. Illustrative visitor message: “Can I view P-214 on Thursday, and is parking included?” Illustrative bot output: “Yes, Thursday at 3 is confirmed and parking is included.” If neither claim is tied to a live booking and reviewed listing fact, that answer fails. The corrected reply is: “I can pass your Thursday preference and parking question to an agent. I cannot confirm the slot or parking from the information I have.” Record the two claims as separate issues; fixing one does not fix the other.
Test on a narrow phone screen as well as a desktop. A fixed chat window that hides the human button, or a keyboard that covers the contact field, can turn a sound workflow into an abandoned lead. Check that a visitor can use the chat with a keyboard, read the disclosure and reach the same handover route without relying on a tiny icon. The broader customer chatbot launch test has additional channel and accessibility cases.
Inspect the handover each week, not only the chat count
Count four distinct outcomes: chats started, visitors who requested human contact, handovers delivered to an owner, and human replies made. A conversation should not count as a successful lead merely because the bot stored an email address. Review a sample of transcripts for wrong property facts, repeated questions, missing consent, unfair routing and answers that make unsupported promises. Keep examples of failures in a change log with the rule or data source that was corrected.
Illustrative weekly review: 20 chats started; nine asked for a viewing or valuation; eight created owner records; six received a human reply during monitored hours. The gap from nine to eight points to delivery. The gap from eight to six points to staffing or follow-up. Changing the greeting will not solve either gap until the owner finds the missing records and unreturned conversations.
When a chat ends without contact details, do not call it wasted. The visitor may have got a verified property answer and left satisfied. Conversely, a transcript with contact details but no clear question may require a gentle clarification, not a hard sales pitch. The useful measure is whether the conversation led to an appropriate answer or an owned human task.
The final launch check is simple: the bot says what it is; the questions help the agent; sensitive decisions stay with people; the transfer really arrives; and the visitor hears a truthful next step. If any of those fail, keep the bot in a small pilot and correct the process before sending every site visitor through it.
Questions before putting the property bot live
Should the bot ask for a budget before showing listings?
No. Let a visitor see the relevant public listing first. A budget can help an agent prepare a shortlist, but make it optional and ask only after the visitor has explained the property they want. A visitor who declines should still be able to request a viewing or speak to an agent.
Can the bot promise an agent will reply within a set time?
Only if the firm has measured that it can meet the promise during every period when the message appears. Otherwise, acknowledge the enquiry, state the actual monitored hours, and offer a route for an urgent matter. Test weekends, absences and failed notifications as well as ordinary working hours.
How much detail belongs in the agent's handover note?
Include the property reference, buyer or seller intent, stated timing, requested next action, contact permission and the full conversation link. Mark unconfirmed details as unconfirmed. Avoid a bot-generated judgement about a visitor's worth or suitability; the agent should see the visitor's own words and make the next decision.
Further reads
- Real Estate AI Chatbot Examples: Five Flows to Copy for Leads — Copy five buyer and seller conversation branches.
- Real Estate Chatbot Pricing: What Agents Pay for AI Lead Capture — Compare the cost of lead capture options.
- Real Estate AI Chatbot Demo: A Test Checklist Before You Sign — Use property enquiries in a vendor demonstration.
- AI Chatbot Disclosure: What to Tell Customers at the Start of a Chat — Write a clear AI disclosure for visitors.
- How to Measure Whether Your AI Chatbot Is Actually Working — Measure whether handovers become useful conversations.
- Real Estate AI Chatbot Features: A Checklist Before You Buy — Eight feature groups for a real estate AI chatbot, each with why it matters and a two-minute way to verify it in a demo, plus a filled-in scorecard.
- AI Lead Generation for Real Estate Agents: No Bought Lists Needed — A consent-first plan for agents: nurture your sphere, publish local answers and capture website enquiries with AI, with no bought or scraped lists.
- AI Real Estate Cold Calling: Scripts, Lists and Do-Not-Call Rules — How a real estate agent can use AI for scripts, objection replies and list prep, with the do-not-call checks that stay with a person.
- Real Estate AI Chatbot Use Cases: Which Three to Start With — Build three narrow chatbot flows first, test the handovers and keep property claims and decisions with agents.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: HubSpot Knowledge Base, Choose your rule-based chatbot actions (question, routing and meeting actions); fair housing steering regulation text; the regulator's 2026 notice withdrawing its 2024 digital-advertising guidance (effective September 2025), read 4 November 2026.