WhatsApp Coexistence Disconnected? Causes and How to Fix

WhatsApp coexistence disconnects for one of six reasons, and Meta tells the partner which one it was: someone tapped disconnect in the app, the primary phone went about 14 days without use, a linked device went about 30 days without use, the number was changed, WhatsApp was registered again, or the account stopped being a WhatsApp Business account. In every case the phone keeps its conversations and contacts. What stops is the API end: the system stops receiving and sending through the number until a new connection, which takes a few minutes and can bring the history in again.

This guide shows how to tell that coexistence dropped, what each reason means, how to reconnect, how to disconnect on purpose, and how to switch providers without losing your number. If you do not know yet what coexistence is, start with the complete guide to coexistence.

How to tell that coexistence dropped

The disconnection does not show up as an error on the phone. The WhatsApp Business app keeps working normally, which is why it is usually noticed late, when someone sees the system stopped replying. The signs are these:

• Messages sent by the system fail. Automatic replies, reminders, bulk sends: nothing goes out through the API.
• The dashboard stops showing what happens on the phone. Messages received and replies given in the app no longer appear in the system's conversation.
• The app's Business Platform screen changed. Under Settings › Account › Business Platform, the partner disappears from the list or shows as disconnected.
• Meta notified the partner. The disconnection reaches the provider through a notification called account_update, with the event PARTNER_REMOVED or ACCOUNT_OFFBOARDED.

In Frame Conexa, that notification marks the number as disconnected immediately, before any send fails, and the number's screen starts showing the Reconnect button. Anyone integrating through the API receives the instance_status event with the state disconnected at the same moment and, when the number comes back, another event with the state connected. The format is in the webhooks guide in the documentation.

Note: a coexistence disconnection is different from a number blocked by Meta. With a block, the number itself loses the right to send, through the app and the API. With a disconnection, the number is healthy and only the integration dropped. If the phone shows "This account is not allowed to use WhatsApp," the problem is something else, and the article on blocked WhatsApp Business explains the path.

The six reasons Meta reports

When coexistence drops, Meta's notification may carry a field called disconnection_info with two pieces of data: the reason (reason) and who initiated it (initiated_by), which is USER when a person did something and SYSTEM when Meta itself turned it off. The official list of reasons is on Meta's page about WhatsApp Business app users.

None of these reasons erases anything on the phone. And none of them is a punishment: Meta turns off the integration because the two ends are no longer in sync, not because the number did something wrong.

The primary phone sat idle for 14 days

This is the most common reason and the easiest to avoid. In coexistence, the phone where WhatsApp Business is installed remains the root of the number. Meta expects it to be active: on, with internet, and with the app opened now and then. After about 14 days without activity, it turns off the integration with the reason PRIMARY_INACTIVITY.

The typical case is a business that connected its number and started handling customers only through the system. The phone sits in a drawer, the battery dies, and two weeks later the API stops working with no warning on the device. If the idea is never to use the phone again, coexistence is not the right mode. The path is a new API-only number, compared with coexistence in the complete guide.

Someone disconnected from the app

The reason ACCOUNT_DISCONNECTED with initiated_by: USER means someone with the phone in hand opened the Business Platform screen and tapped disconnect. Sometimes it is intentional. Often it is an employee who did not recognize the partner's name in the list, or someone who followed another provider's tutorial. Agree with the team on who may touch that screen.

The number changed devices or was registered again

Switching phones is the trickiest trigger. When WhatsApp Business is installed and registered on a new device, Meta considers the number registered again (USER_RE_REGISTERED) and turns off coexistence. The same goes for reinstalling the app and confirming the number by SMS on the same device. Meta also notifies the partner with an event of its own, account_offboarded, which it describes as an exit caused by a device change or a new registration.

If the phone switch is planned, do it this way: migrate WhatsApp Business to the new device, check that the conversations came over, open the app, and only then reconnect the platform. The reconnection brings the API end back.

The number was changed or the account stopped being Business

CHANGE_NUMBER appears when the company uses the change-number function inside the app. The account starts answering under another number, and the old number's coexistence ends. The new number has to go through the connection flow from scratch, because to Meta it is a different asset.

BUSINESS_DOWNGRADE appears when the number stops being a WhatsApp Business account, for example when it is registered in regular WhatsApp. Coexistence only exists for the Business app. To come back, the number has to be on WhatsApp Business again before reconnecting.

What happens when coexistence drops

The question everyone asks is what was lost. The short answer: nothing that was on the phone, and nothing that was already in the dashboard.

One point deserves attention: what happens on the phone while coexistence is off does not reach the dashboard later. A three-day conversation without the integration only returns to the system if you reconnect and agree to share the history again, as the next section shows.

It is also worth remembering what coexistence turns off inside the app while it is active, according to Meta: disappearing messages, view once, live location, and creating broadcast lists. With the integration off, those features return to the app. When you reconnect, they go away again. Groups, calls, and catalog do not change in the app in either state; they just do not go through the API.

How to reconnect without losing anything

Reconnecting means redoing the same flow as the first connection, Meta's Embedded Signup, with the same number. It takes a few minutes when the phone is at hand.

1. Prepare the phone. Open WhatsApp Business, check that it is updated and online, and leave the app open.
2. Open the reconnection. In Frame Conexa, go to the number's screen and tap Reconnect. If the number belongs to a customer of yours, generate a new connection link and send it to whoever has the phone.
3. Authorize in Meta's window. Log in with the account that manages the business, and choose the same WhatsApp Business account and the same number.
4. Confirm on the phone. The app asks to connect to the platform and asks whether you want to share the history. Accept to bring in the conversations from the period when the integration was off.
5. Wait for the sync. The dashboard shows the progress of the conversation and contact import. Keep the app open until it finishes.

In Frame Conexa, reconnecting the same number returns the same instance: the identifier your integration uses does not change, the conversations that were already in the dashboard are still there, and the number takes the same subscription slot again. The history sync starts over from zero, as in the first connection.

The history can be shared again

Meta allows sharing the history and contacts only once per connection. The official rule says that, to repeat it, the customer has to first disconnect and then redo Embedded Signup. A reconnection is exactly that, so the history can come in again: the messages from the 180 days before the new connection, with media only from the last 14 days.

It is also the way out for anyone who declined sharing the first time and regretted it. When the number's owner declines, Meta notifies the partner with code 2593109 ("History sync is turned off by the business from the WhatsApp Business App"), and the only way to change the answer is to disconnect and connect again.

Linked devices are removed again

When connecting, Meta unlinks all devices attached to the account: WhatsApp Web, the desktop app, and tablets. That also applies to a reconnection. Once the number is back, link again the devices the team uses. Meta states that the Windows apps and WearOS watch apps are not supported in coexistence: messages sent from them do not reach the API.

When Meta tells you you're back

When the number connects again to the same partner after having left, Meta sends the account_reconnected event. For anyone integrating, that is the signal that the pause is over. In Frame Conexa it adds to the instance_status event with the state connected, which is the event your integration should listen to in order to mark the channel as active again.

Disconnecting on purpose: the two paths

There are good reasons to disconnect: switching providers, no longer using the API, redoing the flow to share the history. Meta accepts two paths, and neither erases the number.

Through the app. On the number's phone, open Settings › Account › Business Platform, tap the partner and then disconnect. This is the official path in Meta's documentation. In September 2026, a Frame Conexa customer disconnected using this button and the number came back through the same connection link 26 minutes later, with no refusal from Meta.

Through Business Manager. Under the portfolio's Settings › Partners, open the partner, the WhatsApp account, and choose Manage › Remove access. This is the path for whoever administers the business from a computer and does not have the phone nearby. Meta notifies the partner with the events PARTNER_APP_UNINSTALLED and PARTNER_REMOVED.

Warning: Meta does not allow deregistering from the API a number that is in coexistence. The deregister call (deregister) does not work in this mode, and the disconnection has to go through the app or Business Manager. Be suspicious of any procedure that asks for something else.

What not to do to disconnect

Three shortcuts look like they solve it and create a bigger problem:

• Deleting the number from the WhatsApp Business account. Partners report that a number removed from the account can spend weeks or months unable to return to coexistence. The exception is a number that stayed pending in an account without ever having been registered, a case covered in the article on when the coexistence option does not show.
• Deleting the WhatsApp Business account or the portfolio. The effect is the same, with the risk of losing the company's verification.
• Registering the number as a "new number" in another system. That takes the number out of the phone app. In coexistence, the number never goes through the new-number registration, and that is what keeps the app working.

Switching providers without losing your number

Meta does not connect two providers to the same number at the same time. Switching providers is therefore a sequence: disconnect the old one and connect the new one.

1. Export what you need from the old provider. Conversations, contacts, and campaign reports live in its system. Meta does not transfer anything from one provider to another.
2. Disconnect the old provider by one of the two paths above. Check on the Business Platform screen that it left the list.
3. Wait a few minutes. A number that has just left an account may be refused for a short time. Meta responds with code 3441030, and the guidance is to try again after about 3 minutes.
4. Connect with the new provider through the normal flow and accept sharing the history. The new provider receives the 180 days before the connection.

Two problems can show up along the way. The first is the old provider still being assigned to the account, which makes Meta refuse the number with error 2388002; the solution is in the article on Embedded Signup. The second is the credit line: if the old provider was a Solution Partner and the account still uses its credit line, Meta warns that there may be an error when changing partners. In that case, the account needs its own payment method, and the article on the API payment method shows how to register one.

How to avoid disconnections

Most disconnections come from habits, not technical failures. A short routine prevents almost all of them:

• Open WhatsApp Business on the primary phone at least once a week, even if the team handles customers through the system. Meta's margin is about 14 days; once a week leaves slack.
• Keep the phone on and online. A device with a dead battery counts as inactive.
• Do not reinstall or switch phones without planning. If you must, reconnect right after the app is working on the new device.
• Restrict who touches the Business Platform screen. Explain to the team what the partner that appears there is.
• Keep the app updated. Meta requires version 2.24.17 or later for coexistence.
• Listen for the disconnection event. Anyone integrating through the API should handle instance_status and alert someone when the state becomes disconnected, instead of finding out on the first send that fails.

Frequently asked questions

Why did WhatsApp coexistence disconnect on its own?

Almost always because the primary phone went about 14 days without use, and Meta turned off the integration with the reason PRIMARY_INACTIVITY. The other official reasons are a disconnection done in the app, a linked device idle for about 30 days, a number change, a new WhatsApp registration, and an account that stopped being a WhatsApp Business account. None of them erases the conversations on the phone.

Did I lose my conversations when coexistence dropped?

No. The phone app keeps everything, and the conversations that were already in the dashboard are still there. What is left out is the period when the integration was off: those messages only reach the system if you reconnect and agree to share the history again, because Meta sends the 180 days before each new connection.

How do I reconnect coexistence?

Redo Meta's connection flow with the same number: open WhatsApp Business on the phone, start the reconnection in the provider's dashboard, authorize with the account that manages the business, and confirm in the app. In Frame Conexa, the Reconnect button is on the number's screen, and the number comes back with the same identifier and the same conversations.

How do I disconnect WhatsApp Business from the API?

From the phone, under Settings › Account › Business Platform, by tapping the partner and then disconnect. Or from Business Manager, under Partners, by removing the partner's access to the WhatsApp account. Meta does not allow deregistering a coexistence number from the API through any other path, and deleting the number from the account can block its return for weeks.

Can I switch providers and keep the same number?

Yes. Disconnect the old provider, wait a few minutes, and connect with the new one, accepting to share the history. Meta does not connect two providers at once and does not transfer data between them, so export first whatever is in the old system. If the old provider was paying Meta on your behalf, register your own payment method on the account.

Next step

If the number dropped and you use Frame Conexa, open the number's screen and tap Reconnect with the phone nearby. If you are thinking about bringing your number over from another provider, see the per-number plans and the quickstart guide for the first send after connecting.