Knowledge Base
Integrating Property Finder with Salesforce: leads, listings and agent assignment
What actually happens between a buyer tapping “enquire” and an agent picking up the phone — and where Dubai brokerages lose deals in between.
A Property Finder Salesforce integration moves enquiries from the portal into your CRM automatically, attaches them to the right listing and assigns them to an agent under rules you control. Property Finder exposes a lead API that CRM platforms connect to, so the enquiry arrives as a structured record rather than an email somebody has to read and re-type.
That much is standard. The difference between an integration that pays for itself and one that quietly adds a step is in the decisions below.
The problem this solves, stated plainly
Here is a sequence most Dubai sales directors will recognise.
At 22:10 a buyer enquires about a two-bedroom in Dubai Marina. The portal emails the brokerage’s shared inbox and shows the lead in the agent dashboard. The agent assigned to that listing is asleep. At 22:40 the same buyer enquires about a similar unit listed by a competitor, who responds within four minutes because their system paged the duty agent.
By the time your agent opens the portal app at 08:30, the viewing is already booked elsewhere. Nothing was technically lost — the lead is sitting there, correctly recorded. It just lost.
Speed of first response is the single operational variable a brokerage can change without spending more on portals. An integration is the mechanism; the routing and escalation rules are the actual product.
What arrives, and what does not
A portal enquiry typically carries the enquirer’s name, contact details, the listing reference and a timestamp. Some channels carry more than others, and the gaps matter:
- Form enquiries — the richest, usually including a written message that tells you intent
- Call enquiries — a phone number and a listing reference, no message, no email address
- WhatsApp enquiries — arrive on a phone, not necessarily in the CRM, unless specifically handled
The WhatsApp gap is the one that surprises brokerages most often, and it deserves its own treatment. See WhatsApp lead handling for Dubai brokerages in Salesforce.
Plan the data model around the leanest channel, not the richest. If your deduplication logic assumes an email address, every call enquiry becomes a duplicate contact.
How it works in Salesforce
The records involved
Four objects carry the workflow:
- Portal Enquiry (custom) — the raw inbound event: portal, channel, listing reference, timestamp
- Lead — the unqualified person, created only if no match exists
- Contact — the known person, once qualified
- Listing (custom) — the property, holding the portal reference the enquiry points at
Keeping Portal Enquiry separate from Lead is what allows a returning buyer to generate a fifth enquiry without generating a fifth lead. It also preserves the per-portal history you need later for cost per lead and cost per deal reporting.
The integration flow
- The portal delivers enquiry data to an integration layer.
- Fields are normalised — particularly phone numbers, which arrive in inconsistent formats and break matching if stored as received.
- The layer matches against existing Contacts and Leads on phone first, then email.
- A Portal Enquiry record is created and linked to the matched person and to the Listing.
- Assignment rules fire.
- An SLA timer starts.
Step two is where most of the hidden work sits. A UAE mobile number can
arrive as +971 50 123 4567, 0501234567 or
971501234567. Stored raw, those are three different people.
Normalise to a single format at the point of entry, not later in a
report.
Agent assignment logic
Four approaches, and most brokerages end up combining two:
| Rule | Works when | Fails when |
|---|---|---|
| Listing owner | Agents specialise by building or community | The owner is on leave or already at capacity |
| Round robin | Agents are interchangeable | Enquiry needs specific language or area knowledge |
| Community or area | Teams are structured geographically | A listing sits on a community boundary |
| Existing relationship | The buyer is already known | Matching fails, and it silently reverts to another rule |
Whichever you choose, define the fallback first. The rule that matters is not “who gets this lead” but “what happens when that person does not act on it”.
Response SLA and escalation
A workable pattern for a brokerage running extended hours:
- Timer starts at enquiry creation, not at agent login
- First escalation notifies the agent again after a set interval
- Second escalation reassigns to a duty agent or team lead
- Out-of-hours enquiries route to whoever is actually on duty, not to the listing owner by default
The out-of-hours rule is what would have saved the 22:10 enquiry above. It is also the rule most often left out of an initial scope, because it requires the brokerage to decide who is on duty — a management decision, not a technical one.
Listings in the other direction
Enquiries come in; listings go out. Publishing from Salesforce means the property is maintained once and pushed to the portal on a schedule, rather than being typed into each portal’s back office separately.
Two practical points. First, a listing cannot go live in Dubai without a valid advertising permit number, so the permit field belongs on the Listing record and should block the outbound feed when missing or expired. Second, feed rejections need to surface in Salesforce as visible errors — a listing silently dropped from a feed is a listing nobody is marketing.
The mechanics are covered in publishing listings from Salesforce to property portals.
Three failure modes worth designing out
The agent who left
When an agent leaves, their open enquiries and their listings both need reassignment. Listings are usually remembered. Enquiries sitting in an inactive user’s queue are not, and they keep ageing.
The duplicate that is not a duplicate
Two family members share a phone number. Aggressive matching merges them into one record and the second buyer disappears. Match on phone, but flag rather than auto-merge when the names differ substantially.
Reporting that measures the wrong thing
“Leads per portal” counts enquiries. It does not tell you whether those enquiries were worth having. Until Portal Enquiry records connect through to closed Opportunities, portal spend decisions are being made on volume rather than outcome.
Frequently asked questions
How do Property Finder leads get into Salesforce?
Through Property Finder’s lead API, which delivers enquiry data to your CRM in near real time. An integration layer normalises the fields, checks for an existing person and creates the appropriate records.
Can enquiries be assigned to agents automatically?
Yes. Assignment can follow the listing owner, a round robin, community or language, or an existing client relationship — with a fallback rule for when the assigned agent does not respond in time.
What happens to enquiries that arrive outside working hours?
With routing rules in place, out-of-hours enquiries go to whoever is on duty rather than waiting for the listing owner. Without them, the enquiry sits until the next working day.
Does the integration stop duplicate leads?
It can, provided phone numbers are normalised to a consistent format before matching. Matching on email alone misses call enquiries, which rarely carry an email address.
Can we publish listings to Property Finder from Salesforce?
Yes, through a scheduled feed generated from a Listing object. The advertising permit number should be a required field, so a non-compliant listing never reaches the feed.
How long does this take to implement?
The first portal integration takes the longest because it establishes the normalisation and matching layer. Subsequent portals reuse it. Data cleanup, not the integration itself, is usually what extends a timeline.
Talk it through
Tell us which portals you use and how your team is structured, and we will come back with scope, timeline and an indicative cost. Get in touch — the first assessment is free.
Let us look at your lead flow
Send us your portal setup and agent count. We will come back with what an integration would involve, how long it would take and roughly what it would cost — free, and with no obligation.