Real estate is a business where the lead is worth a lot and the enquiry is worth almost nothing. A portal enquiry that says "is this still available?" tells you nothing about whether the person has a mortgage in principle, a chain to sell, a budget within 30% of the asking price, or any intention of moving this decade. You find that out on a call, four days later, if they pick up.
An AI chatbot on your listings site changes the order of operations. It answers the property question instantly, then asks the three things that decide whether this person is worth your Saturday, then books the viewing or hands the qualified enquiry straight to your phone. This guide covers exactly how to build that for a sales or lettings agency.
Speed to lead is the whole game
Every study of enquiry response in property says the same thing in different words: the agent who replies first usually gets the instruction or the viewing. The problem is that enquiries do not arrive during working hours. They arrive at 21:30 on a Sunday when someone is scrolling on the sofa, and by Monday at 10am they have messaged four other agents.
A chatbot is not a better salesperson than you. It is an instantly available one. Its job is to hold the lead's attention for the ninety seconds that decide whether they wait for you or move on.
The three questions that qualify a property lead
Long qualification forms kill good leads. Three questions is the sweet spot, and in property they are almost always these:
| Question | What it filters out | Best format |
|---|---|---|
| Are you looking to buy, sell, rent or let? | Routes vendors away from the buyer flow entirely. Vendor leads are worth 10× more and need a different conversation. | Four buttons |
| What's your budget range? | The tyre-kickers 40% below asking, and the people who should be seeing your higher stock | Three or four price brackets as buttons |
| Have you got a mortgage in principle / a property to sell? | Proceedability. This is the single most useful answer you can have before a viewing. | Yes / No / Not yet |
Three taps, about fifteen seconds. The output is a lead record that tells you whether to call now, book a viewing, or send the mortgage adviser's number. Buttons matter here: on mobile a tap converts far better than a text box, and the answers come back clean instead of as free prose you have to interpret.
Four flows worth building, in priority order
1. The vendor flow (build this first)
A valuation request is the highest-value thing a chatbot can produce for a sales agency. The flow is short: postcode, property type, bedrooms, rough timescale, then name and phone. Route it to a lead form and send yourself an SMS immediately. If you offer instant online valuations, the bot is a far better front door for them than a static form, because it can explain what the number means before asking for contact details.
2. The viewing booking flow
For qualified buyers or tenants, skip the callback and let them book. Connected to your calendar, the bot offers your genuine free slots with your own availability rules (no viewings before 9am, none on Sunday, 45-minute blocks with travel time), and writes the appointment straight in. Full detail on the appointment booking page. This is where the compounding happens: a viewing booked at 22:00 on a Sunday is a viewing your competitor never got a chance at.
3. The listing Q&A
Service charge, ground rent, EPC rating, council tax band, tenure, chain status, parking, garden orientation, school catchment. These are the questions that eat your afternoon, and they are all in the property particulars you already wrote. Load the particulars as a dataset and the bot answers them verbatim, at 2am, in the buyer's own language.
4. The tenant pre-qualification flow (lettings)
Lettings is where filtering saves the most time, because the criteria are hard rules rather than preferences. Pets, smoking, employment status, guarantor availability, benefits acceptance, move-in date, number of occupants. Every one of these is a yes/no branch. A tenant who fails a hard criterion gets told politely and immediately, with a link to your other stock, rather than sitting in a queue for three days to hear no.
Where the human takes over
The handoff point is a decision you should make deliberately. Three sensible triggers:
- The lead qualifies and is hot. Proceedable buyer, in budget, wants to view this week. Push them to WhatsApp with their answers pre-typed so the negotiator opens a message that already says who they are, what they want and what they can spend.
- The question involves a number you'd be liable for. Offers, negotiation, what the vendor would accept, whether a survey issue is a problem. The bot should never speculate. Capture and escalate.
- The visitor asks for a person. Always honour that immediately. A bot that fights to keep someone in the chat loses the instruction.
Compliance and the things a property bot must not say
Property is a regulated, litigious business and an AI that free-associates is a genuine risk. Four hard rules:
- No fair-housing or discrimination exposure. The bot must never characterise an area's demographics, comment on "the type of people" in a neighbourhood, or steer a buyer toward or away from an area based on anything other than their stated budget and requirements. Say this explicitly in your bot's instructions.
- No financial advice. It can say what a mortgage in principle is. It must not tell anyone what they can afford or recommend a product. Route to your adviser.
- No valuation numbers off the cuff. "A member of the team will confirm the figure after the visit" is the correct answer to "what's my house worth". Capture the lead, don't guess the price.
- No claims about the property that aren't in the particulars. Feed the bot only what you have verified. If the tenure is unconfirmed, the dataset should say unconfirmed, and the bot will say so.
All four are configuration, not luck. They live in your chatbot's instructions and in what you do and do not put in its datasets.
Building it in an afternoon
- Create one chatbot per brand. If you run sales and lettings as separate identities, run two. Essential includes two chatbots; Pro includes five, which is usually enough for a small multi-branch agency.
- Load your particulars and area guides as datasets. Crawl your own site for the rest.
- Build the vendor flow first in the flow builder. It has the highest value per completion.
- Build the buyer flow second, with the three qualifying questions and a branch to viewing booking for proceedable leads.
- Connect your calendar and set availability rules honestly, including travel time.
- Turn on SMS notifications so a valuation request reaches you in the car, not in an inbox.
- Push qualified buyers to WhatsApp with the pre-typed summary.
- Read the first fifty transcripts. Every question the bot fumbled is one Q&A pair away from being answered forever.
What to expect, honestly
A chatbot will not double your instructions. What it reliably does is three things: it stops out-of-hours enquiries evaporating, it removes the twenty minutes a day you spend answering service-charge questions, and it tells you before the viewing whether the buyer is proceedable. In an agency doing 30 to 60 enquiries a month, that is usually one or two extra viewings a week and a noticeably shorter Saturday.
Related reading
- Filter bad leads before they reach your WhatsApp
- AI appointment booking use case, calendar rules in detail
- Conversational funnel use case, branching qualification
- Training a chatbot on your own listings and particulars