Which numbers are eligible for Coexistence
A number needs to be already in use in the WhatsApp Business app, on version 2.24.17 or newer, inside a Business Portfolio you can administer, and not already attached to another provider. Geography is no longer a condition. Anything else is refused during onboarding.
The minimum WhatsApp Business app version for Coexistence.
Geographic restrictions in Meta's current onboarding documentation for Business app users.
The error a number returns when it is attached but never completed registration.
What the number itself has to be
Four conditions, and all of them are checked during Meta's own onboarding rather than by a provider.
- Already registered and in use in the WhatsApp Business app, not the consumer WhatsApp app.
- Running app version 2.24.17 or newer on the primary device.
- Inside a Meta Business Portfolio you have administrator access to.
- Not already connected to another provider's app.
Where Coexistence is available
Everywhere the WhatsApp Business app operates. Meta's current onboarding documentation for Business app users states no geographic restriction at all, and the rollout that began regionally finished during 2026, with South Africa and Nigeria among the last markets added.\n\nThis is worth stating plainly because the regional lists published during the rollout are still circulating, and several of them still name countries as excluded that have been supported for months. A business reading one of those concludes it cannot use the feature when it can.\n\nMeta does not publish a dated country list, so the reliable test is the flow itself. If the number is active on the WhatsApp Business app and Embedded Signup does not refuse it on geography, Coexistence is available to that number.
What goes wrong at onboarding
Three failures account for most of them, and each looks different.\n\nA number on the consumer WhatsApp app is not offered Coexistence at all. It has to be moved to the WhatsApp Business app first, which is a migration the business does on the phone.\n\nAn out of date app produces a flow that starts and cannot complete the scan. Updating and retrying is the fix.\n\nAnd a flow closed partway leaves the number attached to the account but not registered, which looks connected in a dashboard and fails on the first send with error 133010. Running the flow again from the start completes it.
Common mistakes
- Starting onboarding on a number still in the consumer WhatsApp app. It has to be moved to the Business app first.
- Trusting a regional availability list from the rollout. Several are stale and still name supported countries as excluded.
- Closing Meta's popup once the number appears. The steps after that are what complete registration.
EasyCoexistence runs Meta's own Embedded Signup, so eligibility is decided by Meta rather than by us, and each attempt is recorded on the connection timeline with what it returned.
Frequently asked questions
Can I use a landline or a virtual number?
It has to be a number registered in the WhatsApp Business app, which means it must be able to receive the registration message.
What app version do I need?
2.24.17 or newer on the device holding the number.
Is Coexistence available in my country?
Almost certainly. Meta's current onboarding documentation states no geographic restriction, and the regional rollout completed during 2026. The flow itself is the reliable test.
The number appears in the dashboard but will not send.
Onboarding probably did not complete. That returns error 133010, and rerunning the flow fixes it.
Keep reading
Ready to get started?
Set up WhatsApp Coexistence in minutes, not months. The app keeps working on the phone.
Start Free TrialVerified on