One of our customers lost their WhatsApp Business Account mid-week, at volume, with no prior warning in the dashboard. Messages stopped, the number went dark, and the contact centre found out from customers rather than from Meta. They were live again on another number the same day. That is the outcome this piece is about, because the difference between a day and a fortnight is almost entirely preparation.
What actually triggers it
Bans are rarely about one message. They are about a pattern crossing a threshold, and the thresholds are not published. In practice the recurring causes are these:
- Quality rating falling. Blocks and "report" taps from recipients drive it down. A campaign to a cold or stale list will do it in a day.
- Template drift. A template approved for one purpose used for another — a utility template carrying a marketing message is the classic.
- Policy category mismatch. Commerce and messaging policies differ by market, and what is fine in one country is not in another.
- Business verification gaps. An unverified or partially verified business is far less resilient when a complaint lands.
The first hour
Do not spend it appealing. Appeals are worth filing, but they resolve on Meta's clock, not yours. Spend the first hour keeping the operation running.
- Fail the traffic over to your other channels — voice, web chat, Instagram, email — so customers reaching out still land somewhere staffed.
- Bring up a secondary number on the same Business Manager if you have one provisioned. This is the step that turns a fortnight into a day.
- Post the alternative contact route publicly — your site, your IVR greeting, your social bios.
- File the appeal with specifics, and preserve the message history you will be asked for.
How to not be here again
Provision a second number before you need it. Keep your quality rating visible on a dashboard someone actually looks at, not buried in Business Manager. Separate utility and marketing templates strictly, and review them when Meta updates policy rather than when something breaks. And make sure the customer conversation history survives the number change — if the history lives with the number rather than with the customer, you lose the relationship along with the channel.
That last point is the one most operations discover too late. A platform that keys conversation history to the phone number will hand you a clean slate on recovery day. One that keys it to the customer will carry five years of context onto the new number.