CRM for a Dubai broker: portal leads and duplicates
Dubai recorded 11,883 property transactions worth AED 34.8 billion in October 2026, with resale deals up 13% to 5,304: those are Dubai Land Department figures analysed by Property Finder, published on 11 November 2026. Resale is the broker's market: several agencies market the same unit, and in a CRM that turns into duplicate enquiries and an argument over who brought the buyer first.
Where a broker's enquiries come from
A Dubai agency's pipeline arrives through several channels, and each one delivers the contact in a different shape. Bayut, Property Finder and Dubizzle pass on an enquiry tied to a specific advert: a name, a phone number or email, and a listing reference. A call from the portal's tracking number lands in your telephony. The chat goes to WhatsApp, often on an agent's personal handset. The form on your own site drops into a mailbox. Referrals and repeat buyers arrive separately again.
While those channels stay apart, nobody can answer a simple question: how many enquiries came in last week, and for which units. We cover pulling portals, telephony and messengers into one pipeline on our CRM for real estate agencies page.
Why duplicates create themselves
A duplicate in a brokerage database is not a careless agent, it is how the market works. A buyer messages five adverts in an evening and several of them are yours. The same resale unit is advertised by different agencies, so the same person reaches you twice from two listings. He left a phone number on the portal, then wrote from a different number on WhatsApp. The seller, meanwhile, ends up as both a contact and a company.
The expensive part is not holding two records. It is two agents calling the same buyer, quoting different terms, and then splitting the commission through their manager.
What gets configured in the portal
- A duplicate check as the lead is created. Bitrix24 compares phone and email and flags the match before the record goes into the pipeline.
- One phone format. Numbers are normalised to +971..., otherwise the same person written three ways never registers as a duplicate.
- The listing reference as its own field. That shows which advert and which portal produced the enquiry, rather than a generic «web lead».
- An owner rule. If the buyer is already in the database, the enquiry goes to their agent, not to whoever opened the record first.
- A single chat channel. WhatsApp connects to the portal as a channel instead of living on a personal phone that leaves with the employee. See our messengers page for how that works.
What it means for your budget
Portal enquiries are paid for, and a duplicate costs twice: once to the portal, then again in the agent hours spent working one buyer in parallel. In a new project from AED 10,000 the duplicate check, the phone format and the listing field are built in from the start. On a live portal it is usually a few hours at AED 200, or a support plan from AED 1,250 a month for 5 hours, with WhatsApp as a channel at AED 500. The payoff is not licence savings. It is that at month end you can see which portal produced deals rather than calls, and move the listing budget accordingly. Full rates are on the pricing page.
Quick answers
Can duplicates be eliminated completely? Not while several agencies advertise the same unit. The goal is to catch the duplicate as the lead is created and route it to the right agent.
What does setting this up on a working portal cost? Usually a few hours at AED 200, or a support plan from AED 1,250 a month for 5 hours.
Why store the listing reference in the CRM? Without it you cannot tell which portal and which advert produced a deal, only an enquiry.
We'll set up duplicate checks, the listing field and WhatsApp as a channel so every enquiry reaches the right agent
Let us discuss your project
Leave a contact and we reply within a business day. We run a short diagnostic and tell you where to start
