Knowledge Base
Integrating Dubizzle Property with Salesforce: handling volume and owner-listing leads
More enquiries is not the same as more business. What a brokerage actually needs from a Dubizzle integration is triage before assignment.
A Dubizzle Property Salesforce integration brings portal enquiries into the CRM the same way the other portals do. The difference is what arrives. Dubizzle is a general classifieds platform covering property alongside cars, jobs and goods, operating across all the emirates, where listings come from owners and landlords as well as agents and agencies.
That mix produces higher enquiry volume with wider variation in intent. Routing all of it straight to agents, the way you might with a smaller and more qualified stream, burns the time of the people you most need selling.
What “high volume” does to a sales floor
Volume changes behaviour, not just workload. Three effects show up consistently:
- Selective response. Agents start choosing which enquiries to call back, usually by gut feel. The selection is invisible and unmanaged.
- Response times drift. Averages stay acceptable while the tail gets worse, and the tail is where lost deals live.
- Portal blame. “Dubizzle leads are rubbish” becomes received wisdom, which may be true, partly true, or a triage failure. Without data nobody can tell.
The point of an integration here is not faster delivery of everything. It is sorting, so that agents spend their time on the enquiries worth their time.
How it works in Salesforce
Triage before assignment
Insert a qualification step between capture and routing. Enquiries arrive as Portal Enquiry records, get scored, and only then reach an agent:
- Capture. The enquiry is recorded with portal, channel, listing reference and timestamp — nothing is discarded.
- Automated checks. Contactability, duplicate status, whether the enquirer has engaged before, whether the listing is still active.
- Scoring. A simple band — high, standard, low — beats an elaborate model nobody trusts.
- Routing. High-band enquiries go straight to agents; standard-band may go to a queue; low-band gets an automated response and waits for a reply.
Keep the low band. Filtering enquiries out of the CRM entirely destroys the data you need to judge the portal later, and occasionally the low-band enquiry replies and turns out to be real.
Scoring inputs that are actually available
Scoring only works on fields you reliably receive. Practical inputs for a UAE brokerage:
| Signal | What it suggests |
|---|---|
| Enquiry channel | A written message usually carries more intent than a bare call-back request |
| Repeat enquirer | Several enquiries across listings suggests an active search |
| Price band of listing | Determines which team should handle it, not whether it is good |
| Time of day | Affects routing, not quality — see the out-of-hours rule below |
| Previous outcome | A contact who viewed and did not proceed is still a live prospect |
Resist scoring on nationality, language or anything that reads as a proxy for them. Beyond the fairness problem, it produces a model that encodes an agent’s assumptions rather than observed behaviour.
Routing across emirates
Dubizzle covers all the emirates, so enquiries arrive for areas your team may not cover. Decide explicitly what happens to an Abu Dhabi enquiry when your coverage is Dubai: route to a named person, refer it out, or close it with a polite response. Leaving it unrouted means it sits in a queue nobody owns.
Owner and landlord listings: a lead source, not just competition
Because Dubizzle carries listings from owners and landlords directly, brokerages tend to see it as competition for the same buyers. There is a second reading.
An owner marketing a property themselves is a potential instruction. A landlord listing a unit directly is a potential property management client. Neither is a buyer lead, and both are worth recording — as a different record type, with a different owner and a different follow-up rhythm.
In Salesforce terms, that means distinguishing enquiry purpose at capture: buyer or tenant enquiry versus a seller or landlord conversation. Mixing the two in one pipeline produces conversion reporting that makes no sense, because they convert on completely different timescales.
Whether prospecting owner listings suits your firm is a commercial judgement, and in some markets a regulated one. The CRM point stands either way: if you do it, it belongs in the same system as everything else.
Out-of-hours and weekend volume
Classifieds traffic skews towards evenings and weekends, when people are browsing rather than working. An enquiry at 21:30 on a Saturday is normal here, not an edge case.
Two rules handle most of it:
- Duty routing. Out-of-hours enquiries go to whoever is on duty, not to the listing owner by default.
- Acknowledgement, then handover. An immediate automated acknowledgement buys time without pretending an agent has replied — provided a real response follows within the SLA.
Automated acknowledgements are worth doing carefully. A templated message that reads like a bot, followed by silence for eleven hours, is worse than no message at all.
What to measure
For a high-volume portal, lead count is the least useful number. More telling:
- Share of enquiries reaching each score band
- Conversion to viewing by band — does your scoring predict anything?
- Response time at the 90th percentile, not the average
- Cost per viewing and cost per deal, not cost per lead
The second line is the one that keeps a scoring model honest. If high-band enquiries do not convert better than standard-band, the model is decoration. Full method in measuring portal ROI in Salesforce.
How this differs from the Bayut integration
Both portals sit under the same group and can share a normalisation layer, but the CRM work differs. Bayut’s demands centre on the listing verification lifecycle, covered in integrating Bayut with Salesforce. Dubizzle’s centre on triage and routing at volume.
Building both with identical rules is the common mistake. Enquiries should land in the same records; what happens next should not be the same.
Frequently asked questions
How do Dubizzle Property leads get into Salesforce?
Through an integration that captures each enquiry as a structured record with portal, channel, listing reference and timestamp, then applies matching and routing rules before an agent sees it.
How do you stop high-volume portals overwhelming agents?
By inserting a qualification step between capture and assignment. Enquiries are scored on available signals and routed by band, so agents receive the ones worth immediate attention rather than everything at once.
Should low-quality enquiries be filtered out completely?
No. Record them, route them differently. Filtering destroys the data you need to evaluate the portal, and low-band enquiries occasionally turn out to be genuine.
What about enquiries from owner or landlord listings?
They are a different kind of opportunity — a potential instruction or property management client rather than a buyer. Capture them as a separate record type with their own follow-up rhythm.
Can Dubizzle and Bayut share one integration?
They can share a normalisation layer so enquiries land in the same records. Routing and qualification rules should differ, because lead volume and character differ between the two.
How should weekend and evening enquiries be handled?
With duty routing rather than default assignment to the listing owner, and an immediate acknowledgement followed by a real response inside the agreed SLA.
Talk it through
If enquiry volume is outrunning your team, tell us what you are seeing and we will come back with what a triage layer would involve. Get in touch — the first assessment is free.
Let us look at your enquiry volume
Tell us roughly how many enquiries you receive and how they reach agents today. We will come back with scope, timeline and an indicative cost.