Skip to content

Property Finder leads: reply, qualify, route and follow up

Property Finder leads and Bayut enquiries need one owner, a WhatsApp reply that names the listing, and a follow-up that is on the record.

Property Finder leads and Bayut leads get a reply on the WhatsApp number already on the listing, a short qualification, and one owner chosen by community, language and who is free. Capture the enquiry from the portal feed or, if there is no API, from the alert email. Answer while the buyer is still comparing agencies, and put a next action on the record the same day, because a buyer who hears nothing, or who hears from two agents, does not become a viewing.

This is the path we run with Dubai brokerages on the number and the CRM they already have. The dated lines are what we read in October 2026. Where a rule is legal, the brokerage’s counsel decides it.

How Property Finder leads arrive

A Property Finder lead is someone who acted on a live listing: a WhatsApp tap, a call, or an email alert. A missed call buried under live chats waits until lunch.

Property Finder’s partner hub tells a brokerage to put a valid WhatsApp number on the user who should receive the taps, and it allows one central number if a person is watching it. That setting makes the button work, and the desk still has to assign the chat, qualify the buyer and book the viewing.

On that page Property Finder describes a test of 10 brokerages in Dubai and Abu Dhabi. After WhatsApp leads were turned on, the page reports a 44% rise in mobile leads and a 16% rise in leads overall, with call leads still arriving. The figure counts how many enquiries show up and says nothing about reply speed, so more taps on a slow desk make a larger unread pile.

WhatsApp, a call, or an email

  • WhatsApp tap. The buyer messaged the number on the listing. The thread is open, so reply in that thread, from that number.
  • Call. You have a number and a time, sometimes a recording. Call them back, since the call did not open a WhatsApp chat.
  • Email alert. You have a name, a phone and a listing reference. Reply by email or by phone.

Property Finder’s Lead Tracker is the portal’s app for opening those leads and running reports, next to Price Finder. It shows what arrived. The owner, the questions and the follow-up live in your CRM.

When too few enquiries arrive, the problem is the listing: the community, a verified listing, and an exclusive mandate.

What the Bayut leads API sends

A Profolio user requests the Leads API by emailing support@bayut.com, because Bayut does not hand you a URL to paste. Name the types in that email. A WhatsApp-only feed is a separate request to the same inbox. Ask for a test lead and match it to the listing reference before you treat a working listing sync as proof that the lead feed is on.

Bayut’s help article of 30 January 2024 lists six deliveries:

  1. Call logs
  2. Phone views
  3. Email leads
  4. SMS clicks
  5. WhatsApp views
  6. WhatsApp leads

Call logs, email leads and WhatsApp leads are conversations, or an attempt at one. A phone view, a WhatsApp view or an SMS click means someone looked. Attach a view to a person you already have. If the phone does not match, leave the view as a signal and do not assign an owner or start a chase. Store the type on every row, so that when the CRM counts all six and Profolio counts fewer, the type is how you make the two reports agree.

When you email Bayut, ask how often you may pull. Pull often enough that a 9pm enquiry is in the CRM before the morning meeting, and do not inherit a middleware interval you have not read.

The marketplace is a different queue

The New Project Leads Marketplace is a hub of off-plan buyers. Bayut’s article of 18 February 2026 says an admin opens the contact of someone who submitted interest in new projects on Bayut and dubizzle. Keep those names on their own list, with their own cost, outside the listing-enquiry count. A seller lead is a homeowner who wants an instruction. The questions further down are for someone who asked about a unit you are already marketing.

When the email is the only feed

Some accounts never get an API. Read the name, phone, listing reference and portal out of the alert email, and write the same fields. Mark the record “email”, because a template change breaks the parse. Each morning, compare yesterday’s alert count with the CRM, and when they drift, check the parser before you coach anyone. Dubizzle can send another copy of the same person. The phone match further down covers that copy. This article does not describe Dubizzle’s fields.

ArrivalWhatsApp windowFirst move
WhatsApp tap on the listingOpens when they message youReply in that thread. Name the listing. Ask one question.
Call or missed callStays closedCall back. Start WhatsApp only with opt-in and an approved template.
Email alertStays closedReply by email or phone. Same WhatsApp rule as a call.
View or SMS clickStays closedAttach it to a matching phone. Leave it as a signal if nobody matches.
Marketplace contactStays closed until they message youIts own list. An off-plan buyer you opened, kept apart from listing taps.

The first reply on WhatsApp

Reply from the number the listing shows. Personal SIMs take the thread with the agent when they leave, and the buyer meets a new name on the next message. One brokerage number can front the listing, and the routing behind it still picks a human. Owner reports go on a second number, so a buyer who asked about a flat does not receive a broadcast. That split is how we build brokerage systems.

WhatsApp’s business policy allows a free-form reply inside a 24-hour customer service window, which opens and resets when the user messages you. Outside it, only an approved template can go. You may contact someone only after they gave you their number and opted in to hear from you again. A buyer who tapped WhatsApp and wrote has done that for this conversation. A number lifted from an email alert has not opted in, so we start WhatsApp from an email or a missed call only after the brokerage accepts that enquiry as opt-in, and only with a template already approved. Until then the first touch is a call or an email.

The same policy says automation inside the window needs a direct path to a person, including a handoff in the chat. The first reply can leave before an agent is free, as long as a person can take the thread.

As of October 2026 that free-form reply is a service message. Meta’s pricing documentation, updated 30 September 2026, gives each business number 1,000 service messages a month from 1 October 2026. Unused ones do not roll over, and messages after the tier are charged. With no payment method, the page says those messages stop once the tier is used. Read the UAE rate before you budget night replies. Templates outside the window are charged on their own category.

What the first message may say

Name the community and the bedrooms as they stand on the live listing. Say an agent who covers the area will continue, and ask one question. State availability only after a person has confirmed it today. Leave out any price that is not on the live listing, and hold even that price while the listing is under review. Leave out the viewing time, the service charge, the transfer fee, the mortgage figure and any second unit. Hold other stock for the agent, because the buyer keeps a message that names the wrong unit.

After hours

An 11pm WhatsApp tap still gets that reply. The window is open because the buyer wrote, and a 9am answer loses the chat to whoever answered overnight. The night message says an agent who covers the community will continue when the desk opens, names the hour, such as after 9:30, and does not offer a morning viewing.

An 11pm email or missed call has no WhatsApp thread yet. Log it, name an owner, and have a person call or email when the desk opens. A template at 11pm to a number that never wrote to you means the brokerage is starting the chat, which is the case the opt-in rule covers.

We have not found a published share of Dubai portal enquiries that arrive after hours. Pull that share from your own portal report before you staff a night rota. The automatic reply can run at night, provided the copy does not pretend a person is sitting there.

Keep the automatic reply and the human reply as two timestamps. The 2011 Harvard Business Review article by Oldroyd, McElheran and Elkington is the study other posts cite for a multiple. The public page says many companies reply too slowly, without printing the multiples, and the firms were not Dubai brokerages. Publish your own median by the hour the enquiry arrived.

Which questions qualify the lead

One question per message, in the language of the message they sent.

  1. Buy or rent, when the listing does not already say.
  2. Budget, as a range.
  3. Bedrooms, when they are asking about an area rather than one unit.
  4. Timeline: this month, inside three months, or later.
  5. Cash or mortgage, for a buyer, after the four above. A person reads the answer, and the thread does not estimate a loan.

Stop once budget, bedrooms and timeline are filled, and hand the thread to the agent. Write intent, budget, bedrooms, timeline, language, community, listing reference, source and enquiry type on the lead. The stage stays short of qualified while those three are empty. Once an agent is typing, stop the questions.

Who should get the lead

A rota across the whole company sends a Downtown Arabic enquiry to an English-speaking agent who lists in JVC, and the clock then runs out on someone who was never going to answer in Arabic.

The order we use

  1. The agent on the listing, if they still work with you, cover the language, and are under their cap of open leads.
  2. An agent who covers that community and that language, and who is marked free.
  3. The duty agent who is free and covers the language.
  4. Round-robin only among people who already passed the community and language filter.

If nobody matches, the team lead owns it, since a shared inbox has no name on it. The rule has to be readable as community, language, cap, and the person who is free.

When the portal user has left

Leads follow the portal user on the listing until someone changes that user. After an agent leaves, the old login still receives enquiries and the portal still shows them as assigned. Point the listing at a current user the same day, and send any unmatched portal user to the default owner. An agent at their cap does not take the next lead, even with their name on the listing, so the lead passes to the next person who fits, with a note that it moved for capacity.

Duplicates across the two portals

Match the phone first. If there is no phone, match the email. Store one person and both sources, and take the source from a fixed list: Property Finder, Bayut, Dubizzle, Meta, Website. “PF”, “property finder” and “PropertyFinder” become three rows in a report. A second listing is another interest on that person, with its own reference, and it stays with the agent who already owns them, unless that agent has left.

A view stays a signal. A marketplace contact stays on the marketplace list, because nobody tapped a listing. Merge when the phone or the email matches, and leave an ambiguous pair for a person. Merging two different buyers is a worse miss than a duplicate.

One buyer, the same night

Walk this through on a sample, with no client behind it. At 21:40 a buyer sends an Arabic WhatsApp from the button on a Dubai Marina two-bed on Property Finder. The listing number receives it, so the window is open. The reply names the bedrooms and the community, asks whether they are buying or renting, and does not claim the unit is free. The record stores source Property Finder, the listing reference, language Arabic, community Marina and the reply time. The listing agent covers Marina and Arabic and is under the cap, so the lead is theirs, and the handoff waits on budget, bedrooms and timeline.

At 08:10 the same phone emails through Bayut about another Marina unit. The phone matches, so source Bayut and the second reference are added and the owner stays. If that agent has logged nothing by 10:00, the lead returns to the pool with reason “no contact”. Skip that agent on the way back, and keep the Arabic thread.

Follow-up and lead repooling

A buyer who said “in three months” and then went quiet is the usual case. Daily nudges get muted, and a lead with no date on it is how the portal budget leaks.

A cadence the desk can keep

  1. On arrival. If the window is open, send the reply above. If it is closed, a person calls or emails. Either way, timestamp the record.
  2. While they answer. One qualification question at a time. At budget, bedrooms and timeline, the agent takes the thread.
  3. Same day, if they answered and then stopped. The agent sends one message with two times to talk, and does not add a new price or a second unit.
  4. Next working day, if they never replied and the window has closed. One approved template, and only with opt-in on the record. Without opt-in, the next step is a call.
  5. Day 3. Send one message, and only after they qualified and asked for options. Availability still comes from a person.
  6. Day 7. End the short chase. If they named a month, move them to that month, then a quarterly check. If they named nothing, close the lead with a reason.

Templates wait on days the desk is closed, because a reply needs a person. The night acknowledgement to someone who just wrote does not wait, because they asked for that message.

The long cycle is the month they gave, then a quarter. Those templates pause on days nobody is there to take a reply, the same control we use on owner campaigns.

Sending the lead back to the pool

Send the lead back on a clock, and write the reason on the record.

  • During desk hours, no logged attempt within two hours: back to the pool, reason “no contact”.
  • After hours, with only the acknowledgement sent, and still no human attempt by 10:00 on the next day the desk is open: same reason.
  • The agent declines, or they are over the cap: back immediately, reason “declined” or “over cap”.
  • The owner has left, or the community was wrong: back immediately, reason “left” or “wrong community”.

Skip the previous owner. Keep the transcript, both sources, the qualification fields and every attempt, so the next agent can see why it returned.

A lead leaves the active list when someone is working it, when a person disqualifies it with a reason, or when the day-7 rule closes it.

What to check each week

Review one screen, once a week:

  • Median minutes to the automatic reply, and to the first human message, by portal and by hour of arrival.
  • Share of new leads with a named owner inside a minute.
  • Leads with no next action.
  • Leads with nothing logged at 24 hours and at 48 hours.
  • Leads returned to the pool, by reason.
  • How often a new enquiry matched a person you already had.
  • Share that reached qualified with budget, bedrooms and timeline filled.
  • Viewings by source. Treat taps with no viewings as a response problem until these numbers say something else.

When a channel goes quiet, check the pipe before you coach anyone.

  • WhatsApp taps stopped on Property Finder: the number on the user is blank, is not on WhatsApp, or is not the number your WhatsApp account uses.
  • Bayut shows the lead and the CRM does not: that type was never on the API request, the pull stopped, or the test lead was never confirmed.
  • Emails stopped: the parser is reading a mailbox you retired.
  • Leads keep landing on someone who left: the portal user was not changed.

Where the listing permit fits

The Trakheesi permit belongs to the advertisement. Someone who already asked about that listing is in a conversation, and a broadcast of the unit to people who did not ask needs the permit for that unit. Filing steps, and the unit match before either portal will accept the listing, are in how to get a Trakheesi permit for a listing. With no permit on the record, the agent says so, and the number from the flat next door stays out of the chat.

If yesterday’s enquiries are still split across a personal WhatsApp, a shared inbox and a morning export, we can put this path on the number and the CRM you already use. You own what we build. It goes live in 3 to 6 weeks, and the setup fee comes back if it does not work in 45 days. The first call is a look at where those enquiries sat. Start from the real estate work or from what we set up.

Frequently asked questions

How fast should you reply to a Property Finder lead?

Keep two clocks: when the automatic reply went, and when a person wrote. While the desk is open, get a person on the thread within a few minutes, and try again within two hours if the buyer goes quiet. No Dubai study we found turns five minutes into a multiple. The 2011 Harvard Business Review article does not print those multiples. Measure your median by the hour the enquiry arrived.

Can I request the Bayut leads API for WhatsApp only?

Yes. Bayut's help centre says a Profolio user requests the Leads API by emailing support@bayut.com, and that a WhatsApp-only feed is a separate request to the same address. Name the types you want. A listing connection does not turn the feed on. Ask Bayut for a test lead after they enable it, and match that test to the listing reference before you trust the pipe.

Why do my Bayut leads look low quality?

Check the clock and the type before you blame the portal. A buyer who wrote to three agencies at 10pm and heard from you at 9am looks uninterested. Count phone views and WhatsApp views apart from email leads. Split the six types the API sends, then read median time to a human reply by the hour the enquiry arrived.

What is a Bayut seller lead?

A seller lead is a homeowner who wants an agent to take the instruction. A buyer who tapped a listing you already published is a different contact. Put the homeowner on a list whose next step is a valuation conversation, and skip the buyer questions on budget, beds and timeline. Sending a landlord to the agent on duty for sales enquiries wastes both of them.

Are WhatsApp replies to portal leads free?

A buyer message opens a 24-hour window, so you can send a free-form reply instead of a template. From 1 October 2026, Meta's pricing page gives each business number 1,000 service messages a month and charges after that. An email lead does not open the window. Check the live rate card for the UAE, and keep a payment method on the account so replies continue after the free tier.

What if the same buyer enquires on both portals?

Match the phone number before anyone is assigned. Keep Property Finder and Bayut on one record, note each listing, and leave the lead with the agent who already owns the person. A second unit is another interest on that same buyer. Open a second record only when the phone and the email both fail to match. Two agents calling the same person that morning means the match did not run.

Filed under

  • Property Finder
  • Bayut
  • WhatsApp
  • Lead routing

Let's find your first workflow

Book a 30-minute call. We'll map the workflow costing you the most hours and tell you honestly whether AI can fix it.

Book a 30-min call