Knowledge Base
Integrating Bayut with Salesforce: verified listings, lead capture and WhatsApp enquiries
Bayut rewards verified listings with better ranking — but verification expires, and keeping it current is a CRM problem before it is a marketing one.
A Bayut Salesforce integration does two jobs. It brings enquiries into the CRM as structured records, and it gives you somewhere to manage the listing verification lifecycle that Bayut’s ranking depends on. The second job is the one brokerages underestimate.
On Bayut, a listing can carry a Checked badge and, above that, a TruCheck™ badge. Getting from one to the other requires an agent to physically visit the property and photograph it through Bayut’s agent app, with the app’s camera only accessible within 500 metres of the unit. Verification is therefore a scheduled field task — and field tasks that nobody schedules do not happen.
Why this is different from other portal integrations
Most portal integrations are about inbound leads. Bayut’s is about inbound leads and an outbound operational workflow with its own state machine.
The sequence, as it affects a brokerage in Dubai:
- The listing needs a valid advertising permit before it goes live at all.
- Entering the permit number, where the details match the listing, produces the Checked badge.
- An agent visits the property and uploads current photographs through the app to activate TruCheck.
- Verified listings rank ahead of unverified ones, which changes how many enquiries the listing generates.
- For off-plan listings, Checked and TruCheck carry a 45-day validity, so the cycle repeats.
Read that list as a brokerage operations problem rather than a portal feature list. Somebody has to know which listings are unverified, which are approaching expiry, which agent is nearest, and whether the visit actually happened. That is a CRM job.
How it works in Salesforce
Verification status on the Listing record
The Listing object needs fields that reflect the real states, not a single tick box:
- Permit number and permit expiry — the gate before anything else
- Verification stage — none, Checked, TruCheck
- Verification date — when the stage was last achieved
- Verification expiry — calculated where a validity period applies
- Assigned visitor — who is responsible for the physical visit
With those fields in place, three reports become possible: live listings with no verification, verifications expiring inside the next fortnight, and visits assigned but not completed. Without them, the information exists only in the portal’s own dashboard, one listing at a time.
Automating the verification cycle
A workable pattern:
- A listing goes live with permit details recorded.
- If verification stage is still “none” after a set number of days, a task is created for the listing owner.
- Where a validity period applies, a re-verification task is created before expiry rather than after it.
- Completed visits update the stage and date, either manually or by sync.
- A weekly report to team leads lists everything unverified or expiring.
The escalation rule matters more than the reminder. An agent who is behind on visits does not need another notification; the team lead needs to see the backlog.
Enquiries and the records they create
Inbound enquiries follow the same model used across the series: a Portal Enquiry record captures the raw event with portal, channel, listing reference and timestamp, then matching decides whether a new Lead is created or an existing Contact is reused. The mechanics are covered in integrating Property Finder with Salesforce and apply here unchanged.
One Bayut-specific point: because verified listings attract disproportionately more enquiries, lead volume per listing is uneven. Round-robin assignment across agents will not distribute work evenly if two agents hold all the TruCheck listings. Assignment rules should account for listing quality, not just listing count.
WhatsApp enquiries, and where they go
A significant share of UAE portal enquiries arrive through WhatsApp rather than a form. The commercial problem is that a WhatsApp enquiry lands on a phone, which means:
- No timestamp in the CRM, so no response-time measurement
- No record if the agent leaves the company
- No visibility for a team lead reviewing unanswered enquiries
- No connection between the conversation and the eventual deal
Bringing WhatsApp into Salesforce properly is its own piece of work — see WhatsApp lead handling for Dubai brokerages. The point to note here is that if WhatsApp is a large share of your Bayut enquiries and it stays outside the CRM, your portal reporting is measuring the minority of your leads.
Bayut and Dubizzle are related, but not the same problem
Both sit under the same group, and agent tooling increasingly spans the two. That leads some brokerages to treat them as one integration. They behave differently in ways that affect CRM design:
| Bayut | Dubizzle Property | |
|---|---|---|
| Emphasis | Verified, agent-listed inventory | Classifieds heritage, broader listing base |
| Lead character | Fewer, more qualified | Higher volume, more variable |
| CRM implication | Verification lifecycle tracking | Filtering and triage before assignment |
Handling both through one normalisation layer is right. Assuming they need identical routing and qualification rules is not. The Dubizzle side is covered in integrating Dubizzle Property with Salesforce.
Two mistakes worth avoiding
Treating verification as a marketing task
Verification looks like something the marketing team should own, because it affects visibility. In practice it requires an agent to be at the property, so it is a field operations task with a scheduling dependency. Assign it where the work happens.
Letting the portal be the record of listing status
If verification status only exists inside Bayut’s dashboard, nobody can answer “how much of our inventory is verified?” without counting manually. The CRM should hold the status, whether it is updated by integration or by the agent after a visit. A manually updated field that everyone can report on beats a perfectly synced field that nobody built.
Frequently asked questions
How do Bayut leads get into Salesforce?
Through an integration that delivers enquiry data into the CRM as structured records, linked to the listing they refer to. Enquiries are normalised alongside other portals so routing, deduplication and reporting work consistently.
Can Salesforce track TruCheck and Checked status?
Yes, as fields on the Listing record covering verification stage, the date it was achieved and, where a validity period applies, the expiry date. Tasks and reports are then built on those fields.
What is the difference between Checked and TruCheck?
Checked reflects document and permit verification. TruCheck additionally requires the agent to visit the property and upload current photographs through Bayut’s agent app, which only allows this within 500 metres of the unit.
Do verified listings really get more enquiries?
Bayut ranks verified listings ahead of unverified ones, so they are seen more often. The practical consequence for a brokerage is uneven lead distribution across agents, which assignment rules need to account for.
Can WhatsApp enquiries from Bayut be captured in Salesforce?
Yes, but it requires a deliberate integration. Left alone, WhatsApp enquiries stay on the agent’s phone and never appear in response-time or attribution reporting.
Should Bayut and Dubizzle share one integration?
They can share a normalisation layer, so enquiries land in the same records. They should not share identical routing rules, because lead volume and qualification differ between the two.
Talk it through
If verification tracking or WhatsApp enquiries are the gap in your setup, get in touch. We will come back with scope, timeline and an indicative cost — free, with no obligation.
Let us look at your listing operation
Tell us how many listings you run and how verification is handled today. We will come back with what it would take to manage it from one place.