How to disconnect WhatsApp Coexistence without losing your data

To disconnect WhatsApp Coexistence is to take your number off the Cloud API and leave it only in the WhatsApp Business app, the way it was before you connected. Same number, same chats, same team on the phone. The app features that were locked while the API was on come back. The history that was already synced stays in your dashboard. What goes away is everything the API was doing for you: automated sends, template messages sent through it, and the record of which ad started each new conversation.

The short version: disconnecting is fully reversible for the number and not reversible for the data. Anything that is not captured while the number is off the API does not show up later.

Before and after: the full picture

Here is the side-by-side. If you read nothing else, read this.

The pattern is easy to spot. On the phone side, nothing is lost and a few things come back. On the API side, everything stops. That is why the decision to disconnect is usually a marketing and data decision, not a customer service one.

What your team gets back on the phone

While coexistence is on, the app gives up a few features: broadcast lists, disappearing messages, view once and live location. Groups stay on the phone but sit outside the API. When you disconnect, the app goes back to how it was.

The one most teams miss is broadcast lists. Picture a med spa that used to send a monthly promo to past clients from the app. With coexistence on, that list is gone, and someone notices fast.

One warning, though. A broadcast list is not a license to blast. Replacing API sends with manual mass sends from the phone is exactly the pattern Meta penalizes. Number quality and blocks apply the same way with or without the API. If that is the real reason you want to disconnect, read WhatsApp number quality first.

What stays in the dashboard, and what stops arriving

Synced history does not disappear. When you first connected, Meta synced up to six months of chat history, and everything that came in live after that was recorded too. All of it stays available.

What stops is the new flow. From the moment you disconnect, messages arriving on the phone no longer reach the API. And this is the part that hurts anyone running paid media.

With click-to-WhatsApp ads, Meta sends a click identifier along with the first message of the conversation, and only through the webhook. That identifier is what tells you which ad started the chat and what it cost. If the number is not connected when that first message lands, the identifier is gone. There is no way to pull it later.

Say you disconnect on a Monday and reconnect on Friday. Every ad-driven conversation that started in those four days has no source in your reporting, even if the customer keeps chatting after you reconnect. How that tracking works end to end is covered in which ad started the WhatsApp conversation.

Good reasons to disconnect

Disconnecting is not a failure. There are solid reasons to do it:

• You are moving the number to another provider or another API. A number can only be on one API at a time. Disconnecting frees it.
• Your day-to-day depends on a locked feature. If broadcast lists or disappearing messages matter more to the business than API sends, the math changes.
• The test is over and the API did not pay off. You connected to measure, you measured, and your volume does not justify keeping it. Fair call.
• Your agency contract with the client ended. The number belongs to the client. Disconnecting at the end of the engagement is the clean exit. More on that in WhatsApp Coexistence for agencies.
• The number is being retired or replaced. No point keeping a connection for a line that is going away.

Bad reasons to disconnect

These come up a lot, and they usually backfire:

• To "fix" something that stopped working. If messages stopped reaching the API, the first suspect is different: nobody has opened the app in a while. See the next section.
• In the middle of a click-to-WhatsApp campaign. You lose the source of every conversation that starts during the gap.
• To go back to blasting from the phone. Same pattern Meta penalizes, as covered above.
• Because you think the team will lose the app. They never lose it, not even while connected. Does the app keep working with coexistence answers that one.

Disconnecting vs. getting dropped

There is a way to lose the connection without clicking anything. If nobody opens WhatsApp Business for about 14 days, Meta may drop the connection. In practice it looks a lot like a disconnect: new conversations stop reaching the API and ad tracking stops.

The difference is that nobody made the call. Nobody paused the automations, nobody told the media buyer, nobody wrote down the date. That makes it the worst kind of data gap, because you only find it when someone squints at a report and asks why cost per conversation flatlined.

Prevention is boring and effective: someone on the team opens the app regularly. On a number that is answered every day, that happens on its own. On secondary lines, like a number used for one campaign or a small location, put it on someone's weekly checklist.

Pre-disconnect checklist

Run through this so you do not find the problem next week:

• No click-to-WhatsApp campaign is live that depends on tracking for this number, or you have accepted the gap
• Anyone sending through the dashboard, Claude or other tools knows sends will stop
• Automations using this number are paused
• If you are moving to another provider, it is ready, so the number spends as little time as possible off an API
• The disconnect date is written down, so whoever reads the next report understands the drop
• The team agreed on how broadcast lists will be used, so they do not turn into mass sends

Reconnecting later

Coming back means running the connection flow again: the number owner authorizes it inside Meta's Embedded Signup and scans a QR code in the app. The requirements are the same as the first time.

What does not come back is the gap. Treat the disconnected period as a known hole in your data: documented, with a start and end date, and called out in any report that covers it. A one-line note in the monthly deck, something like "WhatsApp tracking paused Oct 12 to Oct 16", saves you a long meeting later.

Your next move

Start with the right question: is what I get back in the app worth more than what I lose on the API? If you run click-to-WhatsApp ads and report cost per conversation, the answer is usually no. If the API was only there for a test that has ended, it is usually yes.

If you are still deciding whether coexistence fits at all, the WhatsApp Coexistence page walks through the module, and per-number tiers starting at US$ 39 a month are on the pricing page.