WhatsApp Business Account Restricted or Banned: The 48-Hour Recovery Playbook

Appeal speed is the single biggest predictor of a successful recovery. Appeals submitted within 24 to 48 hours succeed far more often than those filed a week later, where reported success rates fall below 20%. Whatever else is happening, file the appeal today.

Last verified: August 2026 against Meta Business Suite and WhatsApp Business Platform policy. Meta revises enforcement mechanics regularly - confirm current steps in Account Quality before acting on anything business-critical.

Do these in order:

1. Stop all outbound sending immediately. Pause campaigns, disable scheduled template sends, and turn off any automation that initiates conversations. Continued sending during a restriction worsens your position, and if the trigger was volume or complaints, every additional message adds evidence against you.
2. Open Account Quality and read the actual status. In Meta Business Suite, go to Account Quality (or Business Support Home) and find your WhatsApp Business Account. "Restricted" and "banned" are different states with different paths back, and people frequently panic about the wrong one.
3. File the appeal. Select the restricted asset, choose Request Review, and submit. You can refine your understanding of the cause afterwards - what you cannot recover is the time advantage of appealing early.

Only after those three should you start diagnosing. The diagnosis matters enormously for whether the account survives long term, but it does not need to happen before the clock starts.

Meta uses several enforcement levels and they are commonly conflated. Identify yours precisely, because the recovery path differs.

Quality rating is a rolling window, not a permanent score

Quality rating is calculated from recent recipient feedback - blocks and reports - over a rolling period. That has two consequences worth internalising.

A rating can drop from green to red within days if a single badly-targeted campaign generates complaints, so a healthy history offers less protection than people assume. And a rating recovers on its own once the bad signal ages out, provided you stop generating new complaints. A yellow rating requires no appeal and no support ticket - it requires you to stop doing whatever caused it.

Reduced messaging limits recover automatically

If your tier dropped - say from 10,000 unique customers per day to 1,000 - that is an automated consequence of quality, not a manual enforcement action. It restores itself as quality recovers. Appealing a tier reduction is not the mechanism; fixing the underlying complaint rate is.

You need a genuine diagnosis, because a successful appeal that does not address the cause leads to a second restriction within days - and second restrictions are much harder to reverse.

1. Messaging people who never opted in

By a wide margin the most common cause. WhatsApp requires explicit opt-in to receive business messages, and the standard is higher than most marketing teams apply elsewhere. Having someone's phone number from a purchase, a form, or a business card is not opt-in for WhatsApp specifically. The customer must have agreed to be contacted on WhatsApp, and you should be able to show when and how.

2. High block and report rate

The direct input to quality rating. Every recipient who blocks or reports you feeds it. This is why untargeted broadcasts are so dangerous: sending to 10,000 marginally interested contacts can generate enough blocks in an hour to move you from green to red.

3. Purchased, scraped or rented lists

A special case of the first, and the fastest route to a permanent ban. These lists produce extreme block rates because recipients have no idea who you are. Meta is also reasonably good at recognising the pattern - a brand new number sending to thousands of unrelated contacts is exactly what abuse looks like.

4. Sudden volume spikes

Going from 200 messages a day to 20,000 overnight is an abuse signal regardless of consent, because compromised accounts behave that way. Ramp deliberately - increase volume over days, not in a single step, particularly on a number without an established history.

5. Wrong template category

Sending marketing content under a utility template is a policy violation, not just a billing question. Meta detects the mismatch and it counts against your account. Our guide to WhatsApp template rejections covers the category test in detail.

6. Prohibited goods and services

Selling anything on WhatsApp's Commerce Policy prohibited list - alcohol, tobacco and vaping, drugs and many supplements, weapons, gambling, adult content, medical devices - can restrict the account regardless of how the messages are worded or how enthusiastically recipients opted in.

7. Unofficial tools and modified clients

Bulk senders built on unofficial libraries, modified WhatsApp applications, and automation that drives the consumer app all violate the terms. Detection is reliable and the usual outcome is a permanent ban rather than a restriction - typically on the number printed on your packaging, invoices and storefront. There is no version of this that is worth the saving.

Appeals are read by a human. That means the content genuinely matters, and most appeals fail because they argue the wrong thing.

Where to file

Meta Business Suite -> Account Quality -> locate the restricted asset under Business Support Home -> Request Review. Submit any supporting evidence in the same flow.

What actually persuades

The reviewer is deciding one thing: is this business likely to generate complaints again? Everything in your appeal should answer that question. A structure that works:

1. Acknowledge the likely cause specifically. "We believe the restriction resulted from a campaign on 14 July sent to a segment that had opted into email but not WhatsApp." Naming it demonstrates you understand what went wrong, which is the strongest possible signal that it will not recur.
2. State what you have already changed - in the past tense, not as a promise. "We have removed 4,200 contacts without a WhatsApp-specific opt-in, and suspended all marketing sends pending review."
3. Describe your opt-in mechanism concretely. Where it appears, what the wording says, whether it is a separate checkbox, and how consent is recorded with a timestamp.
4. Attach evidence. A screenshot of the opt-in checkbox, your privacy policy section on WhatsApp messaging, an example of the consent record. Evidence turns an assertion into a verifiable claim.
5. Keep it factual. No pleading, no revenue impact, no mention of how many staff depend on the account. It does not influence the decision and it displaces information that does.

What guarantees rejection

• "We don't know why this happened" - reads as an intention to repeat it
• Blaming customers for reporting you
• Boilerplate that does not mention your actual business
• Filing several appeals for the same asset, which resets rather than accelerates the queue

Timelines and outcomes

WABA appeals typically take 3 to 14 days, though simpler cases can resolve in 24 to 72 hours. Most successful appeals return a quality-score reset rather than a clean verdict - meaning you can send again but you are effectively on probation. One further violation at that point commonly leads to permanent suspension.

Treat reinstatement as a second chance with a much lower tolerance, not as vindication.

This is where most accounts are lost for good. The account is restored, the pressure returns, someone resumes the campaign calendar, and the same complaint pattern reappears against a much lower threshold.

Clean the list before you send anything

If you cannot demonstrate WhatsApp-specific opt-in for a contact, remove them. This is uncomfortable - lists shrink substantially - but sending to that segment is precisely what caused the restriction, and it is what will cause the next one.

The right way to rebuild is to re-permission through a channel you are not at risk on: an email or website prompt asking people to opt in to WhatsApp explicitly. A smaller list of people who chose the channel outperforms a large list that did not, on every metric including revenue.

Almost every restriction is preventable with controls that take an afternoon to implement.

• A WhatsApp-specific opt-in checkbox, separate from email consent, with the wording stored alongside a timestamp. This is both your prevention and your appeal evidence.
• An honest opt-out in every marketing template. A visible "Reply STOP to unsubscribe" costs a few opt-outs and prevents blocks - and a block hurts you far more than an unsubscribe, because it feeds quality rating directly.
• Honour STOP instantly and permanently. A contact who opted out and receives another message is the most likely person in your database to report you.
• Weekly quality rating checks. Yellow is a free warning. Acting on it costs nothing; ignoring it costs the account.
• Segment by engagement. Suppress contacts who have not interacted in 90 days rather than trying to reactivate them on WhatsApp - low-engagement sends are where block rates concentrate.
• Ramp volume gradually. Increase over days. Never step from hundreds to tens of thousands.
• Audit template categories monthly. Miscategorisation is a policy violation as well as a billing problem.
• Do not depend on a single channel. If WhatsApp is your only route to customers, a restriction is an outage of your entire communications capability.

That last point is the strategic one. A restriction is survivable when it is one channel among several and existential when it is the only one - and the difference is a decision made long before anything goes wrong.

Two adjacent problems block accounts before they ever send a message, and they generate a lot of the same panic as a restriction.

Display name rejected

Your WhatsApp display name must relate clearly to your actual business. Meta rejects names that are generic ("Customer Support", "Sales Team"), that include a phone number or URL, that use a trademark you do not own, or that describe a product category rather than a business ("Best Pizza Delivery").

The rule people miss: the display name must match the business name on your website, your legal registration, or your verified Facebook Page. A trading name that appears nowhere official is likely to be rejected even when it is genuinely what customers call you. If your legal entity name differs from your brand, get the brand name onto your website prominently before submitting.

Display name changes are also rate-limited. Once approved, you can only change it a limited number of times in a rolling period, so treat the first submission as significant rather than a draft.

Business verification

Meta Business Verification is separate from WhatsApp approval and gates your messaging tier. Unverified accounts are capped at 250 unique customers per day regardless of quality, which is fine for testing and inadequate for production.

Verification requires documents proving legal existence and a verifiable connection between your business and the phone number or domain: certificate of incorporation, a business licence, a utility bill or bank statement showing the business name and address, or a phone bill. The most common rejection cause is a mismatch - the address on the document differs from the address in Business Manager, or the legal entity name is entered as the trading name. Enter the details exactly as they appear on the document, including punctuation and suffixes like Ltd or LLC.

The number itself

A phone number registered on the WhatsApp Business Platform must not be in active use on the consumer WhatsApp app or the WhatsApp Business app. It also cannot be a number already registered to another WhatsApp Business Account. If registration fails on a number that seems fine, delete the existing WhatsApp account on that number first and wait for propagation before retrying - and be aware that doing so permanently deletes that account's chat history.

An appeal takes 3 to 14 days. Customers do not pause for that, and how you handle the gap determines how much of the restriction actually costs you.

Tell people where to go, on the channels you still control

Put a visible notice on your website, in your email signature and on your social profiles pointing to an alternative contact route. Most of the damage from a restriction is not the outage itself - it is customers messaging into silence and concluding you have gone out of business.

Do not spin up a second number

The instinct is to register a new number and carry on. Resist it. Meta links business assets, and a new number sending the same content to the same contacts immediately after a restriction is a recognisable evasion pattern that can escalate a recoverable restriction into a permanent ban across your whole Business Manager - taking your ads and pages with it.

The exception is a genuinely separate business unit with its own contacts and its own consent, established before any of this happened.

Export what you can

If you still have API access in a partially restricted state, export conversation history and contact records now. Access can be reduced further while an appeal is pending, and reconstructing that data afterwards is far harder than exporting it today.

Use the downtime to build the evidence

Whatever caused the restriction, your appeal is stronger with proof that it is fixed. Take screenshots of the new opt-in checkbox, document the contacts you removed and the count, record the template categories you corrected. Attach them. An appeal supported by evidence of remediation is materially more likely to succeed than an assertion that you will do better.

Stand up the alternative channel properly

A restriction is the clearest possible argument for not being single-channel. Standing up a website widget or a Telegram bot takes an afternoon and gives you somewhere to route customers immediately - not just during this outage, but as permanent insurance against the next one.

Everything above is recoverable. What is not recoverable is a business whose entire customer communication runs through one number that Meta can switch off with no notice, no warning and a 3-to-14-day appeal queue.

The practical mitigation is not to leave WhatsApp - it remains the highest-engagement channel in most markets. It is to make sure the same conversations can run somewhere else on short notice. Conferbot builds one flow and deploys it to WhatsApp, Telegram, Instagram, Messenger, Slack and a website widget, with a shared knowledge base and a shared agent inbox. If one channel goes down, the flow keeps running on the others and the conversation history stays in one place.

Start free with Conferbot - 600 conversations a month on the free plan, no credit card required. Building the second channel before you need it takes an afternoon; building it during a restriction takes a week you do not have.

If you are restricted right now, stop reading and file the appeal. Speed matters more than precision, and you can refine the diagnosis while the review is in the queue.