Real estate · Missed enquiries
Real estate lead leakage: where buyers disappear before a site visit
Keep project questions, buyer preferences and visit requests together so property enquiries reach the right person.
A property enquiry can go cold long before a buyer rejects the project. The buyer asks about a configuration after office hours, receives an unrelated brochure, or waits for a callback that never comes.
The problem is not always lead quality. Sometimes the process loses the information that would help the sales team recognise a useful enquiry.
Follow the enquiry across channels
List the routes into your project: website, ad landing pages, channel-partner links, brochures and hoardings. Check where each route sends the buyer and where the resulting enquiry is recorded.
A contact number without the project, configuration or original question is a weak handover. It makes the buyer repeat themselves and leaves pre-sales guessing where to start.
Use tagged agent links or QR codes for distinct campaigns. Attribution records the source when that information is passed through; it does not automatically identify every offline interaction.
Trace one enquiry end to end
Reading a funnel report tells you the totals. Walking a single enquiry through your own process tells you where it breaks. Do this once per route, with a real enquiry or a test you submit yourself.
- Submit the enquiry the way a buyer would — through the hoarding QR, the ad landing page, the channel-partner link, the website. Use a real question, not "test".
- Note the timestamp and what the buyer sees immediately afterwards. Is there any acknowledgement, or silence?
- Find where it landed. A CRM record, a shared inbox, a spreadsheet, one executive's phone. Write down the actual destination, not the intended one.
- Check what arrived with it. Project, configuration, budget, timeline, the original question, the campaign source. Tick only the fields genuinely present.
- Time the first human response and record who made it.
- Ask that person what they knew before they called. If they had to ask the buyer to repeat the question, the handover failed regardless of response time.
Run this for every route and you will usually find one or two that lose the context entirely while still producing a phone number.
The fields that decide whether a callback is useful
| Field | Why the next executive needs it |
|---|---|
| Project and configuration | Prevents quoting the wrong unit type |
| Original question | Lets the call start where the buyer left off |
| Approximate budget | Only if the buyer offered it; do not infer |
| Timeline and purpose | Separates an active buyer from early research |
| Preferred contact time | Raises the chance the call is answered |
| Campaign source | Makes spend comparisons meaningful |
If fewer than four of these reach the lead record, the leak is in capture, not in follow-up.
Ask enough to make the next call useful
Qualification should feel like a conversation, not an application form. Start with the question the buyer asked, then collect relevant preferences:
- Project or locality of interest.
- Configuration and approximate budget.
- Buying timeline and whether the property is for self-use or investment.
- Preferred contact method and a convenient time.
Do not interpret a short number as a budget or a survey reference without context. Ask what it means.
An illustrative comparison
The following is a hypothetical scenario written to show the difference between two handovers, not a customer case study.
Two enquiries arrive on the same evening from the same hoarding QR code.
The first reaches pre-sales as a name and a number. The executive calls the next morning, opens with "you enquired about our project", and spends the first two minutes establishing which project and what the buyer wanted. The buyer has since visited two other sites.
The second reaches pre-sales with the buyer's question about east-facing 3BHK availability, their stated timeline of "within six months", a preferred callback on Saturday morning, and the hoarding location as source. The executive calls on Saturday and opens with the answer to the question that was actually asked.
Neither enquiry has been sold anything. The second one has a conversation worth having; the first has to be rebuilt from nothing.
Keep project facts attached to their project
Prices, carpet areas and possession dates need clear ownership. Put the project, tower or configuration beside the fact in your content. A comparison with another developer's price is not your own price.
A website knowledge base is not a live inventory feed, a title check or an authoritative property-record lookup. When current availability or a specific record needs checking, the agent should explain the boundary and direct the buyer to your team or an approved service.
Where Serviti fits
Serviti answers from approved project content, captures enquiry details and gives your team a lead record with conversation context. The team can manage follow-up from the lead CRM rather than relying only on an executive's personal notes.
An agent can collect interest in a site visit and the buyer's preferred timing. That is a visit request, not a confirmed booking. Your team must check the schedule and confirm it.
Growth includes real-time lead alerts and human WhatsApp handoff. Scale adds Lead Intelligence and supported integrations. Review plans for the current capabilities.
Measure the handover, not just the contact count
Track response time, contactable enquiries, visit requests and visits actually confirmed by staff. Record outcomes consistently before comparing campaigns.
A useful monthly view separates four numbers that are often collapsed into one:
- Enquiries received — everything that arrived, including duplicates and wrong numbers
- Contactable enquiries — those with usable details and a genuine property interest
- Visit requests — buyers who asked for a time
- Visits confirmed by staff — the schedule actually accepted them
The gap between the third and fourth number is where most reporting quietly overstates performance.
Common questions
Is lead leakage the same as poor lead quality? No, and conflating them is expensive. Poor quality means the enquiries were never going to buy. Leakage means usable enquiries lost their context or their owner. The trace exercise above separates the two — if executives are calling people who asked real questions but arriving without the question, that is leakage.
We use a CRM already. Can we still be leaking? Yes. A CRM records what reaches it. If the hoarding QR opens a chat that captures only a phone number, the CRM will faithfully store an incomplete lead. Check what arrives, not whether something arrives.
Should we ask for budget up front? Only if the buyer volunteers it. Demanding a budget before answering a question tends to end the conversation, and an unexplained number in a chat is not reliable data. Capture it when offered and mark it as approximate.
How do we attribute enquiries from hoardings and print? Use a distinct tracked link or QR per placement. That records the source when the buyer uses it. It will not capture people who see the hoarding and search for you separately — offline attribution is always partial, and treating it as complete will mislead your spend decisions.
What is the difference between a visit request and a booking? A request is the buyer telling you when they would like to come. A booking is your team confirming that slot against the schedule. Showing a buyer a confirmation before staff have accepted it creates exactly the kind of broken promise that loses the sale.
Read next: WhatsApp lead management and real estate follow-up.
