Off Plan Lead Qualification Bot for Dubai Real Estate Brokerages
An off plan lead qualification bot for Dubai brokerages: qualifies PropertyFinder and Bayut leads in Arabic and English, books viewings, hands off to agents.
It's 9:40pm on a Thursday. A lead comes in from a PropertyFinder ad for an off-plan tower in Dubai Marina, submitted by someone in Riyadh who wants unit details, payment plan and a viewing slot. The listing agent is asleep. By the time anyone replies at 9am Sunday (weekend gap included), the lead has messaged three other agencies and already booked a viewing with one of them.
That gap is where off-plan enquiries die. Brokerages selling to Gulf, South Asian and European buyers get leads at all hours from PropertyFinder, Bayut and Meta ads, but junior agents can only respond during office hours, in one language, one lead at a time. An off plan lead qualification bot closes that gap by answering in Arabic or English within seconds, asking the same four qualifying questions every time, and handing a ready-to-close lead to the right agent instead of a cold contact.
This guide walks through what the Dubai Real Estate WhatsApp Bot does, how it's built, what it costs, and what a brokerage needs to have ready before kickoff.
What Dubai Real Estate WhatsApp Bot actually does
It's a bilingual WhatsApp bot, built on the WhatsApp Cloud API, that sits between your lead sources and your agents. When a lead comes in from a portal or ad, the bot opens a WhatsApp conversation, asks four qualifying questions (budget range, purchase purpose — investment or end-use, preferred handover timeline, and financing status — cash or mortgage), sends the relevant brochure or brochures automatically, and offers to book a viewing slot. If the lead sends a voice note instead of typing, the bot transcribes it using Whisper so nothing gets missed. Once qualified, the lead is routed to an agent on a round-robin basis with the full conversation history attached, so the agent isn't starting cold.
It is not a chatbot that tries to close the sale. It replaces the slow, inconsistent first contact — the "hi, thanks for your enquiry, can you tell me a bit about what you're looking for" exchange that currently depends on whichever agent happens to be free — with something instant, consistent in both languages, and logged.
How it works, step by step
- Lead source connects. New enquiries from PropertyFinder and Bayut arrive by email notification (these portals don't expose an open lead API, so we parse the notification email or an exported CSV); Meta lead-ad forms connect directly via webhook.
- Bot opens the WhatsApp conversation. Using an approved WhatsApp message template, the bot messages the lead's number within seconds, in the language the enquiry was submitted in (Arabic or English), introducing itself as the brokerage's assistant.
- Four-question qualification. The bot asks about budget, purpose, timeline and financing status, one at a time, accepting free text or voice notes.
- Voice notes get transcribed. Any voice-note reply is run through Whisper and turned into text in the conversation log, so agents can read the exchange rather than replay audio.
- Brochure and listing delivery. Based on the answers, the bot sends the matching project brochure, floor plans or listing PDF already on file for that development.
- Viewing booking or handoff. The bot offers available viewing slots (or, if the lead prefers, just asks to be called) and hands the qualified conversation to the next agent in the round-robin queue, with the full transcript.
- Daily operation and reporting. Each week, the brokerage gets a lead report showing volume, qualification rate and response times; template wording and flows get updated as campaigns change.
Trigger: New Bayut lead — Ahmed K., interested in Marina Vista, submitted 11:47pm Bot: مرحباً أحمد، شكراً لاهتمامك بمارينا فيستا. هل يمكنني أن أسألك بعض الأسئلة السريعة لأرسل لك التفاصيل المناسبة؟ (Hi Ahmed, thanks for your interest in Marina Vista. Can I ask a few quick questions to send you the right details?) Customer: Sure Bot: ما هي الميزانية التقريبية؟ (What's your approximate budget?) Customer: [voice note, 14 seconds] Action: Whisper transcribes — "around 2.5 million dirhams, maybe a bit more for a good unit" Bot: شكراً. هل هذا للاستثمار أم للسكن؟ (Thanks. Is this for investment or to live in?) Customer: Investment Bot: هل موعد التسليم المفضل لديك خلال 2025 أم بعد ذلك؟ (Is your preferred handover 2025 or later?) Customer: 2026 is fine Bot: وهل الشراء نقدي أم عبر تمويل بنكي؟ (Cash purchase or mortgage financing?) Customer: Mortgage Action: Sends Marina Vista brochure PDF + payment plan sheet Bot: هل تود حجز موعد لمعاينة الوحدة النموذجية هذا الأسبوع؟ (Would you like to book a viewing of the show unit this week?) Customer: Yes, Saturday afternoon Action: Lead marked qualified, viewing slot Saturday 3pm logged, handed to Agent Fatima (next in round-robin) with full transcript
Before and after
| Situation | Before | After |
|---|---|---|
| Lead arrives outside office hours | Sits unanswered until next business day | Bot opens conversation within seconds, in Arabic or English |
| Lead sends a voice note | Agent has to find time to listen to it later | Transcribed automatically into the conversation log |
| Qualifying questions | Asked inconsistently, sometimes skipped under time pressure | Same four questions asked every time |
| Brochure requests | Agent manually finds and sends the right PDF | Sent automatically based on the listing the lead enquired about |
| Assigning leads to agents | Ad hoc, sometimes the same agent gets overloaded | Round-robin handoff with transcript attached |
| Tracking lead volume and response time | Rarely measured, anecdotal at best | Weekly lead report from the bot |
What it costs and what is included
| Item | Price | Notes |
|---|---|---|
| One-time setup | $1,500 | WhatsApp Cloud API setup, Meta verification, bilingual bot build, lead ingestion, CRM sync |
| Monthly care plan | $299/month | Flow updates, message template re-approvals, weekly lead report, ongoing support |
| WhatsApp Cloud API usage | Billed by Meta directly | Per-conversation pricing set by Meta, paid by the client |
| Whisper transcription usage | Billed by model provider directly | Usage-based, paid by the client |
| CRM (Bitrix24 / Zoho / HubSpot) subscription | Client's existing plan | We sync into whatever CRM you already run |
There is no lock-in: the setup fee covers the build and go-live, and the monthly plan can be paused or cancelled — you keep the bot and the WhatsApp number either way. The payback logic is straightforward: a brokerage that currently loses even a handful of qualified off-plan leads a month to slow response typically recovers more than $299 in commission value from a single closed unit, though results depend entirely on your lead volume and closing rate.
Delivery timeline
Day 0: Kickoff
Discovery call to confirm lead sources (PropertyFinder, Bayut, Meta ads), current CRM, brochure inventory, and WhatsApp Business account status.
Days 1-6: Build
WhatsApp Cloud API setup and Meta Business verification submitted; bilingual qualification flow built and tested; brochure library mapped to listings; CRM sync configured; agent round-robin queue set up.
Days 7-9: Testing
Test leads run through both languages, voice-note transcription checked, template messages submitted for Meta approval (this step has variable turnaround, which is why it starts early).
Day 10: Go-live
Bot goes live on the brokerage's WhatsApp number; team walkthrough on reading the lead report and reassigning the round-robin queue.
What you need to have ready
- A WhatsApp Business number not already in personal use, for Cloud API registration
- Access to your Meta Business Manager account for verification
- Login access to your PropertyFinder and Bayut portal accounts (for email lead notifications) or agreement to forward lead CSVs
- CRM login (Bitrix24, Zoho or HubSpot) with permission to create a sync integration
- Brochure PDFs and floor plans for the developments you're currently marketing
- A list of agents to include in the handoff round-robin, with their WhatsApp numbers
- Sign-off on the Arabic and English wording used in qualifying questions and templates
- Confirmation of your data residency and consent requirements, if you operate under a compliance policy stricter than Meta's default
Doing it yourself vs done-for-you
| Factor | DIY (WhatsApp Business app + manual replies) | DIY (no-code chatbot builder) | Done-for-you (this system) |
|---|---|---|---|
| Time to set up | Minimal, but no automation | Days to weeks learning the tool | 10 days, we build it |
| Bilingual support | Depends entirely on staff availability | Possible but needs manual translation and testing | Built in from day one |
| Voice-note handling | Agent listens manually | Usually unsupported | Whisper transcription included |
| Lead source integration | Manual copy-paste from portal emails | Requires webhook/API setup skills | Configured for you |
| CRM sync | Manual entry | Often needs a paid integration add-on or Zapier-style workaround | Native sync included |
| Ongoing maintenance | Whoever's free, when they're free | Falls on one person who set it up | Covered by the $299/month care plan |
| Best for | Very low lead volume, single agent | Technically comfortable teams with time to spare | Brokerages with steady portal/ad lead flow who want it running reliably |
Compliance and risk notes
- WhatsApp message templates must be approved by Meta before use for outbound qualification messages; unapproved template wording can get flagged and delay delivery. This is a platform policy matter, not legal advice.
- Consent: leads submitting enquiries via PropertyFinder, Bayut or Meta ads should already be consenting to follow-up contact, but brokerages should confirm this against their own portal terms and any applicable data protection framework (e.g. UAE PDPL) rather than assume.
- Voice-note transcription involves sending audio to a third-party model provider; brokerages with strict data-handling policies should review that provider's data terms before enabling this feature.
- Data residency: lead data flows through Meta's WhatsApp Cloud API and your chosen CRM's infrastructure; confirm where each stores data if your brokerage has residency requirements.
- Meta can suspend WhatsApp Business accounts for template misuse or spam complaints, so message frequency and opt-out handling matter and should be reviewed periodically.
- None of the above is legal advice; brokerages with specific regulatory obligations should confirm requirements with their own counsel.
Mistakes buyers make
- Skipping Meta Business verification early. It can take longer than expected; starting it on Day 0 rather than Day 5 avoids delaying go-live.
- Assuming the portal has a lead API. PropertyFinder and Bayut don't expose one publicly, so lead ingestion is via email parsing or CSV — plan for that, not a live API feed.
- Not preparing brochures in advance. If PDFs for active listings aren't ready before the build, the bot has nothing to send when it qualifies a lead.
- Treating the bot as a closer. It qualifies and hands off; agents still need to do the actual selling and relationship building.
- Ignoring the weekly lead report. The report is only useful if someone reviews it and adjusts agent assignments or campaign spend based on it.
FAQ
Does this work with PropertyFinder and Bayut leads directly?
Yes, but since neither portal offers an open lead API, we ingest leads via email notification parsing or a CSV export you provide. Meta lead-ad forms connect via a direct webhook instead.
Can it handle Arabic voice notes as well as text?
Yes. Whisper transcribes voice notes in Arabic or English into text, which is logged in the conversation and readable by the handling agent.
What happens if a lead doesn't want to answer all four questions?
The bot moves on gracefully and hands the lead to an agent with whatever information was gathered rather than pushing for complete answers, since incomplete-but-fast beats a lead going cold.
Do we need our own WhatsApp Business number?
Yes, and it needs to be a number not already tied to a personal WhatsApp account, since it's registered separately on the WhatsApp Cloud API for your brokerage.
Is there a contract or lock-in?
No. The $1,500 setup is one-time, and the $299/month care plan can be paused or cancelled at any time — you keep the bot and number regardless.
How is this different from a generic WhatsApp chatbot tool?
It's built specifically around off-plan real estate qualification: the four-question flow, brochure-matching logic, agent round-robin and portal lead ingestion are pre-built for this use case rather than something you'd configure from scratch in a generic builder.
Next step
Email support@bharataisaathi.com or message https://wa.me/917735268199 with your WhatsApp Business number, your current lead sources (PropertyFinder, Bayut, Meta ads) and your CRM, and we'll confirm a kickoff date. Full scope and pricing are on the offer page, and our general process is on the how we work page. Bharat AI Saathi delivers this live within 10 days of kickoff.
Dubai Real Estate WhatsApp Bot
Third-party platform and model usage billed to you directly. No lock-in. Live in 10 days.