WhatsApp Business banned: why it happens and how to recover

A WhatsApp Business ban is Meta deactivating a business number's access to WhatsApp — and it happens in four different places: the WhatsApp Business app, a number connected to the official API, the entire WhatsApp Business Account (WABA), and the Meta Business portfolio. Each of these cases has its own appeal channel, and mixing one up for another costs days.

The path, in any of them, is to request a review through the right channel, with the number in international format (+55 and area code) and an honest description of the business use — and to do that before you go off registering the SIM on another device. But the question that comes first is which account was banned. In one case you get a warning by email, with a stated deadline. In the other, you find out from a locked screen.

This guide separates the cases, gives the step-by-step for each, and faces the point almost no content on the topic addresses: the official API does not eliminate ban risk. What it changes is how much of it you can see coming. The error codes and webhook fields cited here were checked in Meta's documentation as of August 2026.

Which WhatsApp account got banned?

Confusing these cases costs time. Whoever has a deactivated WABA and keeps requesting a review from the phone is knocking on the wrong door — and the appeal clock keeps running on the other side.

Why does Meta ban a business account?

The official policy covers a long list of violations, but in practice what takes down a business number fits into six items:

1. No opt-in. The rule is dual: the person needs to have given you the number and authorized the contact. A purchased list, a base scraped from a group, and an event spreadsheet don't pass that test.
2. Block and report rate. This is the strongest signal there is. The algorithm doesn't read your message's content — it counts how many people tapped "block" and "report" after receiving it.
3. Modified apps. GB WhatsApp, WhatsApp Plus, and clones violate the Terms by definition. It's worth understanding the real risk of these apps before justifying their use for one extra feature.
4. Abnormal volume on a new number. A SIM activated this week sending hundreds of messages is the exact pattern of a disposable scam account.
5. Automation outside the official path. A bot plugged into WhatsApp Web to bulk-send is the classic scenario of a spam ban.
6. Prohibited content. Restricted products, financial promises, deceptive content.

Notice what's not on the list: selling on WhatsApp. Selling is allowed and encouraged. The problem is never being a business — it's the how of the sending.

Does the WhatsApp Business app warn you before a ban?

No. This is the uncomfortable part. On the WhatsApp Business app — and the same goes for QR code connections, which use the same account as the app — there's no dashboard showing the number's health before the problem: no quality score, no alert email, no intermediate signal. You operate in the dark, and the first warning is usually the block screen itself.

That doesn't make QR code unviable. It handles legitimate cases, it's cheap, and it connects in minutes. But the trade-off needs to be clear when choosing: you're trading visibility for simplicity. Whoever depends on WhatsApp for revenue is betting the whole channel on a system that gives you no statement.

Does the official WhatsApp API also ban a number?

It does. The claim that "the official API doesn't ban" is false, and the proof is right in Meta's own documentation. The account_update webhook carries a field called waba_ban_state, with three possible values:

• SCHEDULE_FOR_DISABLE — the account is flagged for deactivation.
• DISABLE — it's been deactivated.
• REINSTATE — it's been reactivated after an accepted appeal.

A field like that wouldn't exist if a number on the official API couldn't be banned. And when the account is blocked for a policy violation, sending calls start returning error 368 (code verified as of August 2026).

So what changes between one path and the other? Everything that happens before that: the scoreboard, the warning, and the appeal channel.

What does the quality rating show before a ban?

Every number on the official API carries a quality rating — green, yellow, or red — calculated on a weighted window of the last 7 days (criteria documented by Meta and checked as of August 2026), visible in WhatsApp Manager and via the API. Yellow is the alarm going off while the door is still open: you can pause the campaign, swap the template, and clean the list before the score turns red. On the regular app, that number simply doesn't exist.

Along with the score comes a written warning. A drop in quality and a policy violation trigger an email notification to the Business Manager admin, with the fix deadline stated right in the notice. It isn't a favor from Meta: it's the difference between discovering the problem while the operation is still running and discovering it once the number's dead.

How restriction escalates toward deactivation

There's no guarantee all these signals appear, or in this order — Meta can deactivate directly in a severe case. But every row in the table is a chance to catch the problem before the end. On the regular app, none of them exist: the first signal is the block screen, and the appeal is the only step.

Can you send a message outside the 24-hour window?

On the official API, no — and that eliminates a whole cause of bans. Sending a free-form message outside the 24-hour window isn't an infraction you commit and pay for later: it's a call the API refuses. The response comes back with error 131047 (code verified as of August 2026), and only an approved template reopens the conversation.

On QR code, nothing stops the send. The app lets you send whatever you want, to whoever you want, at any hour — and that's exactly where the report is born. The official API's technical guardrail isn't bureaucracy: it's the mechanism that prevents the most common mistake made by anyone selling on WhatsApp.

How do you recover a banned number on the WhatsApp Business app?

1. Tap "Request a review" right on the block screen. It's the fastest channel and the only one that already arrives identified.
2. If the screen shows a countdown, the block is temporary: wait out the deadline shown and, if you're on a modified app, uninstall it and switch to the official one before coming back.
3. With no countdown, it's permanent. Besides the app, you can write to support giving the full number in international format, with +55 and the area code.
4. Describe the real use in three lines: who you are, what customers reach out to you, and that you don't send to cold lists or use an unofficial app. Specific beats generic every time.
5. Don't try registering the number on multiple devices while you wait. That makes things worse and doesn't speed anything up.

The full breakdown of this route is in the WhatsApp banned and the review path guide.

How do you appeal a ban on the official API?

1. Open WhatsApp Manager and read the stated reason. Unlike the app, here there's a written reason — start there.
2. Check the number's quality rating and the history of rejected or paused templates within the 7-day window Meta uses in the calculation.
3. Fix it before appealing. Pause the campaign that generated blocks, remove the list with no opt-in, adjust the template. An appeal with no fix comes back denied.
4. Submit the appeal through WhatsApp Manager's form, stating what changed. Don't write "we don't know what happened" — write "we identified that template X was sent to a base with no logged opt-in; the base was removed and the template unpublished."
5. Track the account_update webhook. The value REINSTATE confirms the account is back.

It's not a guarantee of winning. It's predictability: you know where to appeal, what to fix, and where the response arrives.

What to never do while the appeal is pending

Don't pay for an "unbanning service." There's no paid channel running parallel to Meta — it's a scam built on top of people who are already in trouble, and handing Business Manager access to a stranger trades one problem for two.

It also doesn't help to switch to a modified app to "come back faster," register the number on multiple devices at once, or open a new number to keep sending exactly the same way. In all three cases you repeat the behavior that caused the block, now with a history. While the appeal is pending, the best move is to stop active sending and clean up the base.

What changes in the operation after coming back

Recovering the number solves today's problem. What prevents the next episode is a lot less glamorous:

• Get the customer to start the conversation whenever you can. A WhatsApp link on your website and on Instagram converts cold contact into requested contact — and whoever starts the chat doesn't report you.
• Add an explicit opt-out to every recurring communication and honor the request the same day. Reports are the fuel of a ban; opt-out is the extinguisher.
• Respect the adaptive marketing limit. There's no public "messages per day" figure — the limit varies by user and by business. When you exceed it, the API returns error 131049 (code verified as of August 2026). That error is a warning, not a suggestion.
• Scale only through the official path, with approved templates and controlled pacing.

If WhatsApp pays the company's bills, it's worth understanding what the official connection costs and what it delivers in multi-agent support and history off the device. On CRPRO you can connect through the official API or through QR code — and now you know what you gain and give up with each one.

Frequently Asked Questions

Does the official WhatsApp API prevent bans?

No. Meta keeps the waba_ban_state field in the account_update webhook and error 368 precisely because accounts on the official API can be deactivated. What the API gives you is a visible quality rating on a 7-day window, an email warning with a stated fix deadline, intermediate signals before deactivation, and a formal appeal with a decision trackable through the webhook. The regular app bans with no warning at all.

How long does it take to recover a banned WhatsApp Business account?

Depends on the channel. Through the in-app review, the response usually arrives within hours to a few days. On the official API, the appeal is formal and the decision comes back through the account_update webhook; the timeline varies by case. A temporary ban with a countdown resolves itself at the deadline shown on screen.

Do I lose my conversations and contacts when the number is banned?

On the app, access to the history on the device gets blocked along with the account — that's why backups matter. On the official API, the history lives on the connected platform, not on the phone, so it stays accessible even with the number suspended.

I got banned without doing anything wrong. Is that possible?

Yes. Coordinated reports and false positives from the algorithm happen. The review resolves a good share of these cases — describe the number's real use instead of arguing that Meta made a mistake.

Can I switch numbers and keep going as before?

Technically yes, in practice it's expensive. A new number on the official API resets to the starting sending tier, needs to rebuild reputation, and waits on template re-approval. And if the cause of the ban was how you were sending, the new number drops for the same reason within a few weeks.

Does a QR code connection carry more ban risk than the official API?

The risk isn't higher because it's QR code — it's more blind. The account is the same one the app uses: no quality score, no advance warning, no intermediate signal, and no guardrail stopping a send outside the 24-hour window. You only find out about the problem once it's already turned into a block.