Connecting a number, step by step
Connecting runs through Meta's own Embedded Signup: pick the Business Portfolio, the WhatsApp Business Account and the number, then scan a code in the WhatsApp Business app. About two minutes, and the app keeps working throughout.
- Meta's own flow, not ours
- One code scan on the phone
- History sharing is decided once
Nothing charged for 7 days. Cancel anytime.
Typical time from starting the flow to a connected number.
Steps that happen on the phone rather than in the browser.
The Embedded Signup version a Coexistence connection uses.
What happens in the flow?
Meta's popup opens and asks three things in order.
First the Business Portfolio, which is the company level container in Business Manager. Then the WhatsApp Business Account inside it. Then the phone number, which has to be one already registered in the WhatsApp Business app, because Coexistence connects a number the app is using rather than creating one.
After that the flow moves to the phone. Meta shows a code, someone opens the WhatsApp Business app on the device holding that number, and scans it. That is the only step that leaves the browser, and it is the step nobody else can do on the business's behalf.
What is decided during onboarding and cannot be changed?
Whether to share existing chat history, which is asked once and is final for that connection.
Saying yes syncs recent conversation history to the API, so software starts with context rather than blind. Saying no means the API sees only messages from the moment it connects. Both are reasonable, and most integrations care about new conversations, but the decision cannot be revisited without disconnecting and connecting again.
There is also a window on it. The synchronization has to be started within 24 hours of onboarding, and it can only run once. Missing either produces an unfamiliar error rather than a warning, which is why history is worth deciding on the day rather than during integration work.
What should be ready before starting?
Three things, and having them saves the flow being abandoned halfway.
Access to the Business Portfolio that owns the number, which is usually the business owner rather than whoever is doing the integration. The phone with the number, unlocked and with the WhatsApp Business app installed. And ideally the webhook destination, because setting it at the end of onboarding is cleaner than remembering later.
If the flow is closed before it finishes, the number can end up attached to the account but not registered, which produces an error on the first send. Running the flow again from the start fixes it.
Common mistakes
- Starting without the phone nearby. The scan cannot be done later from a different device.
- Closing the popup once the number appears. The flow has steps after that and stopping leaves it unregistered.
- Leaving the history decision until the integration is built. It expires 24 hours after onboarding.
EasyCoexistence runs Meta's flow and then watches what it produced, recording each step on the connection timeline. US$ 9 per number per month, first 7 days free.
Frequently asked questions
Can I connect a number I do not own?
Only the business that owns it can authorise it. You send them a link and they complete the flow on their own phone.
Does the app stop working during onboarding?
No. It keeps working throughout, including while the code is being scanned.
What if the number is on the consumer WhatsApp app?
It has to be moved to the WhatsApp Business app first. Coexistence connects a Business app number.
Can I redo the flow?
Yes. Disconnecting and connecting again reruns it, including a fresh chance to accept chat history.
Keep reading
Ready to get started?
Set up WhatsApp Coexistence in minutes, not months. The app keeps working on the phone.
Start Free TrialNothing charged for 7 days. Cancel anytime.Verified on