Integration, planned
Bayut and Dubizzle
There is no native Bayut connection in Treasury yet. Here is how a Bayut or Dubizzle enquiry reaches the right brand today, and what the native connection would change.
The claim
Bayut and Dubizzle enquiries reach Treasury today by forwarding them to your brand's lead webhook. A native sync is planned, and it is first in the queue.
Today
How a portal lead arrives now
- Forward the enquiry
- Point the mailbox that receives Bayut and Dubizzle enquiries at your brand's lead webhook, or post it from whatever tool already reads that mailbox.
- One brand only
- The webhook secret belongs to one brand, so an enquiry can only ever be written into that brand's pipeline and never into a sibling's.
- Never filed twice
- Send the portal's own reference and a repeated delivery updates the record rather than creating a second one.
- Answered on arrival
- The owner is alerted, the answering clock starts, and a WhatsApp follow-up can begin without anybody opening a screen.
- Reported by source
- Every lead keeps the source it came in on, so the month's reporting shows which portal produced deals and which produced noise.
Planned
Why Bayut is first
Bayut's push API is reported to carry Dubizzle on the same connection, which means one piece of work covers two of the three portals a Dubai brokerage cares about. That is why it sits at the front of the queue rather than Property Finder.
A native connection would bring the enquiry in structured rather than parsed from an email: the listing, the enquiry type, the portal's own lead id, and the call and project enquiries an email forward never carries at all. No date, and we will not invent one.
Being straight about it
Where this leaves you today
We are not a Bayut push API partner. Competitors are, and if a native connection is the deciding factor you should buy one of them, and we will say so on the call.
What we give you today is everything after the lead arrives: one system holding every brand you run, WhatsApp with the reply logged on the record, an answering clock that moves the ignored ones, and a price that does not rise when you hire.
Asked and answered
Questions
- Does Treasury sync with Bayut today?
- No, not natively. Enquiries reach Treasury by being forwarded to your brand's lead webhook, which works today.
- Does Dubizzle need separate work?
- Bayut's push API is reported to carry Dubizzle on the same connection, so the native work should cover both. Today both arrive the same way, by forwarding.
- Will forwarded leads be deduplicated?
- Yes, when the portal's own reference travels with them. Without it, two deliveries of the same enquiry look like two people.
- Which portal connection ships first?
- Bayut, because it is reported to carry Dubizzle as well. Property Finder follows it.
Request access
Tell us how many brands you run and who needs to see them. We will walk you through the system with your names in it, not ours.
We reply within one working day. Already a customer? Sign in at app.treasurycrm.com.