How to enable WhatsApp Coexistence: a step-by-step setup guide

To enable WhatsApp Coexistence you need three things: the number running on the WhatsApp Business app (not regular WhatsApp), that number not connected to any other API, and the number's owner with the phone in hand. Setup runs through Meta's Embedded Signup: you start the connection from your provider, authorize it inside Meta's flow, scan a QR code in the app and let the history sync finish. Then you test that conversations show up on both sides. The connection itself is quick. What goes wrong usually happens before it (a requirement nobody checked) or after it (nobody tests anything).

The pre-flight checklist

Most failed setups trace back to one skipped line here. Run through it before you click anything:

• the number is on the WhatsApp Business app, the business one, not personal WhatsApp
• the number is not connected to another API through any other provider
• whoever runs the setup has the phone with the app on it
• you picked a time when nobody will touch the configuration for the next few hours
• your team knows that broadcast lists and a few other app features will be locked
• you know what you want the API to do first: track ad conversations, send reminders, get reports

The second line is the one that blocks people most often. A number can only sit in one API at a time. If someone once hooked this number up to a bulk-messaging tool or a support platform and never unhooked it, that has to be undone first. Each requirement is covered in detail in coexistence requirements.

The fifth line is the one that generates complaints a week later. While the API is connected, the app loses broadcast lists, disappearing messages, view once and live location. Groups stay on the phone but sit outside the API. If your sales rep relies on a broadcast list to announce promos, sort out the alternative before you connect, not after.

Step 1: start from your provider, not the app

Coexistence is not a toggle inside WhatsApp Business. It starts on the platform of the provider that will connect to your number, which opens Meta's official flow: Embedded Signup.

Before you start, confirm two things with that provider. First, that they actually offer coexistence and not only full migration. Second, how they bill. You will have two separate bills: Meta's, per message sent through the API, and the provider's. If a vendor only says "we connect your WhatsApp," ask it plainly: "Will my team keep replying from the app, on the same number?"

Step 2: authorize inside Meta's flow

Embedded Signup is a window run by Meta itself. That is where the number's owner authorizes the connection. The provider never gets a password and never needs your phone: the decision is yours, inside Meta's environment.

A practical tip: have the person who actually owns the number and the business account do this step. Handing it to a contractor or an intern who lacks that access is the most common way to end up with a half-finished connection.

Step 3: scan the QR code in the app

At some point in the flow, a QR code appears. You scan it with the WhatsApp Business app on the number's phone. This is the step that links the app to the API without taking the number off the device.

If the number is on personal WhatsApp, this step will not work. Coexistence requires the business app.

Step 4: let the sync finish

After the QR scan, Meta syncs up to six months of history from the app. It takes anywhere from minutes to hours and happens only once. From then on, everything that comes in and goes out is recorded live.

Nobody can promise you an exact time, because it depends on how many conversations the number has. What you can do is stay out of the way: do not restart the process, do not disconnect to "try again," and do not kick off a second connection in parallel. Because the sync happens once, interrupting it is the easiest way to end up with partial history. More on this in how the history sync works.

Step 5: run these tests after connecting

Connecting is not the finish line. This is where you find out whether it actually worked, and the tests are quick:

One note on the send test: the Cloud API's 24-hour window only opens when the customer messages you. That is why the test starts with a message from outside to your number. Messages your team sends from the app do not open, extend or affect that window, and they are not billed. Outside the window, a business-initiated message sent through the API needs a template approved by Meta.

What to watch in the first few weeks

Setup worked. Now come the problems that only show up over time.

Open the app regularly. If nobody opens WhatsApp Business for roughly 14 days, Meta can drop the connection. This mostly hits numbers that exist to catch ad leads and that nobody checks daily, like a lead line for a roofing company that the owner forgets about during busy season.

Do not swap broadcasts for mass manual sends. With broadcast lists locked, it is tempting to paste the same message to dozens of contacts from the phone. That is exactly the pattern Meta penalizes. Your quality rating drops and blocks still count. See WhatsApp number quality.

Know the throughput cap. The number gets a limit of 20 messages per second. For customer support that is plenty. If you were planning large sends, factor it in.

Automate one thing first. An appointment reminder, an order received notice, an internal report. The plan for the first month is in first 30 days with coexistence.

Troubleshooting a stuck setup

The usual snags and what to do about them:

The flow will not accept the number. Most often it is still connected to another API. Disconnect it at the previous provider and try again. One number, one API.

The QR code will not scan. Make sure you are scanning from the WhatsApp Business app, not personal WhatsApp, and on the phone that actually holds that number.

The sync looks frozen. It can take hours. Give it time before you decide something broke. Restarting halfway usually makes things worse.

The connection dropped weeks later. Almost always, the app went unopened for around 14 days. Assign someone to open the number's WhatsApp Business regularly.

Other problems that crop up after setup are covered in WhatsApp coexistence mistakes.

Your next move

Run the checklist, confirm the number is on the business app and free of any other API, and block out a quiet window to connect. To see what the module does before you commit, the WhatsApp Coexistence page walks through it. When you are ready, create your account: your first 7 days cost US$ 2.99.