Surviving a WhatsApp ban with a standby number
Most advice about bans is about avoiding them. This is about the morning one happens anyway: what a standby number can carry across, what it cannot, and why setting it up afterwards is too late.
Almost everything written about WhatsApp bans is about prevention, and prevention is worth doing — we have a page on it. This is about the other morning: the one where it happened anyway, to a number your customers have saved, that your invoices are printed with.
A ban is survivable. It is survivable in proportion to how much of the work you did before it happened, and essentially not at all if you start when it does.
What actually stops
When a number is restricted, several things fail at once, and they are worth separating:
| What | Status |
|---|---|
| Sending and receiving | Gone immediately |
| Chat history on the handset | Still there — it is local |
| Your customers’ view | Your messages stop. Nothing tells them why |
| Contacts and conversation records in your software | Unaffected — they are yours |
| Automations pointing at the number | Running, failing, usually silently |
| Printed and cached references to the number | Everywhere, and now wrong |
The expensive part is the last two. Your flows keep trying, your website keeps showing the number, and your customers keep messaging a number nobody is reading — for as long as it takes you to find and change every reference.
Why the second number has to exist first
The instinct is to buy a SIM the morning it happens. That is the worst possible time, because a brand-new WhatsApp account is the most fragile thing in this ecosystem:
- A number registered today, immediately sending to hundreds of contacts, is a textbook spam pattern. The replacement gets restricted faster than the original.
- It has no history, no established conversations, and no reply rate — which are the things WhatsApp weighs.
- It cannot be warmed up retroactively. Warming takes weeks of ordinary, modest, answered conversation.
A standby number that has been quietly alive for a month — used a little, replied to, never blasting — is an account with a history. It survives being switched to. A SIM bought this morning does not.
What can move across, and what cannot
| Moves? | Notes | |
|---|---|---|
| Contacts | Yes | They live in your system, not in the number |
| Open conversations | Yes, as records | The thread on the customer’s phone stays with the old number |
| Flows and automations | Yes | If they point at a session rather than a hardcoded number |
| AI agents and knowledge | Yes | Attached to the session, not the SIM |
| Webhooks and integrations | Yes | Same, if they were configured by session |
| Chat history on customers’ phones | No | Nothing can move this. It is on their device |
| The number itself | No | That is the whole problem |
| Your customers knowing | No — you must tell them | The single biggest task on the day |
Telling people, without getting the new number banned
Here is the trap. The obvious move is to message every contact from the new number announcing the change. That is a brand-new account sending a bulk unsolicited broadcast, which is precisely the behaviour that restricts numbers.
Safer, in order:
- Change it where you control the surface first — website, widget, email footer, invoices, social profiles. Free, instant, and it catches new enquiries.
- Tell people who message the old number, if it is readable at all. Often it is not.
- Use another channel to announce it. Email and SMS are the right tools for this, and neither will ban you for it.
- Then, slowly, to recent active contacts only. People who messaged you in the last few weeks, paced over days, not a list of four thousand in an afternoon.
What to set up now
- Get a second number and register it. Today, not later.
- Use it lightly and regularly. Real conversations, however few.
- Make sure nothing hardcodes the primary. Every integration should point at a session you can repoint, not a number in a config file.
- Know where the number is published. Write the list down now; you will not enjoy compiling it under pressure.
- Rehearse the switch once. The first time you do it should not be the day it matters.
How WaveSenda handles it
A standby number is registered as a second session and nominated as the failover. When the switch happens, agents, flows, webhooks and open conversations move to it, because they were attached to a session rather than to a number. The website widget follows automatically, since it forwards to whichever session is live.
Recent contacts can be told, paced rather than blasted. It does not fail back on its own — an automatic switch back to a number that is still in trouble would be worse than the problem.
Common questions
How long does a WhatsApp ban last?
Temporary restrictions are typically hours to days. A permanent ban is permanent unless an appeal succeeds, and appeals are answered by an automated system far more often than by a person. Plan for the possibility that the number never comes back.
Can I appeal a WhatsApp ban?
Yes, through the app or the support form, and it is worth doing immediately because the appeal is stronger while the account is fresh in the system. Keep it short and factual. Do not appeal repeatedly — it does not help and can hurt.
Will using a standby number get that one banned too?
Only if you use it the way the first one was used. A ban is caused by behaviour, and moving the same behaviour to a new number moves the outcome with it. The standby buys you continuity, not immunity.
Can I move my chat history to the new number?
Not on your customers’ phones — that history is on their devices and belongs to the old thread. Your own records of those conversations move, so your team keeps the context even though the customer sees a new thread starting.
Should I just use the official Business API instead?
It changes the failure mode rather than removing it: quality ratings fall, sending limits are cut, and numbers can still be disabled for policy breaches. It is more predictable and has a real appeals process, which is a genuine advantage — see our comparison of the two routes.