WhatsApp Coexistence in the UAE: keep the number on the phone, put the team on it too
One number, the Business app and the API at once — including the requirement nobody documents.
Every UAE business that has run WhatsApp properly for a few years arrives at the same wall. The number works. An agent has it on their phone. Hundreds of live conversations sit in it. And moving to the API — the only way to put a team on that number — used to mean taking it off the phone entirely. Coexistence removes that choice. This is what it actually does, what it does not, and the requirement that stops most attempts before they start.
Coexistence lets a number run in the WhatsApp Business app and the Cloud API at the same time. Your agent keeps replying from the phone; everything mirrors into a shared team inbox. Meta also releases up to 6 months of that number's existing chats into the API. Requirements: the number must have been on the Business app for at least 7 days, and the setup must be done on a computer — because you scan a QR code with the very phone you are connecting.
What Coexistence actually gives you
Three things, and it is worth being precise, because people expect a fourth that does not exist.
The number stays in the Business app. Nobody has to stop using the phone, no conversation is interrupted, and there is no cut-over evening where the business is offline.
Messages sent from the phone appear in the API. When your agent replies from their handset, that message mirrors into your shared inbox. The team sees the full thread rather than half of it.
Existing chat history is released. After onboarding, Meta replays up to six months of that number's conversations into the API.
What it is not: a complete two-way sync of everything forever. Groups and status stay outside the API. And the history replay is a one-time event at connection, not an ongoing backfill.
The requirements, including the one nobody documents
| Requirement | Detail |
|---|---|
| Time on the Business app | At least 7 days before it can be linked |
| App type | WhatsApp Business app — not personal WhatsApp |
| Facebook Business account | Required, as with any API onboarding |
| Where you run the setup | A computer — with the phone in your hand |
| History released | Up to 6 months, sent after onboarding completes |
That fourth row is the one that matters most in practice, and it is not written down anywhere obvious.
During Coexistence onboarding, WhatsApp displays a QR code that must be scanned using the Business app on the phone you are connecting. If you run the whole flow on that same phone, you would have to scan your own screen. It is not a bug in anyone's software — it is geometry.
We can be specific about how often this bites: across every Coexistence attempt started from a phone on our platform, not one has ever completed, while the ordinary new-number flow from a phone succeeds routinely. If someone tells you to "just do it on the app", they have not done it.
The setup, step by step
Before you start, have two things ready: a computer, and the phone with the Business app in your hand. Also a Facebook Business account — in our own onboarding data this, not the number, is the most common place UAE businesses stall.
1. On the computer, log in to your WhatsApp platform and open the WhatsApp connection settings.
2. Choose the Coexistence option — the one that mentions connecting a number you already use in the Business app. This is a different button from the ordinary "connect a new number" flow, and choosing the wrong one is a common mistake.
3. Log in with Facebook and select or create your Business.
4. Pick the number that is on the Business app.
5. A QR code appears on the computer screen. On the phone: WhatsApp Business app → Settings → Linked devices → Link a device → scan it.
6. Done. The number now runs in both places.
What happens to your old chats
This is the question every business asks, and it deserves a careful answer rather than a reassuring one.
Meta releases up to six months of the number's existing conversations after onboarding, and a platform that supports it will import them into your inbox. But three caveats matter:
It is not instant. Meta sends it in the minutes after onboarding, in chunks. Sometimes it takes considerably longer.
There is no way to request it. No API exists to trigger the replay, check its status, or retry it. If it does not arrive, there is no button anyone can press.
It only happens at connection time. A number connected before your platform supported history import will not receive it retroactively — it would have to be disconnected and reconnected.
So the honest framing for any business asking: your ongoing conversations continue uninterrupted and everything from the moment you connect is captured. The older history usually arrives too, and your existing chats remain on the phone in the Business app either way, so nothing is lost even in the worst case.
Coexistence or a clean migration?
| Coexistence | Move the number to the API | |
|---|---|---|
| Number stays in the Business app | Yes | No |
| Agent keeps using their phone | Yes | No |
| Downtime during switch | None | Short cut-over |
| Old chats available in the API | Up to 6 months, released by Meta | No |
| Setup can be done on a phone | No — computer required | Yes |
| Needs 7 days on the Business app | Yes | No |
Coexistence suits a business whose number is genuinely in daily use by a person who is not going to stop using it. A clean migration suits a fresh number, or a team that is moving to a shared inbox wholesale and wants one place for everything.
There is also a third option worth naming, because it is often the least disruptive of all: connect a second number to the API and leave the original untouched. Your agent carries on exactly as before, the team gets a proper inbox on the new line, and you migrate at your own pace.
Why this matters more in the UAE than most markets
UAE businesses tend to run WhatsApp harder than their equivalents elsewhere. A Dubai real-estate agent, a clinic reception, a trading company — these are often running the entire customer relationship through one handset, in two languages, with hundreds of live threads.
That makes the old trade-off unusually painful. Asking a broker to hand over the number their clients have been messaging for three years is not a technical change, it is a business risk. Coexistence turns it into a non-event: the phone keeps working, and the team gains the shared inbox, assignment, automation and reporting that the app alone cannot provide.
Common problems, and what causes them
Nothing happens when you tap the Coexistence button on a phone. Expected — see above. Move to a computer.
The number is less than 7 days old on the Business app. There is no way around this; wait it out.
You picked the wrong button. The ordinary "connect a new number" flow does not preserve the Business app link. If you have already gone through it, the number has moved rather than been linked.
Old chats have not appeared. Give it time; there is no retry. Meanwhile everything new is captured, and the old threads are still on the phone.
The Facebook Business account step blocks you. The most common stall of all, and it has nothing to do with WhatsApp. Set it up before you start.
Want someone on the call while you do it?
Coexistence takes about ten minutes with a computer and your phone in hand. We will stay on WhatsApp with you through the Facebook and QR steps.
Set it up with us →Sources
- Meta WhatsApp Cloud API documentation — Coexistence onboarding, the 7-day requirement and the chat-history release
- QuickWA platform telemetry — observed outcomes of Coexistence onboarding attempts by device type
- QuickWA onboarding data — where UAE accounts most commonly stall
Last reviewed: 8 September 2026. Meta changes onboarding flows without notice — if a step here no longer matches what you see, tell us and we will correct it.