# Bayut, Property Finder and dubizzle Leads: Capture Every Enquiry Fast

> Portal enquiries in the UAE arrive by email alert, phone call and WhatsApp, not one clean feed. Here is how to capture each route into your CRM and enforce a first-response SLA.

Published: 2026-10-27T04:10:11Z · Source: https://homelead.com/blog/bayut-crm-integration-property-finder-dubizzle-leads

Bayut, Property Finder and dubizzle enquiries reach a UAE brokerage through three routes: an email alert, a call to the number on the listing, or a WhatsApp message. There is rarely one clean feed. The fix is to capture each route into your CRM automatically (an email parser posting to a webhook, a company-owned WhatsApp Business number, and a call webhook), assign the lead within minutes, and treat first-response time as a hard SLA that someone reviews every week.

**Key takeaways**

- A listing feed sends your properties *to* a portal. It does not bring enquiries *back*. Treat them as two separate projects.
- Map each enquiry route (email, call, WhatsApp) to one capture method and test each with a real enquiry before you trust it.
- Put a company-owned WhatsApp Business number and a tracked phone number on listings, never an agent's personal mobile.
- Set a first-response SLA in minutes with automatic escalation, and review the source report by portal every week.

## Why do portal enquiries go missing before follow-up?

The portal counts a lead the moment a buyer taps **Call**, **Email** or **WhatsApp** on your listing. From that second the brokerage owns it, but the three buttons land in three different places:

- **Email** goes to whichever address was registered with the portal, often a listings coordinator's inbox or the listing agent's own mailbox, sometimes under a filter nobody checks after 6pm.
- **Call** forwards to whatever mobile number the listing agent put on the listing, which is usually a personal phone.
- **WhatsApp** opens a chat with that same personal number.

Three things follow. First, nobody can count enquiries: the portal dashboard says 60 leads this week, the CRM says 22, and the difference is unexplained. Second, response time depends on one person's phone; if that agent is on a viewing in Dubai Hills for two hours, the buyer has already messaged three other agents on the same portal. Third, the leads leave with the agent, because the history lives in their WhatsApp.

Owners tend to blame portal lead quality. The sharper question is how many of those enquiries got a useful reply inside 15 minutes. Most brokerages cannot answer it, and that is the real problem. Our guide on [why real estate leads don't convert](https://homelead.com/blog/why-real-estate-leads-dont-convert) covers the downstream symptoms; this article is about the capture step that comes before.

## Listing feed vs lead push: what is the difference?

A listing feed (XML or API) exports your inventory to the portal: photos, price, permit number, agent details. It is outbound. Enquiries come back by a separate path, and that path depends on the portal and the package you are on. Typical options are per-lead email notifications, a leads dashboard with export, call-tracking numbers, WhatsApp buttons, and in some cases a developer API.

Before you configure anything in the CRM, ask each portal's account manager four questions:

1. Which email address receives lead alerts for our account, and can we change it?
2. Is there a leads export, and in what format?
3. Do calls route through a tracking number we can forward to a number of our choice?
4. Which phone and WhatsApp numbers are shown on each of our listings, and who can edit them?

In Dubai, every advertised listing also needs an advertising permit issued through the Dubai Land Department; keep the permit number against the listing in your CRM so compliance checks are quick. The official source is [dubailand.gov.ae](https://dubailand.gov.ae/).

| Enquiry route | What the buyer did | Where it lands by default | How to capture it |
|---|---|---|---|
| Email alert | Tapped Email / Enquire | A mailbox | Parser reads the alert and posts JSON to the CRM's generic webhook |
| Phone call | Tapped Call | The agent's mobile | Tracked or virtual number whose provider pings a call webhook; or CRM app on the agent's Android phone syncing call logs |
| WhatsApp | Tapped WhatsApp | The agent's personal WhatsApp | Company WhatsApp Business number on listings; inbound message auto-creates a lead in a shared inbox |
| Portal dashboard export | Any of the above | Portal only | Scheduled CSV export and bulk import with dedupe on phone number (fallback) |

## How do you capture email enquiries from Bayut, Property Finder and dubizzle?

### Route alerts to a dedicated mailbox

Create one address such as leads@yourbrokerage.ae and register it with every portal. Nobody is expected to read this mailbox; it is a pipe. Keep a human-readable copy going to the team lead if you like, but the CRM should not depend on anyone opening an email.

### Parse each alert and post it to a webhook

Use an email parser (Zapier, Make, or a dedicated parsing tool) with one rule per portal. Each rule extracts name, phone, email, listing reference, message text and portal name, then posts a JSON payload to your CRM's generic webhook. On the CRM side, map those fields once: portal name becomes the lead source, the listing reference or project becomes the sub-source, and the message goes into the first note.

An illustrative payload looks like this:

```
{
  "name": "Fatima A.",
  "phone": "+971501234567",
  "email": "fatima@example.com",
  "source": "Property Finder",
  "sub_source": "PF-884213 / Marina Gate 2BR",
  "message": "Is this still available? Can I view on Saturday?"
}
```

Test with five real enquiries, not sample data. Check that phone numbers arrive in one format (+971 50 vs 050 is the usual mismatch), that the listing reference survives, and that a second enquiry from the same number is flagged as a duplicate rather than silently dropped or silently merged.

### Fallback: scheduled export and bulk import

If the parser is not ready, export the leads list from each portal dashboard daily and bulk-import it with dedupe on phone number and round-robin assignment on import. Treat this as a floor, not a target: a lead that waited until the next morning has usually been answered by someone else.

## How do you capture WhatsApp enquiries from portal listings?

The WhatsApp button on a listing opens a chat with the number shown on that listing. Three decisions follow: which number, who sees inbound messages, and what happens after hours.

- **Which number.** Use a WhatsApp Business (Cloud API) number owned by the brokerage, connected to the CRM. Put it on every listing. Agents can still have personal WhatsApp, but portal traffic should not land there.
- **Who sees it.** A shared team inbox where every inbound message creates a lead automatically, with the number as source. Assignment rules then route it; agents see their own conversations, managers see the team's.
- **After hours.** UAE buyers message at 11pm and expect a reply. A bot that answers from your own brochures and price sheets (availability, price, location, viewing slots) inside Meta's 24-hour customer-service window, classifies the enquiry and hands anything hot to a human keeps the conversation alive until morning. Meta's rules for the 24-hour window and templates are documented at [developers.facebook.com](https://developers.facebook.com/docs/whatsapp/).

The detailed set-up, including templates and the bot, is in our guide to [WhatsApp CRM for real estate](https://homelead.com/blog/whatsapp-crm-for-real-estate).

## How do you capture phone calls from portal listings?

Calls are the most-dropped route because a missed call leaves nothing behind except a number on someone's phone. Two set-ups work:

1. **Tracked or virtual number.** Route the portal's call button (or the portal's own call-tracking number) to a virtual number from an IVR or telephony provider, forwarded to the duty agent. The provider pings your CRM's call webhook on every call, so each call creates or matches a lead and writes a call log with duration and connected/missed status. A missed call becomes a lead with a call-back due, which is exactly the enquiry that used to vanish.
2. **Agents' own Android phones.** If agents answer on their own handsets, the CRM mobile app syncs call logs from the phone, matches numbers to leads, and shows the lead name as a caller-ID popup when a known number calls back. Recordings and AI summaries attach to the lead so the manager can hear what was promised.

Either way, the number on the listing should be one the company controls. When an agent leaves, you change a forwarding rule, not a listing.

## How fast should you respond, and how do you enforce it?

A buyer on Bayut or Property Finder usually sends the same enquiry to several listings in one sitting. The first agent who replies with something useful (a confirmation the unit is available, a price, a viewing slot) sets the frame for the whole conversation. Everyone after that is a comparison.

Design the SLA like this:

- **Define first response.** A human call attempt or a personalised WhatsApp reply. An automatic acknowledgement is fine and worth sending, but it does not count.
- **Pick the minutes.** 15 minutes during working hours is realistic for a staffed team; 60 minutes is the outer limit before the lead is effectively cold.
- **Warn, then act.** The assignee gets a warning before the deadline. On breach, the system should do something without waiting for a manager: notify the manager, flag the lead, or reassign it to someone who is free.
- **Cover the gaps.** A rota per shift, a weekend duty pool, and a rule that routes evening leads to whoever is on duty rather than to the listing agent who went home.
- **Measure weekly.** SLA compliance by agent and by source, next to lead-source effectiveness (volume, conversion, share marked hot). The portal with the most leads is not always the portal with the most viewings.

Our post on [real estate lead assignment software](https://homelead.com/blog/real-estate-lead-assignment-software) goes deeper on rotation strategies; what matters here is that assignment and SLA are configured together.

### Illustrative example: a 12-agent brokerage with 40 enquiries a day

Before: alerts from three portals go to the listings coordinator's inbox, calls go to agent mobiles, WhatsApp goes to personal numbers. The owner sees portal invoices and closed deals, and nothing in between.

After: parser rules post every alert to the webhook with portal as source and listing reference as sub-source; the company WhatsApp number is on all listings with auto-lead creation on; a tracked number forwards calls and pings the call webhook. Leads round-robin within each portal's pool, the SLA is 30 minutes with a warning at 15; on breach the team lead is notified, the lead is flagged and it is auto-reassigned to the duty pool, and the bot covers 9pm to 9am.

What changes is not a percentage but accountability: every enquiry has a timestamp and an owner, the team lead's morning view shows overnight leads with the bot's temperature and status updates and a Next Best Action per lead, and the weekly source report shows which portal produced viewings rather than just enquiries. Budget conversations with portals get easier when you can show that.

### First-response playbook

| Clock | Action | Owner |
|---|---|---|
| Minute 0 | Automatic WhatsApp acknowledgement with agent name and listing reference | System |
| 0 to 15 min | Call attempt; if no answer, personalised WhatsApp with availability and two viewing slots | Assigned agent |
| 15 to 30 min | Warning to agent; second call attempt | Assigned agent |
| 30 min | Breach: team lead notified, lead flagged, reassigned to duty pool if still untouched | System / team lead |
| Day 1 | Shortlist of two or three similar units sent as a collection link | Agent |
| Day 3 | Viewing confirmed or lead moved to a nurture cadence with a dated follow-up | Agent |

## How does Homelead handle UAE portal enquiries?

Homelead's lead sources screen (Settings → Lead Sources) includes a generic webhook with field mapping, so an email parser, Zapier or any outside tool can post Bayut, Property Finder or dubizzle alerts straight in; a partner API key covers vendors and call centres. Every lead carries a source and a lockable sub-source, and the lead-source effectiveness report shows volume, conversion percentage and hot percentage per portal. Duplicates are created, flagged and linked to the original, never dropped. On the listings side, Homelead pushes listings to Property Finder and feeds Bayut and dubizzle, so inventory goes out from the same record the enquiry comes back to.

For WhatsApp, you connect your own number through Meta Embedded Signup inside the panel, run several numbers with an owner per number, and switch on auto-create lead from inbound messages. The shared inbox handles free replies inside the 24-hour window and approved templates outside it. The WhatsApp AI bot is off by default per number, has a dry-run tester, answers from your Knowledge Center, classifies temperature, hands hot buyers to a live agent and can be taken over by any agent with one click.

For calls, an IVR or virtual-number provider's pings create leads and call logs through the IVR webhook. Agents on Android get call-log sync every 15 minutes and on app open, a caller-ID popup with lead name and assignee, and AI transcript, summary and disposition on the lead after the call.

Assignment offers five auto-assign strategies per source, rotation teams with shift windows and a Rotation Log explaining each pick. The first-response SLA sits in Settings → Configuration → Leads: set the minutes (default 60, range 1 to 1,440), get a warning before the deadline, and choose breach actions: notify assignee, escalate to manager, flag red or auto-reassign, with an optional daily digest and alerts by in-app, push and Telegram. The panel runs in English and Arabic, and UAE accounts are invoiced in AED. See the [India and UAE markets page](https://homelead.com/markets) for the UAE-specific fields.

## Which mistakes keep portal enquiries leaking?

- **Treating the listing feed as the integration.** The feed went live, so the owner assumes leads are flowing in. Check the lead path separately.
- **Personal numbers on listings.** Every enquiry becomes the agent's property, not the company's.
- **Counting the auto-reply as a response.** The SLA clock should stop on a human action.
- **No weekend rota.** Friday evening enquiries sit until Monday in some brokerages.
- **Never reconciling portal counts.** Once a week, compare the portal dashboard total with CRM leads by source. A gap means a route is not captured.
- **Skipping the phone-format check.** Half-captured numbers are the quiet killer of WhatsApp follow-up.

## Weekly checklist for the team lead

- Portal lead count vs CRM lead count per portal, with any gap explained.
- SLA compliance by agent and by source.
- Missed calls from the tracked number that still have no call-back note.
- Overnight WhatsApp conversations the bot handled, and which ones were escalated.
- Listings whose displayed phone or WhatsApp number is not the company number.
- Source report: enquiries, viewings and offers per portal, to inform next month's listing spend.

If you are still choosing a system, our guide to [choosing a real estate CRM for Dubai brokerages](https://homelead.com/blog/real-estate-crm-dubai-how-to-choose) lists what to test in a demo, and the [lead follow-up system article](https://homelead.com/blog/real-estate-lead-follow-up-system) covers what happens after the first response.

To see the generic webhook, WhatsApp inbox and SLA set-up on your own listings, book a demo at https://homelead.com/#demo or WhatsApp +91 72400 44472.

## Frequently asked questions

### Does connecting a listing feed to Bayut or Property Finder bring leads into my CRM?

No. A listing feed sends your inventory to the portal. Enquiries come back through separate channels, usually email alerts, calls to the listed number and WhatsApp, and each of those needs its own capture route into the CRM.

### What is the simplest way to get portal email alerts into a CRM?

Register one dedicated mailbox with every portal, run an email parser rule per portal that extracts name, phone, listing reference and message, and post the result to the CRM's generic webhook with the portal as source. Test with real enquiries and check phone-number formats.

### Should the WhatsApp number on listings be the agent's or the company's?

The company's. A WhatsApp Business (Cloud API) number connected to the CRM lets every inbound message create a lead in a shared inbox, keeps history when an agent leaves, and allows a bot to answer after hours.

### How do I capture phone calls from portal listings?

Route the portal's call button or tracking number to a virtual number whose provider pings your CRM's call webhook, so every call (including missed calls) creates or matches a lead with a call log. Alternatively, agents' Android phones with the CRM app can sync call logs and show caller ID for known leads.

### What first-response SLA is realistic for a UAE brokerage?

Fifteen minutes during staffed hours, with a hard outer limit of 60 minutes. Count only a human call or personalised WhatsApp reply as a response, warn the agent before the deadline, and escalate or reassign automatically on breach.

### How do I know which portal is worth the spend?

Compare enquiries, viewings booked and offers per portal in the CRM's source report each week, not just the enquiry count on the portal dashboard. The portal with the most leads is often not the one producing the most viewings.