Coexistence Option Not Showing? Causes and Fixes

When the coexistence option does not show up, the Meta window displays the new-number signup: it asks you to type in a number, offers a virtual number and wants to confirm by SMS or phone call. This happens because Meta decides which path to offer by looking at the number and the account, and something there does not fit coexistence. The most common causes are the number being on regular WhatsApp instead of WhatsApp Business, an outdated app, the number being left pending on an account created by an earlier attempt, or the number already being tied to another platform. All of them have a fix, and none requires deleting WhatsApp from the phone.

The most important rule comes before the causes: if the number is on the phone, do not complete the new-number signup. That path exists for numbers without WhatsApp, and finishing it takes the number off the app.

What the right coexistence screen looks like

Knowing how coexistence should look is the fastest way to notice that something went off track. On Meta's official page about WhatsApp Business app users, the path is this:

1. Meta offers to connect the existing account. In the Embedded Signup window, the option appears to connect the WhatsApp Business app account you already use to the platform.
2. You enter the app's number. Meta shows a verification code. In the new interface, launched in September 2026, this step may appear as a QR code.
3. The phone receives a message from the official Facebook Business account. In it you tap Connect and confirm the connection with the platform.
4. The app asks about history. You confirm whether you want to share conversations and contacts with the partner.
5. You return to the Meta window to enter the code, if it asks, and finish the flow.

If instead the window asks for a new number, offers a virtual number or wants to send a code by SMS, you are in the standard signup. That is the flow for people who will use a number on the API only, with no app on the phone.

Why the standard signup is dangerous for app users

In the standard signup, the partner has to register the number on the API with a call named /register. On a number that is on WhatsApp Business on the phone, this registration logs the app out: the number becomes exclusive to the API and the team loses the app. The partner cannot undo it.

That is why Frame Conexa never registers a number you asked to connect with coexistence. If Meta completes the standard signup in that case, the dashboard stops and warns: "Meta completed the standard signup. The authorization arrived, but the number was not confirmed in coexistence. We did not enable API-only use." Nothing changes on the phone. The coexistence guide explains this rule in detail.

Why Meta does not offer coexistence

The causes below go from the simplest to check to those that depend on someone else. It is worth going through them one at a time before trying again.

The number is on regular WhatsApp, not Business

Coexistence exists only for the WhatsApp Business app, the one with the B icon. A number on regular WhatsApp, the personal one, has nothing to coexist with, and Meta does not offer the path.

Check on the phone which of the two apps has the number. If it is regular WhatsApp, the first step is to move the number to WhatsApp Business: when you install the Business app, it offers to use the number already on the device and bring over the conversations. After that, use the number normally in the app for a few days before connecting. Meta may refuse numbers that are very new or barely used on WhatsApp Business, with code 3441045, and the way out in that case is to use the app and try again later.

WhatsApp Business is outdated

Meta requires WhatsApp Business version 2.24.17 or higher. With an earlier version, it rejects the number at the eligibility step, and the rejection code is 4563015.

The fix takes a minute: open the App Store or Play Store on the number's phone, search for WhatsApp Business and tap Update. If the button says Open, the app is already up to date.

An earlier attempt left the number pending on an account

This is the hardest cause to spot, because no error appears. We measured the case in September 2026: a customer went through the standard signup one night without completing the connection. Meta created a WhatsApp Business account and left his number inside it, in a pending state, never registered. The phone app kept working normally. From then on, every coexistence attempt fell into the standard signup, and the window's number list showed his own number as already verified.

The fix was to delete the number from that account, done by the business owner:

1. Open the WhatsApp Manager for the company's portfolio, with an admin user.
2. In the number list, find the number that shows as pending.
3. Tap the trash icon, confirm with the Meta account password and choose the reason about switching to the WhatsApp Business app.
4. Redo the connection. In the measured case, the coexistence screen appeared on the next attempt.

Two notes on this case. The partner cannot delete the number for you: Meta only lets the account owner do it, through the screen. And this deletion only applies to a number that stayed pending on an account without ever having been registered. Deleting an active number, or deleting the whole account, is what partners report as the cause of weeks of waiting to get back to coexistence.

The number is already tied to another platform

Meta does not connect two providers to the same number at the same time. If the number was already connected to another tool, the window refuses with a notice and a code. In Frame Conexa, codes 2655093, 2655049, 2494119 and 3441049 appear with the same guidance, because the way out is the same for all four:

1. On the number's phone, open WhatsApp Business › Settings › Account › Business Platform (in some versions, Business platform).
2. If another company appears there, disconnect it, or ask its support to disconnect it.
3. Wait a few minutes and try again. A number that just left another account can be refused for about 3 minutes, with code 3441030.

There is a variation that does not show up on that screen: the old partner is still assigned to the WhatsApp Business account in Business Manager, and Meta refuses with error 2388002. The fix is in the article on Embedded Signup. If you are switching providers, the full step-by-step is in coexistence disconnected: reasons and fixes.

The number is already API-only

A number that was already registered on the Cloud API, by another system or in an old attempt, is no longer on the app. There is no app to coexist with, and Meta treats the number as API-exclusive. In that case coexistence is not possible until the number goes back to the app, and the decision to do that depends on how it is being used today. Talk to the current provider before touching anything.

The wrong account was used in the Meta window

The Meta window shows the businesses and WhatsApp Business accounts that the logged-in user manages. Signing in with the wrong Facebook account, or creating a new business instead of choosing the existing one, leads down a path that does not see the app's number. Sign in with the account that has full control of the company's registration at Meta. If that is someone else, ask them to make the connection, or have them open the connection link themselves.

The partner's configuration is outdated

If nothing above explains it, the cause may be on the partner's side. The coexistence option only appears when the partner requests that flow from Meta, with a configuration Meta still accepts. Meta announced the end of Embedded Signup version 2 on October 15, 2026 and tells partners to migrate to version 4. Partners that do not migrate may start opening only the standard signup. There is nothing to do on your side beyond telling the provider.

Table: what the window shows and what to do

In Frame Conexa, each of these drop-offs is recorded with its reason, including those that happen only inside the Meta window and never generate an authorization. That is what lets support tell "Meta refused" apart from "the person closed the window".

What never to do to force coexistence

The frustration of seeing the option vanish leads to shortcuts that make things worse:

• Do not complete the standard signup with a number that is on the phone. Finishing that path takes the number off the app.
• Do not delete the WhatsApp account from the phone to "start from scratch". You lose conversations, and Meta may take a while to consider the number eligible again.
• Do not delete an active number from the WhatsApp Business account. Only the pending number, never registered, goes away with no known side effect.
• Do not try ten times in a row. Meta limits attempts for a few minutes, and each refused attempt can leave the partner assigned to the account, which causes 2388002 on the following ones.
• Do not ask for the connection from someone who does not have the phone in hand. Coexistence requires a confirmation inside the app, on the number's device. Without it, the flow stops halfway.

Checklist before trying again

With the number's phone in hand:

1. The number is on WhatsApp Business, the app with the letter B.
2. The app is up to date, version 2.24.17 or higher.
3. In Settings › Account › Business Platform no other company is connected.
4. In the company's WhatsApp Manager, the number does not show as pending on an account.
5. You will sign in with the account that manages the company at Meta.
6. The phone is online with the app open, ready for the confirmation.

If all six items are right and the window keeps opening the standard signup, contact the provider's support and tell them the time of the attempt. In Frame Conexa, that time helps locate what Meta replied on that attempt.

When a new number is the right choice

Sometimes the standard signup is not a mistake: it is the right path. If the number has no WhatsApp on any device, if nobody will answer from the phone, or if the sending volume justifies the higher pace of the API, a new API-only number works better. It does not depend on the phone being on, sends up to 80 messages per second versus 20 with coexistence, and has its business profile edited from the dashboard. The full comparison is in the coexistence guide, and what changes in cost is in the article on how much the WhatsApp API costs.

Frequently asked questions

Why does the coexistence option not appear in Meta's signup?

Because Meta did not recognize the number as an active WhatsApp Business app account. The most common causes are the number being on regular WhatsApp, the app being below version 2.24.17, the number being left pending on an account created by an earlier attempt, or the number already being tied to another platform. If all of that is fine, the cause may be the partner's configuration.

Can I use coexistence with regular WhatsApp?

No. Coexistence is exclusive to the WhatsApp Business app. Move the number to WhatsApp Business first, bringing over the conversations during installation, and use the app for a few days before connecting. Meta may refuse numbers that are very new or barely used on the app, with code 3441045.

Meta asked for an SMS code. Should I continue?

Only if the number is not on any WhatsApp. The SMS or phone call code belongs to the new-number signup, and completing that path with a number that is on the phone takes the number off the app. If the number is on WhatsApp Business, close the window and review the causes in this article before trying again.

Does deleting the number from the WhatsApp Business account fix it?

Only in one case: when the number was left pending on an account, created by an earlier attempt, without ever having been registered. Then the business owner deletes it through WhatsApp Manager and coexistence shows up again. Deleting an active number or deleting the whole account can leave the number unable to enter coexistence for weeks.

How long should I wait before trying again?

It depends on the reason. After disconnecting another platform, about 3 minutes. After a notice of too many attempts, a few minutes. If Meta refused because the number is new or barely used, a few days of normal app use. For an outdated app or a pending number, you can try right after the fix.

Next step

With the checklist in order, the connection takes a few minutes. In Frame Conexa, the Connect WhatsApp button opens the flow with coexistence as the first option, and the per-number plans show what each number includes. If the number was already connected and dropped, the path is different: see why coexistence disconnects and how to reconnect.