WhatsApp connection problems, and what each one means
Most stalled connections are one of six things, and two of them are not errors at all.
A connection that will not complete is frustrating precisely because the error messages are written for developers. In practice there are about six causes, two of which are not problems at all, and you can usually tell which you have in under a minute.
This page is the translation.
The six causes
| What you see | What it means | Who fixes it |
|---|---|---|
| Connected, but the number never goes active | Often a two-step PIN on the number | You, then support |
| "Already registered" | Usually benign — the number is registered and working | Nobody |
| Still on the WhatsApp Business app | The coexistence path. Expected, and it settles on its own | Nobody — wait |
| A payment error that will not clear | The card is on the wrong account | You, in Meta billing |
| Signup popup closes with nothing saved | Wrong Facebook account, or a blocked popup | You |
| Connected but cannot send templates | No approved templates yet, or a payment block | You |
Note the third row. A number coming from the WhatsApp Business app reports something that reads like a failure and is the normal, expected route — it activates shortly by itself.
The two-step PIN, which is the real one
If the number has two-step verification enabled and the PIN is not available, registration is refused. There is no way around it and retrying does not help.
Two fixes:
- Turn two-step verification off on that number in the WhatsApp app before connecting.
- Supply the PIN to whoever is completing the registration, if turning it off is not possible.
Doing the first before you start removes the whole category. It is the single most useful piece of preparation on this page, and it takes about thirty seconds.
"Already registered" is usually good news
It means the number is registered on the platform. In the common case the registration succeeded and the message is describing a state rather than a failure.
Where it is genuinely a problem is when the number is registered somewhere else — an old provider, an account you no longer control. That is a move rather than a fresh connection, and the route is in migrating your number.
When the popup itself fails
The connection happens inside Meta's own window, which is why it is quick and also why the failures are opaque. Three checks, in order:
- Are you logged into the right Facebook account? The one that owns, or will own, the business. Personal accounts with no business attached are the usual cause.
- Is the popup blocked? Browser extensions and popup blockers close it silently.
- Did you finish it? Closing the window early leaves nothing saved — the flow is short but it does have to complete.
Trying again in a normal browser window, logged into the right account, resolves most of these.
Connected, but nothing sends
A separate class of problem, and worth distinguishing because the connection is fine. Two causes:
No payment method reaching the account. The most common, and it is a layers problem rather than a card problem — see adding a payment method.
No approved templates. A first message to a customer who has not messaged you needs an approved template, per Meta's template documentation. Replies inside the 24-hour window need nothing, which is why inbound conversations work while outbound ones do not.
A diagnostic order that works
- Can you receive a message? Send one to your business number from your own phone. If it arrives, the connection is real.
- Can you reply? If yes, everything except templates is working.
- Can you send a template? If not, it is payment or template approval, in that order of likelihood.
- Check the account health status your onboarding checklist reads — it names payment and eligibility problems directly.
- Then ask for help, with the answers to the first four.
Those four answers turn a support conversation from an hour of questions into a single reply, which is worth the five minutes.
What to do while you are stuck
Keep going on everything that does not depend on it. Draft and submit your templates — approval takes time you may as well spend now. Build your flows as unpublished drafts. Write your knowledge base answers.
None of that needs a working connection, and it means the day the connection clears you are ready rather than starting. The sequence is in your first 30 days.
Frequently asked
How long should activation take?
The signup itself is a few minutes. A coexistence number settles shortly after. Anything measured in days is a real problem rather than patience.
Will disconnecting and reconnecting fix it?
For a permissions problem, sometimes. For a two-step PIN, never — the PIN is still there.
Can I test before customers arrive?
Yes, and you should. Message your own business number from your own phone and run your flows against it, as described in testing an automation safely.
Is a rejected business verification fatal?
No. Fix the flagged detail and resubmit — a rejection is not final, and it does not stop you starting.
Preparation that removes most of this
Five minutes before you start, and it eliminates four of the six causes:
- Turn off two-step verification on the number in the WhatsApp app.
- Log into the correct Facebook account — the one that owns the business.
- Use a normal browser window with popups allowed.
- Know whether the number is already on WhatsApp, and where.
- Have the payment method ready to add immediately afterwards.
None of these are difficult; they are just easier to do before than to diagnose after.
What "connected" actually guarantees
Less than people assume, which is why so many problems appear after a successful connection. A connected number means messages can flow. It does not mean you can start conversations.
| Capability | Needs |
|---|---|
| Receive customer messages | A connected number |
| Reply within 24 hours | A connected number |
| Message a cold chat | An approved template and a payment method |
| Reach more than 250 people a day | A higher messaging tier |
| Send marketing | All of the above, plus opt-in |
The bottom two rows are worth knowing early. Your messaging tier starts at 250 unique recipients per rolling 24 hours and climbs 250 → 2,000 → 10,000 → 100,000 → unlimited per Meta's messaging limits documentation — so "connected" and "ready to run a campaign" are different states, sometimes weeks apart.
When to stop debugging and ask
Three signals that the problem is not one you should keep poking at:
- A two-step PIN you do not have. No amount of retrying helps.
- The number is registered to an account you cannot access — an old agency, a former provider.
- Nothing has changed in more than a day on a number that is not on the coexistence path.
In all three cases the next step is a person rather than another attempt, and arriving with the diagnostic answers above makes that conversation short.
The short version
Six causes. Two of them — "already registered" and a number still on the WhatsApp Business app — are not problems. One, a two-step PIN, cannot be fixed by retrying and should be cleared before you start. The other three are the payment method, the signup popup, and simply not having templates yet.
Work out which by sending yourself a message, replying to it, then trying a template. Each step that works rules out a whole class of cause, and the first one that fails names the problem.
A note on patience
Two of the six causes resolve themselves, and the instinct when a connection looks stuck is to disconnect and try again. That instinct makes the coexistence case worse, because reconnecting restarts a process that was already going to finish.
The rule of thumb: if the number came from the WhatsApp Business app, give it time before you touch anything. If it did not, and nothing has changed in an hour, start working through the causes above.
Frequently asked, part two
Does a failed attempt use anything up?
No. There is no penalty for a signup that did not complete.
Can I connect from a phone?
It works, and a desktop browser is easier — the Meta popup involves several steps and a small screen makes it harder to see what you are agreeing to.
Is there a way to check without messaging myself?
The account health status your onboarding checklist reads is the closest thing, and it names payment and eligibility problems directly. A real test send is still the better proof, because it exercises the whole path rather than one report.
My connection worked and then stopped.
That is a different problem from a connection that never worked. Look at billing first — an expired card produces exactly this — and then at whether a template was paused.
Should I keep retrying the signup?
Once, in a clean browser window, logged into the right account. Beyond that, repeated attempts do not fix any of the six causes and they make the coexistence case slower rather than faster.
Who should I ask for help?
Your provider first, with the four diagnostic answers above. Meta's own support is the right escalation only for things that live with Meta — business verification and billing.