Blocked WhatsApp number: what to do, step by step

Many "number down" cases are only a disconnected session, which has nothing to do with a ban. Check the instance status through the API: if it comes back "disconnected" or "connecting", the path is to reconnect. If the phone app also shows a restricted or banned account warning, WhatsApp is acting.

At ZapZap the check is a simple GET on the status endpoint; the example is just below. If it is only a disconnection, request a new QR code (QR code endpoint) and scan it with the phone. Scanning the code again does not change the account's state at WhatsApp.

curl https://api.zapzapapi.com/api/v1/SEU_INSTANCE_ID/instance/status \
  -H "x-api-key: SUA_API_KEY" \
  -H "x-api-secret: SEU_API_SECRET"

curl https://api.zapzapapi.com/api/v1/instances/SEU_INSTANCE_ID/qrcode \
  -H "x-api-key: SUA_API_KEY" \
  -H "x-api-secret: SEU_API_SECRET"

The exact wording of the warnings changes with WhatsApp versions, so go by what appears on your own device's screen. Photograph or note the warning: it is your best piece of information.

Stop campaigns and automations on that number, including ones that resend. Insisting on a restricted number only makes things worse. Pause webhooks that trigger automatic messages from it. If you have other numbers, do not move all the volume to them at once: that repeats the pattern that caused the problem.

Export what you can: contacts, history and conversation state. If you already keep history in your CRM, great. If not, use the API's message search while the session is still reachable and record what matters.

When WhatsApp itself shows a button or link to request a review, use it once, with an objective and truthful text, without exaggerated complaints. There is no guaranteed timeframe and no guarantee of reversal, and the decision belongs to the platform. Avoid filing several requests in a row.

Do not pay anyone who promises to "unban" a number with certainty. No outsider controls that decision, and the offer is usually a scam. See also the guide banned number: what to do.

Review the last week of operation: was the audience cold? Was there a volume spike? Was the text identical? Was the number new? Were there reports or many negative replies? Cross-check with the risk matrix by type of use to find the most likely factor.

Without an identified cause, the next number falls for the same reason. Document the most likely cause and the change you will make.

A new number needs warm-up: start with one to one conversations with people who already know you, increase gradually and track replies. Use the warm-up checklist as a routine.

If your operation depends on a single number, this is the moment to split functions and keep a warmed-up spare. The API has an endpoint for new conversation limits to follow progress. See several numbers in one system.

Do not reconnect the same number on several devices or providers in sequence, do not fire a "new number notice" to your whole list at once, do not buy numbers of dubious origin and do not use tools that promise to evade detection. Also do not wipe everything in a hurry: preserve evidence and history.

And remember the premise: WhatsApp can restrict an account that uses unauthorized automated means, according to its Terms. If losing the number is unacceptable for your business, consider Meta's official API.

Hour 0 to 1: confirm the type of problem (instance status and the in-app warning), stop campaigns and automations on the number and tell whoever handles support. Hour 1 to 4: export contacts and history that are still reachable, note the exact text of the warning and list what was sent in recent days.

Day 1: if there is a review path, file a single request. Decide which critical conversations must move to another channel (phone call, email, another warmed-up number). Day 2: with the likely cause identified, plan the new or spare number and the change in behavior. Do not resume volume until the plan is written down.

Customers who depend on the channel need a clear alternative. Use email, phone or your site to say that support is temporarily on another contact, and only send the new number to people who already talk to you, in small groups, not to the whole list at once. A mass "new number" notice repeats the blasting pattern that tends to generate reports.

Be objective, do not blame the platform and do not promise timeframes you do not control. Record who was told and through which channel, so you can resume history when the new number is ready. If your support is critical, it is a good time to weigh the official API as the main channel and leave the unofficial one for day to day conversation.

Prevention is routine, not an event. Keep a warmed-up spare number, split functions across different numbers, keep contacts and history in your CRM and track reply rate, exit requests and undelivered messages weekly. Whoever does this turns a block into a few days of annoyance instead of a business outage.

Also review the text of your automated flows: identical replies sent to many people in little time are an easy pattern to recognize. Varying wording, spacing sends and offering an easy exit remain the cheapest and most effective measures, even though they do not remove the risk.