Keeping your number and your chats: WhatsApp coexistence

Coexistence is a Meta setup in which one phone number works on the WhatsApp Business app and through the API at the same time — you keep replying from the handset, and those messages also appear in your shared team inbox. It exists precisely because the alternative frightens people out of migrating at all.

The fear is reasonable. Your number is printed on your packaging, saved in thousands of customers' phones, and answering your ads. "Will I lose it, and will I lose three years of conversations?" is the right question to ask before you touch anything.

The two paths, and why the choice is not casual

Both keep the number. The difference is whether the phone app survives — and that matters enormously to a business where the owner answers customers from their handset in the evening.

What coexistence genuinely gives you

• The same number on both surfaces. Your team works the shared inbox; you can still reply from the phone.
• Message echoes. A reply typed on the handset appears in the shared inbox, so a colleague picking the conversation up later sees what was said.
• Contact sync. The contacts held in the Business app come across.
• Everything the API adds — automations, approved templates, broadcasts, multiple people answering at once.

Chat history: the honest answer

This is where most articles become vague, so here is the position plainly.

Meta's coexistence flow can import previous conversations, and the import is supported end to end on our side. What we cannot tell you is that your specific history will arrive, because whether Meta sends it — and how much — depends on the account, the app state and the signup path.

So treat history as a bonus, not a guarantee. Connect, then check the inbox for imported conversations before you rely on them being there. If your business depends on having those threads, take an export from the Business app first, which costs you ten minutes and removes the risk entirely.

The trade coexistence asks in return

Running one number on two surfaces creates a coordination problem the standard path does not have.

1. Two people can answer the same customer. You from the phone, a colleague from the inbox. Agreeing who owns which conversation matters more here than anywhere else — see running one number across a team.
2. Automations do not know what you typed on the phone. A bot waiting for an answer can still capture a customer's reply meant for you. The fix is the same two-step flow everyone needs — handing a chat from bot to human.
3. The handset stays part of your infrastructure. A phone that is lost, wiped or logged out is now an operational event rather than an inconvenience.

Which path should you choose?

That last row is worth taking seriously. Connecting a different number to the API first — a spare SIM, a second line — lets you learn the platform with zero risk to your main line, and you migrate the important number once you are comfortable. It is the most under-used de-risking move available.

What does not change either way

Both paths land you under the same Meta rules, and it is worth knowing them before you start rather than discovering them in week two:

• Messaging someone who has not written to you recently needs an approved template. The 24-hour customer service window opens when a customer messages or calls you and resets each time, per Meta's sending messages documentation.
• You start on a limited messaging tier — 250 unique recipients per rolling 24 hours, rising through 2,000, 10,000 and 100,000, per Meta's messaging limits documentation.
• There are two bills. Your platform's subscription, and Meta's per-message charge for templates. Messages inside an open window are free.

The window mechanic is the one that surprises people most — the 24-hour window explains it properly.

A safe migration sequence

1. Export your chat history from the Business app before you touch anything. Ten minutes, and it makes the rest of this risk-free.
2. Decide the path — coexistence or standard — before starting connection, since the choice happens inside Meta's window.
3. Pick a quiet day. Not the morning of a sale.
4. Connect, and check the inbox for imported conversations rather than assuming.
5. Send yourself a test message from a personal phone to confirm both directions work.
6. Start business verification immediately — it lifts your messaging tier and your template ceiling, and it takes days.
7. Tell nobody. Customers do not need to know; from their side the number is unchanged.

The thing genuinely worth worrying about

Not the migration. The migration is well-trodden and your number survives either way.

What actually loses people their number is the setup they choose instead of the official API — tools that link a device by QR code and drive the app. Those get accounts restricted for the automation pattern regardless of what is being sent, which is covered in the ban risk of unofficial WhatsApp tools.

Coexistence is the opposite of that: it is Meta's own sanctioned way to have both surfaces at once.

What it means for your team's habits

Coexistence solves a technical problem and creates a human one. Two surfaces means two places a customer can be answered, so agree three things before you turn it on:

1. Who answers what. The simplest split that works: the phone is for conversations you personally own, the inbox is for everything else.
2. What happens to a conversation you started on the phone. It appears in the inbox, so a colleague can pick it up — decide whether they should.
3. Who is responsible for the queue. The phone shows you what arrives; it does not show you what nobody has answered.

Automations and the handset

Worth understanding before it surprises you. A message you type on the phone is not the same as a message sent by an automation, and the flow waiting for a customer's answer does not know you have intervened.

So the customer replies to you, and the bot captures it as the answer to a question it asked earlier. The fix is a two-step automation triggered when a human sends a message, which cancels any pending question — it sends nothing and needs no configuration. Details in handing a chat from bot to human.

What coexistence does not change

• Templates are still required to message someone outside the 24-hour window, whichever surface you send from.
• Meta still bills per delivered template message, and messages inside an open window are still free under its pricing documentation.
• Your messaging tier still applies — 250 unique recipients per rolling 24 hours to begin with.
• Template limits still apply — 250 per WhatsApp Business Account unverified, up to 6,000 once verified, per Meta's template documentation.

Coexistence changes where you can type, not what Meta permits.

Questions to settle before you connect

1. Does anyone need to keep replying from a phone? If yes, coexistence. If your team will work from computers, the standard path is simpler.
2. Whose phone? That handset becomes part of your operation, so it should belong to the business rather than to someone who might leave.
3. Have you exported your chat history? Ten minutes, and it makes the history question stop mattering.
4. Could you rehearse on a spare number first? The cheapest way to remove every remaining unknown.
5. Who watches the shared inbox on day one? Messages will start appearing in a new place, and a queue nobody is watching is the commonest first-week problem.

The reassurance that is actually true

Customers notice nothing. Your number is unchanged, their conversation thread is unchanged, and messages keep arriving the way they always did. There is no announcement to make and no reason to make one — explaining the plumbing only invites questions nobody had.

What changes is on your side: more people can answer, order events can start conversations, and the repetitive questions can be handled without anyone typing. That is the whole point of moving, and it is available on both paths.