--- title: "Chatbot for a real estate website: answers and human handoff" description: "Plan a real estate website chatbot around seller and buyer questions, approved sources, inquiry delivery, and failure checks before choosing a provider." canonical: "https://scalewithsearch.com/articles/chatbot-for-real-estate-website" --- ## Site navigation - [Scale With Search](https://scalewithsearch.com/) - Services - Services - [AI systems](https://scalewithsearch.com/ai-systems) - [Site build](https://scalewithsearch.com/work#site-build) - [Whole website fix](https://scalewithsearch.com/work#whole-website-fix) - [Content library with SEO](https://scalewithsearch.com/work#content-library) - [Working session](https://scalewithsearch.com/audit) - Start here - [Send your brief](https://scalewithsearch.com/work#send-your-brief) - [Example scope](https://scalewithsearch.com/work#review-the-example-scope) - [Prices and terms](https://scalewithsearch.com/work#prices-and-terms) - Industries - Real estate - [Real estate agents and teams](https://scalewithsearch.com/for/real-estate) - [Platforms, ownership, and IDX](https://scalewithsearch.com/for/real-estate/real-estate-website-platforms-ownership-idx) - [Search, content, and AI](https://scalewithsearch.com/for/real-estate/real-estate-search-content-ai) - [Inquiries, campaigns, and handoffs](https://scalewithsearch.com/for/real-estate/real-estate-website-inquiries-campaigns-handoffs) - [Buyer, seller, and local pages](https://scalewithsearch.com/for/real-estate/real-estate-buyer-seller-local-resources) - [Rules, privacy, and trust](https://scalewithsearch.com/for/real-estate/real-estate-website-rules-privacy-trust) - Browse by business - [Trades and home services](https://scalewithsearch.com/for/#group-trades) - [Health, wellness, and animal care](https://scalewithsearch.com/for/#group-practices) - [Law, finance, and IT](https://scalewithsearch.com/for/#group-professional) - [Marketing and SEO agencies](https://scalewithsearch.com/for/#group-agencies) - [Shops and manufacturers](https://scalewithsearch.com/for/#group-manufacturing) - [Restaurants, shops, studios, and nonprofits](https://scalewithsearch.com/for/#group-local-services) - Chiropractic practices - [Chiropractic and wellness practices](https://scalewithsearch.com/for/chiropractic-and-wellness-practices) - [Chiropractic and physical therapy clinics](https://scalewithsearch.com/for/chiropractic-and-physical-therapy-clinics) - [All industries](https://scalewithsearch.com/for/) - Resources - Free tools - [AI readiness check](https://scalewithsearch.com/check) - [Free tools](https://scalewithsearch.com/tools/) - [Free Starter Kit](https://scalewithsearch.com/kit/business-memory-starter-kit.zip) - Guides - [AI-native library](https://scalewithsearch.com/ai-native) - [Industry intelligence](https://scalewithsearch.com/intelligence) - [Office job guides](https://scalewithsearch.com/guides/) - [Business memory](https://scalewithsearch.com/articles/business-memory-for-ai-agents-guide) - [Agent governance](https://scalewithsearch.com/articles/ai-agent-governance-guide-small-business) - [Migration and ownership](https://scalewithsearch.com/articles/leaving-vendor-ai-memory-guide) - Articles - [All articles](https://scalewithsearch.com/articles/) - [What changed](https://scalewithsearch.com/changes/) - About - Evidence - [Proof](https://scalewithsearch.com/proof) - Scale With Search - [About](https://scalewithsearch.com/about) - [How it works](https://scalewithsearch.com/how-it-works) # Chatbot for real estate: define your website's answers and handoff Choose a chatbot for your real estate website only after defining what it may answer and how an inquiry reaches you. Start with approved service information, separate seller and buyer questions, and a visible way to contact a person. Require a received test inquiry before accepting the setup. Use this guide as a website brief. The proposed flows and checks are recommendations you can adapt to your practice. Keep an ordinary contact route available throughout the conversation. For AI-generated replies, account for inaccurate answers. NIST identifies confidently presented false information as a generative AI risk called confabulation. An answer's fluent wording does not establish its accuracy. [NIST's Generative AI Profile, section 2.2](https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.600-1.pdf). ## Decide what the chat should do on your website Name the visitor task before comparing real estate chatbots. A seller asking about representation needs a different path from a buyer asking about a particular property. Write the intended outcome for each path. For example, ask the seller flow to explain your approved process and deliver a request for a conversation. Ask the buyer flow to retain the property-page link with the question. Compare these proposed approaches with the provider. The table is a planning framework, without a ranking or a claim about a particular product. | Approach to request | Suitable task to investigate | Demonstration to require | | --- | --- | --- | | Button-led questions and fixed replies | Offer seller, buyer, and general-contact routes | Show every branch and its destination | | Replies selected from approved answers | Explain your services using reviewed wording | Show the answer source and unsupported-question fallback | | AI-generated replies using approved material | Respond to varied wording of supported questions | Show source matching, answer limits, and handoff when information is missing | Choose the smallest approach that completes the task. If the task only needs a question and contact details, compare a short form with chat. Require a demonstrated reason for the extra feature. ## Specify the answers you will approve Prepare a source list before asking a provider to configure replies. Include your service pages, contact information, and approved explanations of your selling or buying process. Name who reviews each source and updates it. Use an answer sheet with these fields: visitor question, approved information, source URL, review date, and fallback. Mark absent information as unavailable. For a seller question about preparation, supply your approved preparation guidance. For a buyer question about requesting a showing, supply the actual request process. Keep the difference between requesting and confirming an appointment explicit. Keep property-specific answers within a separately approved scope. Ask the provider to identify the authorized information source. Require a demonstration with that source unavailable or outdated. Without that evidence, direct the question to a person. Reserve valuations, offer strategy, contract interpretation, and individual financing decisions for human review in your proposed brief. Require the chatbot to offer contact rather than improvise an answer. Do not accept a home-value figure generated without a defined valuation process and supporting information. A seller's request for advice should remain a request until the responsible professional answers it. ## Keep seller and buyer questions tied to the inquiry Label the conversation as automated and explain its intended task. Propose an opening choice of selling, buying, or another question. Allow visitors to change that choice and ask for a person at any point. For a seller path, ask what help the person wants. Offer optional questions about the property's area and intended timing. Request a name and preferred reply method when the person chooses to be contacted. For a buyer path, retain the property-page URL when the conversation starts there. Ask whether the question concerns that property, a search, or the buying process. Let the visitor supply the question in their own words. Treat timing and location as context for a reply. Avoid making every planning field a condition of contacting you. Require the provider to show how skipped questions appear in the received inquiry. Keep a request for a showing separate from confirmed availability. Ask the flow to collect the request and explain the next step you have approved. Permit a confirmation only after the responsible system or person verifies it. Review the proposed questions against their business purpose. The FTC advises collecting and retaining sensitive information only when there is a legitimate business need. [FTC's data-security guide, section 2](https://www.ftc.gov/business-guidance/resources/protecting-personal-information-guide-business). For the initial inquiry, exclude identification documents, financial account details, and payment-card information. Ask the provider where transcripts are stored, who can access them, and how long they remain. Resolve the collection notice and deletion process before launch. ## Define what a human handoff must deliver Name the recipient, receiving inbox or contact system, and person responsible for missed delivery. Agree on the information that must arrive with each inquiry. Require the visitor's question, chosen contact method, seller or buyer route, source page, and submission time. Preserve relevant conversation context within the agreed privacy scope. Ask the provider to show the received record and the reply path. For a fallback form, inspect delivery beyond the browser. MDN explains that an HTML form sends an HTTP request to a server, which processes the submitted information. That mechanism does not establish delivery to your chosen inbox. [MDN's form-data explanation](https://developer.mozilla.org/en-US/docs/Learn_web_development/Extensions/Forms/Sending_and_retrieving_form_data). Agree on separate messages for a saved request, unavailable live staff, and failed submission. Require each message to match the observed system state. Avoid claiming that a person has joined before someone accepts the conversation. Use a clearly labeled test with contact details you control. Compare the visitor's final message with the received inquiry. Confirm that the recipient can answer through the selected channel. - [Real estate CRM and website: map forms to contact records](/articles/real-estate-crm-and-website) - [Test the seller inquiry path on your real estate website](/articles/seller-inquiry-path-agent-website) - [Check your real estate website in 30 minutes](/articles/real-estate-website-audit) ## Limit what a public AI chatbot can access If you choose generated replies, ask the provider how it handles attempts to change its instructions. OWASP describes prompt injection as inputs that alter a language model's behavior or output in unintended ways. [OWASP's prompt-injection guidance](https://genai.owasp.org/llmrisk/llm01-prompt-injection/). Request a demonstration using a question that asks the chatbot to ignore its rules and reveal private information. Require it to maintain its answer limits. Use synthetic material in this test. Keep private client records out of the public answer source. Require separate authorization before any connection can change appointments or records. OWASP recommends restricting model privileges and handling extensible functions in application code. [OWASP's privilege-control guidance](https://genai.owasp.org/llmrisk/llm01-prompt-injection/). ## Test the conversation, delivery, and fallback Agree on the expected result before testing. Run controlled checks on a preview with the provider and receiving person. Keep the prompt, displayed answer, source, and received record together. The following cases are proposed acceptance tests. They are not results from an installed chatbot. | Test case | Expected behavior to agree | | --- | --- | | Seller asks about your services | Use the approved explanation and offer contact | | Buyer starts from a property page | Retain the correct property link with the inquiry | | Visitor skips optional questions | Continue to contact without inventing missing details | | Visitor requests a person immediately | Offer the human-contact path without repeating qualification | | Question has no approved answer | State the information limit and offer handoff | | Listing source is unavailable or outdated | Avoid asserting current status or availability | | Visitor requests private records | Refuse disclosure and retain the configured boundaries | | Recipient is unavailable | Explain the approved next step without claiming live attendance | | Submission fails | Show a truthful failure state and an alternative contact route | | Same request is retried | Follow the agreed duplicate-handling rule and retain context | | Chat service fails to load | Keep the ordinary website contact path usable | Check the phone layout with the keyboard open. Require readable replies and reachable send and close controls. Confirm that closing chat restores access to the page's contact action. Ask the builder to identify the accessibility pattern used by the widget. W3C's modal-dialog guidance includes keyboard focus management and closing with Escape. Apply those checks when chat uses a modal dialog. [W3C's modal-dialog pattern](https://www.w3.org/WAI/ARIA/apg/patterns/dialog-modal/). Record failed checks and the person correcting them. Repeat the affected cases after each repair. Keep delivery unconfirmed until the intended recipient shows the matching test inquiry. ## Bring the chatbot brief into your website scope Your chatbot brief names supported answers, escalation conditions, and the human recipient. Use [whole website fix: chatbot handoffs](/for/real-estate) to request the website connection. The whole website fix requires integration decisions in its written scope. [chatbot handoffs, published scope, checked 2026.10.14](https://scalewithsearch.com/work). ## Related: Real estate - [Real estate CRM and website: map forms to contact records](/articles/real-estate-crm-and-website) - [Test the seller inquiry path on your real estate website](/articles/seller-inquiry-path-agent-website) - [Check your real estate website in 30 minutes](/articles/real-estate-website-audit) ---- ```text .|########||. .|########||. .|########||. |##||. .||##|. |##||. .||##|. |##||. .||##|. |#|. .|#|. |#|. .|#|. |#|. .|#|. |#| |#| |#| |#| |#| |#| .#| |#. .#| |#. .#| |#. .#. .#| .#. .#| .#. .#| |#. .#| |#. .#| |#. .#| |# ...... #| |# ...... #| |# ...... #| .# ||#########| #| .# ||#########| #| .# ||#########| #| .#. |######||######|. .#. .#. |######||######|. .#. .#. |######||######|. .#. #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# # .||####|###########################|. # # .||####|###########################|. # # .||####|###########################|. # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || #. .######|#|#########| .# #. .######|#|#########| .# #. .######|#|#########| .# .#. |#####||||#####| .#. .#. |#####||||#####| .#. .#. |#####||||#####| .#. |# ||########|| #. |# ||########|| #. |# ||########|| #. |# ...... #| |# ...... #| |# ...... #| |#. .#| |#. .#| |#. .#| |#. .#. |#. .#. |#. .#. .#| |#. .#| |#. .#| |#. |#| |#| |#| |#| |#| |#| .|#|. .|#|. .|#|. .|#|. .|#|. .|#|. |##||. .||##| |##||. .||##| |##||. .||##| .||########||. .||########||. .||########||. Scale With Search 2026 [scalewithsearch.com](https://scalewithsearch.com) ```