The four questions every property lead should answer

Budget, locality, timeline, buy or rent — how to read them from natural WhatsApp chat without interrogating the buyer.

The fastest way to lose a warm lead on WhatsApp is to send a form. Buyers didn't click “Enquire” to fill fifteen fields — they want a conversation with someone who knows Whitefield from Sarjapur and can tell them if a 3BHK at ₹1.2 Cr is realistic this quarter.

Good qualification doesn't feel like qualification. It feels like help. The best brokers extract four dimensions — budget, locality, timeline, and intent — while mirroring the buyer's language, one message at a time.

Everything else — floor preference, parking, facing, amenities — is secondary until these four are clear. They decide whether you show them inventory, schedule a visit, or politely close the loop.

1. Budget (with band, not exactness)

Indian buyers rarely open with “My budget is ₹95 lakhs.” They say “around one crore” or “80–90 range” or “under 1.5 for 3BHK.” Your job is to capture the band, not force precision.

• Good ask: “What budget range are you comfortable with for this search?”
• Better read: When they mention a project price, reflect it back — “So roughly ₹1–1.1 Cr all-in?”
• Watch for: Registration, maintenance, and “all inclusive” assumptions — clarify once, lightly.

2. Locality (micro-market, not just city)

“Bangalore” isn't actionable. “Whitefield, near ITPL” or “North Bangalore, open to Yelahanka” is. Locality often arrives before budget in natural chat — the buyer enquired on a specific listing.

If they named a project, you already have locality. Confirm adjacencies: “Open to Kadugodi side as well, or strictly Whitefield?”

3. Timeline (when they need keys, not when they'll chat)

Timeline separates browsers from buyers. “This month” and “after six months” get different inventory and different broker time. Ask directly but conversationally: “When are you looking to move in — urgent this quarter or flexible?”

4. Intent (buy, rent, or invest)

The same 3BHK enquiry can be an end-user purchase, a family rental, or an investor comparing rental yield. One question resolves it: “Is this for your own stay or as an investment?” For rentals, flip budget to monthly rent band and add lease duration.

Interrogation patterns kill trust. These patterns preserve it:

1. One question per message. Stack three questions and replies tend to drop off.
2. Mirror their words. If they write in Hindi-English mix, reply the same way — formal English on a casual Hinglish thread feels like a call centre.
3. Explain why you're asking. “So I don't waste your time with the wrong projects” beats a naked budget probe.
4. Accept partial answers. “Around a crore, still finalising locality” is enough to suggest two options and keep moving.

• 4 — fields that decide whether a visit is worth booking
• 1 — question per message for highest reply rates
• EN/HI — mirror the lead's language, not your template

Buyers volunteer more than they realise. Train yourself — or your system — to extract structure from plain text:

• “Whitefield 3BHK, around 1 crore, this weekend” → locality, configuration hint, budget band, timeline — in one line.
• “Just exploring options” → long timeline; send curated links, don't push Saturday slots.
• “What's the best price you can do?” → serious buyer; budget may be flexible upward if value is clear.
• Voice notes → common in India; treat them as first-class input, not noise.

Rule-based fallback. AI stalling mid-conversation is worse than a simple scripted next question. Always have a deterministic path: if budget is missing after two turns, ask budget; if locality is missing, ask locality. Never leave a thread silent.

Qualification has a finish line. You have enough when you can answer: “Would I send this person to Project A or Project B, and when?” If yes, propose a slot — don't ask a fifth question for completeness.

Genluno runs this loop automatically for portal leads: it reads the four fields from the chat (and the locality, budget and buy-or-rent from the lead email, so it doesn't ask again), falls back to rule-based prompts when needed, and offers three visit slots when the lead is ready. You get an email when a visit is booked, and you can read the whole thread in your Genluno dashboard.

• Did you capture budget band, not just “interested”?
• Is locality at micro-market level?
• Do you know if they need keys in weeks or months?
• Buy, rent, or invest — explicitly confirmed?
• Was each ask a single question in their language?

If you can tick all five from the thread alone, you qualified well. If not, the fix isn't more broker hours — it's a system that asks the right next question, every time, in under a minute.

Qualified leads only pay off when the visit happens — read how to book site visits that actually show up.

What questions should a broker ask to qualify a property lead?

Four: budget band, preferred locality at micro-market level, timeline to move or buy, and whether they want to buy, rent or invest. With those four answers you can decide whether a site visit is worth booking.

How do you ask a buyer's budget without sounding pushy?

Offer a range instead of asking for a number, ask one question per message, and use the buyer's own language, for example: are you looking around 60 to 80 lakh or a little higher?

Should brokers qualify leads in Hindi or English on WhatsApp?

Mirror the lead. Reply in the language and tone of their first message, and switch to Hinglish or Hindi when they do; matching them keeps the replies coming.

How does Genluno qualify leads on WhatsApp?

Genluno reads budget, locality, timeline and buy versus rent from natural chat, uses what the lead email already says, asks only for what is missing, and offers three visit slots when the lead is ready. After the buyer's first reply, it answers in English, Hindi or Hinglish to match them.