An off-plan lead nurture sequence for Dubai brokerages: what to send, when, and how to automate it without spamming
Short answer: A nurture sequence is a planned set of follow-up messages sent to a lead over days or weeks until they book a viewing, say no, or go quiet. For off-plan (buying a property still under construction from a developer) I split leads into investors and end-users, send a first message within minutes, follow with useful material such as the payment plan, area context and handover timeline, and pause the whole sequence the moment the lead replies, books or opts out. The cadence below is my own recommended design, not a proven benchmark. Messages outside WhatsApp's 24-hour window need an approved template and the person's consent.
Off-plan buyers take weeks or months to decide, and most agents follow up from memory for three days and then stop. You want a sequence that keeps useful contact going without turning into spam, and that never talks over an agent who is already in a conversation.
I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.
Why off-plan leads need a sequence, not a diary reminder
A buyer who enquires about an off-plan project is rarely ready that day. They compare developers, payment plans and handover dates, talk to a partner or an adviser abroad, and come back. If the only follow-up is an agent's memory, the lead gets two messages and then silence, while a competitor keeps showing up with useful information.
You will see claims that most sales need five or more follow-ups, or that a quick reply makes you many times more likely to convert. I could not find a primary source for those numbers, so I do not build on them. The argument here is simpler: a planned sequence costs less than an agent's time, and stop rules keep it from becoming a nuisance.
Before you send anything: consent, the 24-hour window and Dubai rules
This is general information, not legal advice. Confirm with the relevant authority or a lawyer.
- WhatsApp opt-in. The WhatsApp Business policy, set by Meta (the company that owns WhatsApp), says you may only contact people on WhatsApp if they gave you their number and you have their opt-in permission. Record the consent text, date and channel in your CRM (the system where you keep leads and clients). See the WhatsApp Business API guide.
- The 24-hour window. When a lead messages you, a 24-hour customer service window opens and restarts each time they write. Inside it you can send normal replies. Outside it you can only send approved message templates. Design the sequence so the first day sits inside the window, and later touches use templates, email or a call.
- Cost. Meta charges per delivered template message by category and country. Per its rate card effective 1 October 2026, a UAE marketing message costs AED 0.2115 and a utility message AED 0.0576. Meta changes rates on the first day of a quarter, so check the current card before budgeting.
- Marketing message rules. TDRA, the UAE telecoms regulator, says marketing text messages need prior explicit consent, a free unsubscribe option and sending between 07:00 and 21:00. The UAE telemarketing resolution (Cabinet Resolution 56 of 2024) defines telemarketing to include marketing messages on social media apps, so keep WhatsApp marketing to people who asked for it, inside sensible daytime hours, with a way to stop.
- Cold owners and investors. Dubai Land Department (DLD) Circular 02-2026 bans brokerage offices from contacting property owners or investors directly to offer, market or buy property, unless the office can show a documented prior transaction. It is about unsolicited contact. Your enquiry leads are a different case, but do not add bought or scraped lists to a sequence.
- Advertising material. Off-plan marketing in Dubai needs a DLD advertising permit (Trakheesi, the permit number system) and a QR code on ads. Use brochures and payment-plan PDFs from the developer's approved material, and check anything unusual with your compliance lead.
Split the list first
A single sequence for everyone is how nurture turns into spam. Capture these at enquiry or on the first call, and store them as CRM fields:
- Investor or end-user (someone who will live in the property).
- Cash or mortgage.
- Budget band in AED.
- Language (English, Arabic, Russian and so on).
- Timeline to buy.
Budget thresholds are yours to set. Some brokers use bands like under AED 1 million, 1 to 3 million, 3 to 10 million and above, and give any lead above their top-priority threshold a call task instead of another message.
The investor sequence, day by day
This is my suggested design. Adjust the days after you see your own reply data. Placeholders in square brackets are for you to fill from the developer's approved material.
| When | Channel | What it does | Stop if |
|---|---|---|---|
| Minute 0 to 5 | WhatsApp (inside window) or reply on the portal | Greets by name, names the project, offers a 10-minute call | Lead replies |
| Day 1 | WhatsApp or email | Sends the payment plan PDF and floor plans for the unit type they asked about | Reply, booking, opt-out |
| Day 3 | WhatsApp template or email | Area context: nearby projects, handover date, what is around the site | Same |
| Day 6 | Call task for the agent | A person phones. Not another message | Call connects |
| Day 10 | Handover timeline and payment milestone summary, labelled as the developer's published plan | Same | |
| Day 21 | WhatsApp template | Inventory or price update, only if the developer has actually released one | Same |
| Day 45, then quarterly | Short market note; invite to reply if plans changed | Opt-out |
Never let a message state expected yield or guarantee returns. If an investor asks, an agent answers, using documented figures from the developer. For updates to overseas buyers after the sale, see AI for investor communication.
The end-user sequence, day by day
End-users care about different things: where the school and commute are, the layout, when they can move in, and how the mortgage works. Same skeleton, different content:
- Minute 0 to 5: greeting, project name, offer of a call or a viewing at the sales gallery.
- Day 1: floor plans and a short list of the layouts that match their family size.
- Day 3: community and amenities, commute times to named places (from a map, not guessed).
- Day 6: agent call, ask about timeline and financing.
- Day 10: mortgage steps with a link to a DLD fees calculator so they can see total cost of purchase.
- Day 21 and then monthly: a viewing invitation or a launch of the next phase.
The launch-week version: 72 hours
When a project launches, decisions compress. Replace the spread-out schedule with three touches in 72 hours: instant greeting, the payment plan and unit availability on day 1, and an agent call on day 2. Anyone who has not engaged by day 3 goes back to the steady investor or end-user schedule. A launch weekend can bring in far more leads than your agents can call, so the sequence handles the first contact while agents work the most promising names.
Stop rules: when the sequence pauses and who takes over
Stop rules matter more than start rules. A sequence that carries on after the lead replied is the quickest way to annoy a buyer. Pause everything when any of these happens, in this order of priority:
- The lead opts out. Stop all marketing contact and record it.
- An agent logs a call or a message to the lead.
- The lead replies on any channel.
- A viewing or call is booked.
- The lead says "not interested" or "already bought".
When a sequence pauses, create a task for the assigned agent so a person takes over. The software should never talk over a human conversation.
Triggering the sequence from pipeline stages
Tie each sequence to a stage in your CRM, so a move triggers a change. A typical off-plan pipeline runs: New, Contacted, Qualified, Viewing, Offer or reservation, SPA (the sale and purchase agreement, the main contract), Payment plan active, Handover. Moving a lead to Contacted starts the sequence, Viewing pauses it, and Payment plan active switches the lead to a different set of messages: milestone reminders, which are messages about a purchase the buyer already made and which may fit Meta's utility category (check the category rules before you send). Many CRMs can do this natively. For the choice of system, see a CRM for off-plan sales. If you use GoHighLevel, a marketing automation and CRM platform, or Bitrix24, the pipeline automation is built in, and the question is configuration, not tooling. Compare them in Bitrix24 vs GoHighLevel.
How software and AI help with a nurture sequence, and where an agent steps in
Software does the timing, the pausing and the record keeping. AI helps with three jobs:
- Drafting. Given the project fact sheet and the lead's answers, an AI assistant such as Claude can draft each message in English or Arabic. A person approves each template once, and the template is reused.
- Reply detection. A model can read an incoming reply and tell whether it is positive, a question, a "stop", or an out-of-office message, so the sequence pauses correctly and hot replies go straight to an agent. It will occasionally misread a message, so check a sample every week.
- Summaries. After a thread, an AI summary tells the agent where the lead stands.
What stays human: pricing, availability, returns, and anything that sounds like advice. An agent calls the hot ones within minutes. I build these automations around a brokerage's own CRM, but the same logic can be set up in most CRMs without custom code.
To try drafting yourself, give Claude the developer's fact sheet and this instruction: "Write five WhatsApp messages for an off-plan investor lead, for Day 1, 3, 10, 21 and 45. Use only facts from the sheet. No yield claims, no guarantees, no urgency tricks. Each message ends with an easy way to say stop." Then have an agent edit the result.
Worked example: 150 leads from one launch weekend
The figures below are made up to show the mechanics, not results anyone should expect. A brokerage with three agents collects 150 leads over a launch weekend. All 150 get the minute-0 greeting. The CRM tags 60 as investors, 70 as end-users and 20 with missing answers. The 20 get one qualifying message. By Monday, 38 have replied, so their sequences are paused and the agents hold those conversations. The other 112 move on to the day-1 payment plan message, and agents get call tasks for 15 leads flagged as above the top budget band. If the remaining 112 leads each receive four template messages outside the window, that is 448 messages. At the AED 0.2115 marketing rate, the sending fee is about AED 94.75, before any platform fee. That is cheap next to the spend that produced the leads. The more useful number on Monday is how many replies, viewings booked and sequences paused.
Mistakes that turn a nurture sequence into spam
- Messaging the same lead from the portal, WhatsApp, email and the agent's personal phone in the same hour.
- Sending PDFs that only one agent holds, and are out of date.
- Letting the sequence run after a viewing is booked.
- Sending in the wrong language.
- Reusing a consent given for one project to market another.
- Counting message volume as success. Count replies and viewings.
How I'd approach this
Write two short sequences, not ten. Build the stop rules before the messages. Start with the CRM you already pay for, and add AI only for drafting and reply detection (what AI automation costs a Dubai brokerage). Review replies, opt-outs and viewings booked after a month and change the days to match what you see.
Questions people ask
How many follow-ups should I send an off-plan lead?
There is no proven number. The "five touches" statistic circulating online has no primary source I could find. Use a short planned sequence, stop on any reply, and let an agent call the engaged ones. Review your own results monthly.
Can I send the payment plan PDF on WhatsApp automatically?
Inside the 24-hour window after the lead messages you, yes, as a normal reply. Outside it, you need an approved template and the person's consent. Use the developer's approved material. See the payment plan template.
Do I need permission before sending WhatsApp messages to a portal lead?
Meta's policy requires opt-in before you contact people on WhatsApp, and the opt-in must make clear they agree to hear from your business. Collect and record it in the CRM. This is not legal advice, so confirm with a lawyer. See the WhatsApp broadcast guide.
What if the lead replies in Arabic or Russian?
Store the language as a CRM field and route to a matching agent. An AI assistant can draft in the lead's language, but a fluent speaker should check the templates before first use.
When should the sequence stop and an agent call?
Stop on any reply, booked viewing, logged agent contact, "not interested" or opt-out. Create a call task when a lead is above your priority budget band, asks about price, or reads your messages repeatedly without replying.
Is this different for secondary-market buyers?
Yes. Resale buyers want specific listings, current availability and viewings, so the sequence is shorter and driven by property alerts. The consent and stop rules are the same.
How do I remind existing buyers about payment milestones?
Treat these as service or utility messages about a purchase they made, pulled from the developer's payment schedule, and keep them separate from marketing. Check message categories on Meta's pricing page and keep the schedule in your CRM. See AI follow-up for off-plan buyers.
Sources
- WhatsApp Business Messaging Policy
- Meta for Developers: WhatsApp Business Platform pricing
- TDRA: frequently asked questions
- DLD: Real Estate Ad Permit (Trakheesi) and QR code
- DLD/RERA Circular 02-2026 on communication with property owners
- Property Finder Partner Hub: broadcasts that won't get you blocked
- Groovy Web: off-plan lead management in Dubai (vendor)
- SleekFlow: strategies beyond WhatsApp broadcast for UAE real estate (vendor)