DNCR, PDPL and RERA: the three rules behind every automated call and WhatsApp message
Speed is the easy part. The part that decides whether automation helps a Dubai brokerage or puts it at risk is quieter: who may be contacted, what may be said, and what happens to the buyer's data afterwards. Three sets of rules answer those questions.
The direct answer
Automation does not change the rules. It makes breaking them faster.
A human agent who calls a registered number makes one mistake. An automated system that calls a whole list without screening makes the same mistake hundreds of times before lunch. That is why the safeguards come before the speed: screening, consent records, and a script that only quotes verified listings.
The good news is that the same discipline that keeps a brokerage safe also makes its automation better. Clean consent records mean cleaner lists. One record per buyer means no buyer is chased twice. And a script that never guesses means buyers trust the answers they get. This is the safeguards companion to our channel piece: WhatsApp vs phone vs portal — where Dubai real estate leads actually die — and to how fast a Dubai brokerage should reply to a Bayut / Property Finder lead.
The rule we work to: no consent record, no outbound contact. No screening, no campaign. No verified listing, no claim about it. And one “stop” from a buyer ends contact on every channel, permanently.
Rule by rule
What each rule actually requires
Plain language, not legal text — your legal advisers confirm the detail for your brokerage.
DNCR — Do Not Call Registry
Requires: Screen every outbound number before dialling, every campaign, and log the result.
Risk when skipped: Calling a registered number with a marketing message is the fastest way to turn automation into a complaint.
Screening runs before every campaign, results are logged per attempt, and registered numbers are suppressed automatically.
PDPL — Personal Data Protection Law
Requires: Collect buyer data for a clear purpose, keep only what is needed, protect it, and delete it when done.
Risk when skipped: Buyer numbers and conversations scattered across personal phones, with no consent record and no answer to “how did you get my number”.
Consent records with source and timestamp, data kept in the brokerage's own CRM, and documented deletion schedules.
RERA — Licensing and honest advertising
Requires: Licensed agents only, and every claim about a listing must be true and verifiable.
Risk when skipped: An assistant that invents availability, prices, or payment plans — or speaks as if it were the licensed broker.
Answers drawn only from live listings and the approved script; anything unverified goes to a licensed agent.
Calls vs WhatsApp
What changes between a call and a message
The three rules apply to both — but the failure mode is different.
On a call
The buyer can object in real time
A buyer who objects on a call expects the objection to stick immediately, not after a follow-up email. The assistant must recognise an opt-out in plain language, in Arabic or English, confirm it, and end the call gracefully.
Opt-out recognised on the call itself, confirmed, and recorded.
One objection, handled once, remembered everywhere.
On WhatsApp
The thread is the record
WhatsApp threads live on. A buyer who opted out months ago must never be messaged again because a new campaign used an old list. Consent and suppression must travel with the thread, not sit in a separate spreadsheet.
Suppression checked against the live CRM record before every message.
Old lists cannot resurrect opted-out buyers.
On a portal
The enquiry is consent for that enquiry
A Bayut or Property Finder enquiry is permission to answer that enquiry — not permission to add the buyer to every future campaign. Portal replies stay in the portal thread, and further contact follows the same consent and screening rules.
Portal replies answered in-thread; campaigns need their own consent basis.
Portal buyers get answers, not surprise campaigns.
Before you automate
The four checks we run before launch
If any check fails, launch waits. Speed never outranks a failed safeguard.
Check 1
Consent records in place
Every number has a source, a timestamp, and a consent reference before the first automated contact — and a way for the buyer to withdraw it.
No consent record, no outbound contact.
Every campaign starts from a clean, auditable list.
Check 2
DNCR screening tested, not assumed
A test campaign is screened end to end and the suppression is verified, before any real buyer is contacted.
Screening runs before every campaign, not once at setup.
Registered numbers never slip through on a later campaign.
Check 3
Opt-out that works everywhere
One “stop” ends calls, WhatsApp, and follow-ups across all channels, and the suppression is recorded permanently.
Opt-out tested on a live call and a live WhatsApp thread before launch.
A buyer who opts out stays opted out.
Check 4
Script and listings signed off
Your team reviews the Arabic and English flows, the agent's permissions, and which listings it may quote — and signs them off.
Nothing goes live on a draft script.
The assistant says only what your brokerage would say.
The system behind this article: AI Agent for Dubai Real Estate, AI Chatbot for Dubai Real Estate, WhatsApp Automation Dubai, AI Call Agents Dubai, and AI Lead Management for Dubai Real Estate.
Common Questions
Frequently Asked Questions
Next Step
See a compliant setup on your own leads
Book a demo and we will walk through the screening, consent, and script sign-off for your brokerage — before anything is built.
TechMate Solutions FZ LLC, trading as DevMate Solutions · Dubai | Muscat | NY · devmatesolutions.com