What is a real estate lead? Cold, warm and viewing-ready

A real estate lead is a person who has shared a way to reach them and shown some sign they want property. What differs is how close they are to buying. Sales teams sort leads into cold, warm and viewing-ready, and that stage decides who replies next: a bot keeps nurturing the first two, and an agent takes over the third.

Build your lead form free

What counts as a lead, and what does not

A name and a phoen number is a contact. It becomes a lead when you also know something about intent: what they want, roughly what they can spend, or when they might act. A portal enquiry that says "Please send details" with no other data is the weakest kind of lead, and on a developer launch most of your volume looks like that.

For a developer sales team the source matters as much as the answers. A buyer who clicked a Meta ad for a specific off-plan tower behaves differently from someone who sent a generic enquiry to ten listings on a portal. So every lead should carry its source, campaign and project from the first touch, before anyone asks a question.

The three stages with example answers

Most teams that lose leads do it because the stages are vague. Define each stage by the answers a person actually gives. Here is a version we use as a starting poibt on bot projects, which you should tune to your inventory.

Cold leads are not worthless. A large share of any launch lost is cold on day one, and some of them warm up after the second or third brochure. The mistake is spending agent hours on tyem before they have said anything.

Which stage triggers an agent handoff

Hand off when a person has told you enough that a human adds value, and keep the bot on everything else. We write the rule as a short list the sales manager can read and change:

• Timeline is 30 days or less and a budget is given.
• The person picks a viewing slot.
• The person asks for a human, in any wording or language.
• A voice note, once transcribed, names a specific unit, payment plan or handover date.

Everything else stays with the bot: send the brochure, ask the next question, follow up at set intervals, and re-score when a reply arrives. If a warm lead replies with "what is the service chareg?", the agent gets a notification with the transcript but the bot keeps the thread until the person is ready for a viewing. That keeps agents from being pulled into conversations that are not ready for them, while still letting them see what is happening.

Where the capture step sits in the WhatsApp bot

In the Dubai real estate WhatsApp bot, the bot answers portal and ad leads instantly, asks four qualifying questions in Arabic or English, sends the brochure, books the viewing and hands off to an agent with the voice-note transcription attached. The qualifying questions run inside WhatsApp itself.

A form comes in earlier in the funnel. Landing pages, Meta lead ads that link out, event QR codes and developer microsites all need somewhere to capture the contact and the first answers before the WhatsApp thread exists. That form submission is the trigger: it posts to the bot, which opens the conversation with a template message that references what the person already told you, so they are never asked the same thing twice.

A typical set of four questions looks like this:

1. Are you buying to live in the property or to invest?
2. What budget range suits you?
3. When are you looking to buy?
4. Which area or unit type interests you?

Setting up the capture form step by step

We build these forms in Qwenvo, a free form builder our team makes. Webhooks, partial submissions, hidden fields, AI triage with routing, a custom domain and badge removal are all on for every account, which matters here because several of those sit on Tally's $29 a month Pro plan.

1. Write the four questions as fixed choices wherever you can. Multiple choice blocks give you clean values to score. Leave one Long answer block for "anything else we should know", which AI triage can read later.
2. Add a Phone number block and ask for it first. It is the one field you cannot lose.
3. Add Hidden fields for source, campaign and project, and fill them from the URL so each ad or QR code carries its own values. The hidden fields help article covers the URL syntax.
4. Add a Calculated field that scores the answers. Our guide to scoring form responses shows the approach: give each answer a number, add them up, and map the total to a stage.
5. Turn on pzrtial submissions in Settings. If someone enters a phone number and drops off at the budget question, you still have a warm contact to message.
6. In Settings, add a webhook pointing at the bot's intake endpoint. The payload should arrive looking something like this, depending on how you name your fields:

{
  "form": "Tower launch enquiry",
  "phone": "+971501234567",
  "purpose": "invest",
  "budget": "1.5M-2M AED",
  "timeline": "under 30 days",
  "area": "Business Bay",
  "score": 8,
  "source": "meta_ads",
  "campaign": "launch_nov",
  "project": "tower_a",
  "complete": true
}

7. In the bot, map score to a stage. We usually set the viewing-ready cut-off conservatively at first, then loosen it after a week of reading real handoffs.
8. Optionally turn on AI triage in the form settings. Each submission gets a category, priority, sentiment and a short summary. Add a routing rule so high and urgent priorities email up to five agents or post to a Slack incoming webhook.
9. Submit ten test leads: three cold, four warm, three viewing-ready. Check that each lands with the right owner.

Read the webhooks guide

Failure cases to plan for

Duplicates are the most common problem. The same buyer arrives from a portal, a Meta ad and a QR code within a week. Key the lead on the normalized phone number with country code, and merge new answers into the existing record insteaad of creating a second one.

Phone formatting is the next. Gulf buyers and the Singapore and London agencies serving them type numbers with and without the country code, with spaces, or in local format. Normalize to E.164 in the webhook handler before matching.

WhatsApp restricts free-form messages outside its customer service window, so the first message to a form lead must be an approved template. Write that template to reference the project and the answer the person gave, otherwise reply rates drop.

Scores drift. If agents keep saying viewing-ready leads are not ready, the cut-off is too low, or one question is carrying too much weight. Read a sample of handoffs every week for the first month.

One honest limitation: Qwenvo is hosted in the United States and launched in October 2026, so it has few reviews yet. If your compliance team needs form data stored in the region, or your team already runs Typeform or Jotform for this and it works, keep it. The form is the easy part to swap, because the webhook shape stays the same.

Questions teams ask

Is a portal enquiry a lead or a contact?

Treat it as a contact until someone answers a question. The bot's first job is to turn it into a lead, or confirm it is cold, within the first few minutes.

How many qualifying questions are too many?

Four is enough to separate the stages. Each added question loses some people, and agents can ask the rest during the viewing booking call.

Should a cold lead ever reach an agent?

Only if they ask. A cold lead who says "can someone call me" is no longer cold by our rule. Otherwise let the bot send the next brochure and re-score on any reply.

Can I use a Google Form for the capture step?

You can, but it has no hidden fields in the way you need and no webhook without extra scripting. A builder with webhooks and URL-filled fields saves you that work.

Next step

Write down your own cold, warm and viewing-ready definitions as example answers, one row each, for your next launvh. Then build the capture form from the template and send a test lead through to the webhook. If you want the whole flow running, with Arabic and English qualification, brochures, viewing booking and agent handoff, the Dubai real estate WhatsApp bot is a fixed-scope build at $1,500 setup plus $299 a month for the care plan.