You move the team off personal numbers onto one business number running on the WhatsApp Business Platform, where the brokerage owns the number, every conversation is stored centrally, and agents work from a shared inbox. Meta supports keeping the WhatsApp Business app running on the same number during the change, so threads are not lost.
A brokerage that cannot read its own client conversations does not own its client relationships. The agent does.
Key takeaways
- A 24-hour customer service window opens when a WhatsApp user messages or calls a business, and resets each time they message again. Inside it a business can send any service message type. "When the window closes, you can only send pre-approved template messages instead" (Meta for Developers, Send messages, checked 7 September 2026).
- Templates must be approved before use. "Templates must have a status of APPROVED before they can be sent", review can take up to 24 hours, and every template is categorised as authentication, marketing or utility (Meta for Developers, Template fundamentals, checked 7 September 2026).
- Meta moved to per-message pricing on 1 July 2025, replacing conversation-based pricing. "All non-template messages are free" inside an open window, and utility templates delivered inside an open window are free (Meta for Developers, Pricing, checked 7 September 2026).
- You do not have to abandon the WhatsApp Business app to adopt the Platform. Meta's coexistence onboarding syncs history so a business can share "all messages sent or received within 180 days of the time when the business was onboarded onto Cloud API" (Meta for Developers, Onboard WhatsApp Business app users, checked 7 September 2026).
- One WhatsApp account links to up to four additional devices (WhatsApp blog, 25 April 2023). That is device sharing, not a team inbox, and it does not scale past a handful of people.
- Dubai recorded over 270,000 transactions worth AED 917 billion in 2025 (Dubai Land Department, via Dubai's Public Debt Management Office). The conversations sitting on agents' phones are the brokerage's most valuable undocumented asset.
Why is an agent's personal WhatsApp number a business risk?
Because the relationship is attached to the number, and the number belongs to the agent.
When a Dubai buyer saves an agent's mobile, they are saving a person rather than a company. Every subsequent enquiry, referral and resale goes to that person. If the agent resigns on Sunday and starts at a competing brokerage on Monday, the phone travels with them, and so does two years of client history, offer thresholds and viewing feedback.
Four exposures follow.
The client list walks out. No export, no handover, no leverage. The brokerage cannot even list who the clients were.
Nothing is auditable. If a client disputes what they were told about a payment plan or a price, the only version of events sits on a phone the brokerage does not control.
Nobody can cover. An agent on leave or unreachable means their pipeline stops, because nobody else can see the conversations to reassign them.
Data responsibility sits nowhere. Client data is processed on personal handsets under no policy at all. UAE businesses are subject to federal personal data protection rules published at u.ae, and "it was on Ahmed's phone" is not a control.
None of this is an argument about trust. Good agents leave for good reasons. The problem is that the brokerage has no copy.
What is the difference between a personal number, the WhatsApp Business app and the WhatsApp Business Platform?
These are three different products with three different ownership models, and most brokerages conflate the second and third.
| Personal number | WhatsApp Business app | WhatsApp Business Platform (Cloud API) | |
|---|---|---|---|
| Intended for | Individuals | "The small business owner" (whatsappbusiness.com) | Businesses messaging at scale through software |
| Who controls the number | The agent | Whoever holds the SIM and the handset | The brokerage, through its Meta Business Portfolio |
| Where conversations live | The agent's device | The device, plus up to four linked devices | Your systems, via the API and webhooks |
| Team access | None | Device linking, up to four additional devices | Unlimited agents through a shared inbox in your software |
| History when someone leaves | Leaves with them | Leaves with the handset unless linked | Stays in the brokerage's system |
| Automation | None | Basic greeting and away messages, quick replies, labels | Programmatic routing, assignment, automated replies |
| Messaging outside 24 hours | Not applicable | Manual, one to one | Pre-approved templates only |
| Message cost | Free | Free | Per message from 1 July 2025; non-template messages free in an open window |
| Setup required | A phone | A phone and the app | Meta Business Portfolio, WhatsApp Business Account, a Meta app, and software to connect it |
| Realistic team size | 1 | 1 to 4 | 5 and above |
Platform requirements from Meta's Cloud API get-started guide; pricing and window rules from Meta's pricing documentation. All checked 7 September 2026.
The practical read: the Business app is a better phone. The Platform is infrastructure. A four-agent brokerage can survive on the app. A twelve-agent brokerage cannot, because device linking runs out at four and there is no way to route, assign or audit anything.
What actually happens to conversation history when an agent leaves?
This is where most brokerages discover the problem, and by then it cannot be fixed retrospectively.
On a personal number or an unlinked Business app number, chat history is on the agent's device. WhatsApp is device-centric by design. When the handset leaves the building the history leaves with it, and there is no administrative console that retrieves it. The brokerage's copy is whatever the agent typed into the CRM, which is usually a name, a budget and the word "interested".
On the Business Platform the position reverses. Messages arrive at your system through webhooks and are stored there. Deactivating an agent removes their access and not the conversation, so the next agent opens the same thread and reads what was actually promised.
There is a middle case. If a number has been onboarded to Cloud API through Meta's coexistence route, history is synchronised: "all chat messages in the most recent 6 months can be synchronized", specifically all messages sent or received within 180 days of onboarding (Meta for Developers, checked 7 September 2026). Six months is recoverable. Three years is not.
What are template messages and the 24-hour window?
These two rules govern everything a brokerage can do on WhatsApp, and misunderstanding them is why teams get templates rejected or costs wrong.
The window opens when the user contacts you. Meta's documentation is explicit: "When a WhatsApp user messages you or calls you, a 24-hour timer called a customer service window starts. If the user messages or calls you again before the timer expires, the timer resets to 24 hours." Inside the window you can send any service message type. Outside it, only approved templates.
| What you want to send | When it is allowed | What it costs |
|---|---|---|
| Free-form text, images, documents, floor plans | Only inside an open 24-hour window | Free. "All non-template messages are free" |
| Utility template (viewing confirmation, payment reminder) | Inside or outside the window | Free when delivered inside an open window; charged when delivered outside |
| Authentication template | Inside or outside the window | Charged when delivered outside an open window |
| Marketing template (new launch, price list) | Outside the window, once approved | Charged when sent |
| Anything at all, after a free entry point conversation | Within 72 hours | "All messages are free for 72 hours" in that window |
All rules and quotations from Meta's WhatsApp Business Platform pricing documentation and send messages guide, checked 7 September 2026. Per-message pricing replaced conversation-based pricing on 1 July 2025.
The operational consequence is simple. A buyer who enquires at 22:40 has opened a 24-hour window, so you can reply freely inside it. A buyer who last messaged eleven days ago has not, so reaching them needs an approved template, and a marketing template is charged. Build a library of utility templates before you need them, because approval can take up to 24 hours and nobody wants to wait for that during a launch.
How do you migrate a team onto one inbox without losing threads?
Run it as a project with a date, not as a policy announcement. Seven steps, in order.
1. Decide the number. Use a new business number, or port the brokerage's existing main line. Never adopt an individual agent's personal number as the company number, because you inherit the ownership problem you are trying to solve.
2. Create the Meta assets. A Meta Business Portfolio, a WhatsApp Business Account and a Meta app with the WhatsApp use case, per Meta's get-started documentation. Complete business verification early, because it gates everything else.
3. Pick the inbox before you migrate. The Platform is an API and does nothing on its own. You need software that receives the webhooks, assigns conversations and stores history against the client record, ideally the same system holding your pipeline.
4. Preserve what you can. If agents run the WhatsApp Business app, use Meta's coexistence onboarding to sync the most recent 180 days, and ask agents to export individual chats for live deals before cutover. Older history on personal numbers is gone.
5. Get templates approved in advance. Draft utility templates for viewing confirmations, document requests, payment plan reminders and follow-ups, and submit them a week before go-live.
6. Set assignment rules on day one. Every inbound message needs an owner within a defined time, exactly as portal leads do. Without a rule, a shared inbox is a WhatsApp group with better branding and it fails the same way. See where portal leads actually get lost.
7. Redirect the old numbers. For 60 days, agents keep an away message on personal numbers pointing clients to the business line. Clients migrate themselves if you tell them once and remind them once.
Expect resistance, because top agents understand exactly what they are giving up. The counter-argument that works is coverage: leads get answered while they are on a flight, on leave or in a viewing, and their commission stops depending on their thumbs.
What should you measure once WhatsApp is centralised?
Four numbers, none of which exists before centralisation.
Median time to first reply, split by hour of arrival. Dubai enquiries land at all hours, and a nightly median exposes what a daily average hides.
Unassigned conversation count, checked daily. Any message with no owner is an outage.
Conversations per agent per day, which shows whether your best closer is drowning in unqualified traffic.
Percentage of deals with a complete conversation record. If a Won deal has three messages against it, the real conversation happened elsewhere and you have not finished migrating.
WIYO runs WhatsApp inside the same workspace as the lead pipeline, so an enquiry from any of 11 lead-source connectors and the WhatsApp thread that follows sit on one record, under the seven-stage pipeline and RERA-aware workflows. The wider approach is set out at WhatsApp CRM for Dubai brokerages and in WhatsApp for Dubai real estate agents.
Frequently asked questions
Can several agents use one WhatsApp number?
On the WhatsApp Business app, only through device linking, which supports up to four additional devices per account. For a team inbox with assignment, routing and shared history you need the WhatsApp Business Platform connected to software that receives the messages. The app is a better phone; the Platform is infrastructure.
What is the difference between WhatsApp Business and the WhatsApp Business API?
The WhatsApp Business app is a free application aimed at small business owners, running on a handset. The WhatsApp Business Platform, or Cloud API, is Meta-hosted infrastructure that delivers messages to your systems through webhooks. The app stores conversations on a device. The Platform stores them wherever your software does.
Do we lose our chat history if we move to the Business Platform?
Not necessarily. Meta's coexistence onboarding synchronises all messages sent or received within 180 days of onboarding onto Cloud API, so roughly six months carries over from the WhatsApp Business app. Older history on personal numbers is not recoverable, which is the argument for migrating sooner.
What is the 24-hour rule on WhatsApp?
A 24-hour customer service window opens when a user messages or calls your business, and resets each time they message again. Inside it you can send free-form messages. Once it closes you can only send pre-approved template messages, categorised as utility, authentication or marketing.
How much does WhatsApp Business Platform messaging cost?
Meta charges per message as of 1 July 2025. Non-template messages inside an open customer service window are free, as are utility templates delivered inside an open window. Marketing templates are charged when sent. Rates vary by country and category, so check Meta's current rate card for the UAE.
Should agents keep their personal numbers for work?
No, and the reason is commercial rather than disciplinary. Client relationships attached to a personal handset leave when the agent does, cannot be audited in a dispute and cannot be covered during leave. Move to one business number and let agents keep their personal phone personal.
How long does migration take?
Business verification with Meta and template approval are the two variables. Template review can take up to 24 hours per template, and verification can take longer. A brokerage that prepares its Meta assets, chooses inbox software and drafts templates in advance can usually go live within a fortnight.
Want every agent's WhatsApp, portal leads and pipeline on one record before your next resignation? Book your free demo at wiyo.ae.
Written by Shaffay Bajwa, Founder of WIYO. Software engineer, five years in UAE real estate technology. Published by WIYO L.L.C-FZ, Trade Licence 2649536.01, Meydan Free Zone, Dubai. Published 7 September 2026.
Written by
Shaffay Bajwa
Founder & CTO at WIYO · Software engineer, 5 years building in the UAE real estate market.
Want to see WIYO live?
30-minute personalised demo with live data from your existing portals.
