What does a chatbot for real estate actually do?
A chatbot for real estate is the first responder for property enquiries: it greets, qualifies, shares approved project material and books site visits, then passes a ready-to-call lead to a human sales manager.
Property enquiries have a short half-life. A buyer who fills a portal form at 10:30 pm often fills three more for competing projects within minutes. Whoever replies first with useful information, not just “Thank you, our executive will call you”, usually gets the site visit. A well-built bot replies within seconds with the project name, asks what the buyer is looking for, and sends the right floor plan.
It is equally useful in the opposite direction: filtering. Many portal leads are brokers fishing for inventory, students, or buyers whose budget is far from your project. The bot identifies these politely, so telecallers do not spend the next morning on them.
What the bot does not do is sell. Choosing a home involves family discussion, loan approval, site inspection and trust in the builder. The bot's job ends when a qualified buyer has a confirmed visit and the sales manager has the context. For other property software, such as buyer apps, see real estate app development.
Builder or broker: how the real estate chatbot changes
Builders use a chatbot to sell units in their own registered projects; brokers and channel partners use one to match buyers with inventory across many projects and localities. The flows look similar but the data and rules differ.
For builders
The bot knows each project in depth: towers, unit types, carpet areas, price sheet, amenities, construction status and approved brochures. Qualification checks fit with a specific project. Site visits are booked into the project's sales lounge slots.
For brokers and agents
The bot works across an inventory list. It asks location, budget, BHK and buy or rent, then shortlists matching listings from your sheet or CRM and offers a call or visit. Listings must be current; a bot sharing a flat that sold last week damages trust.
For channel partners of a builder
A separate flow lets registered partners log a client, check availability and download approved material, so registrations are time-stamped and disputes over who brought a buyer are easier to settle.
For rentals and resale
Rental enquiries need speed and filters such as family or bachelor, pets, and move-in date. Resale adds document questions, which the bot should hand to a person rather than answer.
Qualifying property enquiries by budget, location and BHK
Qualification means asking the few questions that decide whether this buyer fits this project, in a natural order, and storing each answer as a field your sales team can filter on.
A typical flow for a residential project, adjusted to your market:
- “Which configuration are you looking at: 2 BHK, 3 BHK or larger?”
- “What budget range should we keep in mind?” shown as ranges, not a free number
- “Is this for your own family or as an investment?”
- “When are you planning to buy: now, within six months, or later?”
- “Will you need a home loan?”, which helps the team prepare
- “Where do you stay or work now?”, useful for commute questions and NRI detection
- Name and preferred time to talk, if not already known from the form
Order matters. Asking budget first feels abrupt; asking configuration first feels helpful. Each answer shapes the next message: a buyer whose budget is below the project's lowest unit gets a polite note and, if you have one, a suggestion for another project. For a deeper look at scoring logic across industries, see AI lead qualification.
Sending brochures, floor plans and price sheets on WhatsApp
The bot sends only files your team has approved for the current phase of the project, matched to what the buyer asked for, and records which version each buyer received.
Real estate collateral changes often: a new price sheet after a phase launch, revised floor plans, updated amenity lists. Sales teams end up forwarding old PDFs from their phones. With a bot, the approved set lives in one place. Your marketing or sales head replaces a file once, and every future message uses the new version.
We tag each document by project, unit type and validity. A buyer asking about 3 BHK gets the 3 BHK floor plan, not the entire 40-page brochure. Price sheets can be sent automatically or only after qualification, depending on your preference; many builders prefer to share prices after a buyer states a matching budget.
Every sent file is logged against the lead: which file, which version, when. If a buyer later says “your brochure said something else”, you can check what they actually received. The location pin, a short walkthrough video and the sales lounge timings usually go with the first message after qualification.
How a real estate chatbot schedules site visits
The bot offers available visit slots for the chosen project, assigns a sales manager by your rules, confirms on WhatsApp with the location pin, and sends reminders the day before and on the morning of the visit.
Slots come from a simple calendar per project: sales lounge hours, maximum visits per slot, and blocked times such as holidays or events. Weekends fill first in most markets, so the bot can suggest weekday alternatives when Saturday is full. For Google Workspace calendars, Google's Calendar API has a free/busy query that returns busy periods for a set of calendars, which lets the bot respect each manager's availability without reading meeting details.
On the day, the reminder includes a map link and the sales manager's name. If the buyer asks to reschedule, the bot offers new slots and updates the calendar and CRM together. After the visit, a short feedback message asks how it went and whether they would like a second visit, a call about loans, or more details on a particular unit.
The same booking engine drives demo and meeting bookings in our AI sales agent builds, adapted here for property visits.
Integrating leads from property portals and ads
Portal and ad leads should reach the bot automatically so each buyer gets a WhatsApp message within seconds of submitting a form, not a callback the next day.
Methods vary by source. Meta lead ads can be connected through Meta's lead retrieval tools, which we cover on Facebook lead ads integration. Google ad lead forms can post to a webhook. Property portals differ by portal and by subscription: some offer an API or a CRM integration, others send lead emails or allow exports. We check what your accounts provide during planning and use the most reliable option; where only email is available, we parse the lead emails into structured records.
Once a lead arrives, the bot sends a message that names the project the buyer enquired about, which feels far more genuine than a generic greeting. Duplicate detection matters: the same buyer often enquires on two portals and your website within an hour. The bot merges these into one lead and one conversation.
Remember that a form submission is not always consent to marketing on WhatsApp. Your opt-in wording on ads and forms should make the follow-up channel clear. Your lawyer should approve the final wording.
RERA-compliant messaging: what a real estate chatbot must be careful about
A real estate chatbot should share only approved, accurate project information, display registration details the way your advisers require, and never make promises about returns, appreciation or possession dates that are not in your approved documents.
The Real Estate (Regulation and Development) Act, 2016 requires projects within its scope to be registered with the state RERA authority before they are marketed, and real estate agents to register as well. State rules add their own details on how advertisements show registration information. We are developers, not lawyers, so we build to the checklist your legal or compliance team gives us rather than interpreting the law ourselves.
In practice, the bot can support careful messaging like this:
- Project introduction messages carry the registration details in the format your advisers specify
- Brochures and price sheets are the approved versions only, with validity dates
- Questions about returns, rental yield or price appreciation get a neutral reply and a handover, never a figure
- Possession timelines are quoted only as stated in your approved documents
- Carpet area is described exactly as in your approved material
- Channel partner flows can ask for the partner's own registration number where you require it
Every outgoing message is logged, which helps if a buyer later disputes what was said. Compliance itself remains the responsibility of the builder or broker and their legal advisers; the bot simply makes consistent, approved messaging much easier to maintain.
Should the chatbot for real estate run on WhatsApp or the project website?
WhatsApp should be the main channel for most Indian real estate enquiries, with a website chat as a second entry point that moves the conversation to WhatsApp once the buyer shares a number.
Property buyers want brochures, floor plans, videos and a location pin, all of which travel naturally on WhatsApp and stay in the buyer's chat for family discussion. Meta's WhatsApp Business Messaging Policy requires opt-in before a business messages someone and a clear path to a human when automation replies, so the flow includes consent and a “talk to sales” button. When a buyer messages you, a 24-hour window opens in which replies are free non-template messages; later follow-ups use approved templates charged per message under Meta's pricing.
The website chat catches visitors who are reading the project page but not ready to fill a form. It can answer basic questions and offer the brochure on WhatsApp, which is often the moment a visitor becomes a lead.
QR codes on hoardings, site boards and newspaper inserts can open a WhatsApp chat with the project pre-selected, so offline campaigns feed the same system and can be counted separately.
Routing qualified leads to the right sales manager and CRM
Routing rules send each qualified lead to the right person by project, budget, language or buyer type, and every conversation is saved to your CRM so nothing depends on one person's phone.
Common rules include round-robin within a project team, sending NRI leads to a dedicated manager, routing premium-budget buyers to senior staff, or assigning by language. The assigned manager gets a WhatsApp summary: name, configuration, budget range, timeline, loan need, brochure versions sent and visit slot if booked.
We connect to Zoho CRM, a real estate CRM that exposes an API, or a Google Sheet. If you do not have a CRM yet, a sheet with clear columns works well for a single project; Zoho CRM implementation suits growing teams. Two-way sync lets the bot stop follow-ups when a manager marks a lead booked or not interested.
Owners usually want one view: leads per source, qualification rate, visits booked, visits done and bookings. A weekly dashboard gives that without anyone compiling spreadsheets on Monday morning.
NRI buyers, time zones and regional languages
NRI buyers enquire when it is night in India, so an always-on chatbot for real estate is especially valuable for them; it answers immediately and books a video call or a family member's site visit at a time that works on both sides.
The bot can detect an international number or ask where the buyer lives, then switch to a flow that offers video walkthroughs, virtual site visits, and calls scheduled in the buyer's time zone. It can also collect whether a relative in India will visit on their behalf and book that visit.
For language, the bot understands and replies in English, Hindi and Hinglish comfortably. Many regional markets expect Marathi, Gujarati, Tamil, Telugu or Kannada. We build the flow and your team supplies or approves the wording in those languages, since our team writes in English and Hindi. WhatsApp templates need Meta's approval separately for each language.
Finance questions from NRI buyers, such as repatriation or loan eligibility abroad, should always go to a person or your finance partner. The bot collects the question and routes it rather than answering.
How much does a chatbot for real estate cost in India?
A custom chatbot for real estate from BtechWaleTech starts at ₹40,000 (US$600) for one project on WhatsApp with qualification, approved documents, visit booking and CRM logging. Extra projects, portal integrations and partner flows add to the quote.
What drives the cost:
- Number of projects, each with its own documents, slots and team
- Number of lead sources and how each portal delivers leads
- Routing complexity across teams, languages and budgets
- Channel partner registration and material download flows
- Languages beyond English and Hindi
- Whether you need a full CRM or buyer portal built, from the custom software plan
Running costs are paid directly by you: WhatsApp template messages, AI usage and hosting. For wider chatbot budgets see chatbot development cost in India. After two free months of maintenance, an optional plan starts from ₹8,000/mo.
How long does it take to launch a real estate chatbot?
One project on WhatsApp usually goes live in 2–4 weeks; each additional project takes less time because the flow already exists and only documents, slots and routing change.
Week one collects the project data: unit types, carpet areas, approved brochures and price sheets, site-visit hours, sales team list, and your compliance checklist. Week two builds the qualification flow, document library, booking calendar and CRM mapping. Week three tests with real past enquiries, including awkward ones about discounts, returns and possession dates, and adjusts wording with your sales head.
The WhatsApp side sometimes sets the pace. Business verification and display name approval by Meta can take time, and every template needs approval. We start that paperwork on day one. Launch timing also matters: going live a week before a big project launch or expo gives the team time to trust it before volume peaks.
Measuring a chatbot for real estate: from enquiry to booking
Measure the chatbot on the funnel your sales head already watches: enquiries, qualified leads, site visits booked, visits completed and bookings, split by source and project.
The earliest gains are usually visible in response time and visit bookings, because the bot replies instantly and makes booking a two-tap job. Completed visits show whether the reminders work. Bookings take longer to judge, since property decisions often take weeks or months, so compare quarters rather than weeks.
Source-level numbers are where marketing budgets get decided. When every lead carries its source, whether a portal, a Meta campaign, Google ads, a hoarding QR code or the website, you can calculate cost per qualified lead and cost per site visit for each. That is far more useful than cost per raw lead, because raw portal leads vary so much in quality.
Also watch handover reasons. If many buyers ask about something the bot cannot answer, such as parking allotment or maintenance charges, add the approved answer to the knowledge base. Search visibility for the project itself is a separate task covered on real estate SEO services.
Red flags when choosing a real estate chatbot
Avoid any setup that blasts messages to purchased databases, lets the AI improvise claims about prices or returns, or keeps your leads inside someone else's account.
- Bulk messaging to contact lists that never opted in, which risks your number being blocked
- Unofficial WhatsApp tools running on a personal phone
- An AI allowed to answer questions about returns, appreciation or possession freely
- Old brochures and price sheets with no version control
- No human handover, which Meta's policy expects when automation replies
- Leads stored only in the vendor's dashboard with no export
- Promises of a fixed number of bookings per month
A quick test for any vendor: ask their demo bot “what return will I get in five years?” The right answer is a polite handover, not a percentage.
Worked example: a chatbot for a hypothetical two-project builder
Say a hypothetical builder in Nashik has two residential projects, one mid-segment and one premium, gets enquiries from two property portals, Meta ads and a hoarding campaign, and has four sales managers who spend mornings calling back last night's leads.
A practical first build would put both projects behind one WhatsApp number, with the project chosen by the ad or QR code the buyer came from. The bot would ask configuration, budget range, timeline and purpose; a mid-segment budget enquiring on the premium project would be offered the other project politely. Approved floor plans per unit type would go out after qualification, price sheets after a matching budget, and visits would be booked into Saturday and Sunday slots with weekday alternatives when full.
Portal leads would be pulled in by whatever method each subscription supports, duplicates merged, and every lead routed round-robin within the project team, with NRI numbers sent to one manager. The first project would be quoted from ₹40,000, the second as an add-on. This is an illustration for planning, not a real client or promised result.
Real estate chatbot launch checklist
Have these ready and your chatbot can go live quickly, with messaging your team is comfortable with.
- Project data per project: unit types, carpet areas, status, amenities
- Approved brochures, floor plans and price sheets, each with a validity date
- Your compliance checklist for messages, from your legal or compliance adviser
- Site-visit hours, slot sizes and blocked dates per project
- Sales team list with routing rules by project, budget and language
- Lead sources and how each portal delivers leads on your subscription
- A WhatsApp Business Platform number owned by the business, verified with Meta
- Opt-in wording on ad forms and website forms
- A list of questions the bot must always hand over
- Your CRM or the Google Sheet the team uses daily
Share whatever you have on WhatsApp. The three of us work remotely, in English and Hindi, and do not do site visits ourselves; everything runs over calls and screen-share. An itemised quote follows in about two working days.