Meta Tech Provider

"This phone number is already registered to a WhatsApp account"

Meta's signup popup shows this when the number is already registered somewhere that blocks the step being attempted: consumer WhatsApp, a WhatsApp Business API account, or an account on another platform. The number has to be disconnected from that account first. After disconnecting, Meta says it can take a few minutes before the number is available again.

3 minutes

How long Meta says a number may take to become available after it is disconnected.

3 places

Where Meta says the number may already be registered: WhatsApp Messenger, the WhatsApp Business app, or the API.

2.24.17

Minimum WhatsApp Business app version for connecting an existing app number through Coexistence.

What does Meta's documentation say this message means?

Meta's Embedded Signup error reference lists the message as "This number is registered to an existing WhatsApp account. To use this number, disconnect it from the existing account. Then, return to this page and re-enter the number." It adds that it may take up to 3 minutes for the number to become available.

Meta's explanation is that the phone number is already registered on its platform, naming WhatsApp Messenger, the WhatsApp Business app and the WhatsApp Business API, and its suggested solution is to deregister the number or use a different one. The popup is shown in the user's language, so the same refusal arrives in Italian, Spanish or Portuguese with identical meaning.

Why would a Coexistence signup hit this at all?

Coexistence exists to connect a number that is already registered in the WhatsApp Business app, so being registered is not the problem in itself. The message appears when the flow is not on the Coexistence path, or when the registration is of the wrong kind.

Three situations produce it. The number is on consumer WhatsApp rather than the WhatsApp Business app, which Coexistence cannot connect. The flow being run is a standard new-number signup rather than the option to connect an existing WhatsApp Business app account, so Meta treats the number as one to register fresh. Or the number is registered directly on the WhatsApp Business API, outside the app.

Each needs a different fix, which is why the message alone is not enough to act on.

How do you free the number and retry?

Match the fix to where the number lives.

If it is on consumer WhatsApp, move it to the WhatsApp Business app on the phone first. If it is on the WhatsApp Business app and the popup still says this, check that the flow offered the option to connect an existing WhatsApp Business app account; without that screen the flow is the wrong one. If it is registered on the API through another platform, it has to be disconnected there.

After disconnecting, wait a few minutes, as Meta notes, then return to the popup and enter the number again. If the popup has been closed, start the flow again from the beginning rather than reusing an old window.

Common mistakes

Retrying the same number immediately after disconnecting. Meta says availability can take up to three minutes.
Running a standard new-number signup for an app number. Coexistence needs the flow that offers to connect the existing WhatsApp Business app account.
Deleting the WhatsApp Business app account to clear the error. That removes the very registration Coexistence connects.

Doing this with EasyCoexistence

EasyCoexistence launches Embedded Signup with the Coexistence option already enabled, and records what Meta returned on each attempt on the connection timeline.

Frequently asked questions

Which existing account is Meta talking about?

The popup does not say. It is wherever the number is currently registered: consumer WhatsApp, the WhatsApp Business app on the wrong path, or the API through another platform.

Will I lose my chats if I disconnect?

Disconnecting from a platform happens in the WhatsApp Business app under Settings, Account, Business Platform. It is a separate action from deleting the app account, which is not the fix.

I saw this in Italian. Is it the same error?

Yes. The popup is localised, so the same refusal appears in whichever language the session uses.

Does a provider have to do anything?

Only if the number is connected through that provider. Then the disconnection happens there before the new flow can complete.

Keep reading

Coexistence error: number already connected to another providerMeta blocks Coexistence signup when the number is already connected to another platform. The exact messages, how to disconnect in the app, and how long to wait."Request code failed: Our servers are temporarily unavailable"Why the signup popup says request code failed and asks you to wait 1 hour, how Meta limits verification codes, and how to retry without extending the wait."This phone number isn't eligible" in Coexistence signupWhy Meta's signup popup says a WhatsApp Business app number isn't eligible for registration or migration, what Meta checks, and what to do before retrying.Which numbers are eligible for CoexistenceThe app version, the account type, the portfolio access, and what actually makes Meta refuse a number during Coexistence onboarding.The WhatsApp Business Account, and why overrides live on itWhat a WABA holds, why webhook overrides are applied at this level rather than per number, and what that means when a connection is removed.

Ready to get started?

Set up WhatsApp Coexistence in minutes, not months. The app keeps working on the phone.

Start Free Trial

Verified on 2026-10-11