WhatsApp Business Account Restricted: How Meta's Enforcement Ladder Works and What the Review Request Really Decides
Messaging has stopped. Templates will not send. New numbers cannot be added. Before you touch anything, you need to know which layer the restriction landed on — because the fix for a paused template is nothing like the fix for a locked WhatsApp Business Account.
Most businesses discover a restriction the same way: an automation that ran fine yesterday starts failing, and a banner appears in WhatsApp Manager. The instinct is to change the message copy and try again. That almost never works, because Meta enforces on four separate layers, and only one of them is the message.
This guide explains the layers, what Meta actually publishes about each, and where the review request fits. It is written for businesses running the WhatsApp Business Platform (Cloud API) directly or through a partner.
The four enforcement layers
1. Message template
Each template carries its own quality rating — GREEN, YELLOW, RED or UNKNOWN. A template that reaches low quality gets paused automatically, and repeated pauses end in the template being disabled.
2. Business phone number
A number has a status reflecting its quality rating and current messaging capacity. It must be in a connected state to send or receive through the API at all.
3. WhatsApp Business Account (WABA)
This is where policy enforcement lands. Meta blocks message sending and the addition of new phone numbers at the account level, for an escalating duration.
4. Business portfolio
The container that holds your WABAs. Messaging limits are calculated here and shared across every business phone number in the portfolio — not per number.
How the account-level ladder escalates
Meta enforces against WhatsApp Business Accounts that repeatedly violate the WhatsApp Business Messaging Policy, the WhatsApp Commerce Policy, or the WhatsApp Business Terms of Service. The published progression is deliberately graduated:
- Warning. A notice identifying the policy that was violated. No sending impact yet — and this is the cheapest point at which to fix the underlying cause.
- Short block. A 1 or 3 day block on sending marketing, utility and authentication template messages, and on adding further phone numbers to the account.
- Extended block. A 5, 7 or 30 day block on sending any messages and on adding phone numbers.
- Account lock. An indefinite block on sending any messages. Meta states this can only be removed through an appeal.
- Permanent removal. If a business does not change course after multiple warnings and blocks, the account is permanently disabled from the WhatsApp Business Platform.
Severe cases — evidence of serious harm such as scams, illegal drug sales, terrorism or child exploitation — skip the ladder entirely and result in immediate offboarding. Meta also states it may limit or offboard a business whose account receives excessive negative feedback from users.
Where the restriction is visible
Meta surfaces the same event through several channels, which is why one team member may see it days before another:
- Business Support Home inside Meta Business Suite / Business Manager, under the account overview — the detailed record
- The Business Manager Notifications Center
- A banner inside WhatsApp Manager
- An email to every Business Manager admin on the portfolio
- The
account_updatewebhook, which carries the policy violation and, where applicable, the restriction type and duration
If your platform never wired up the account update webhook, the first signal your engineering team gets is a wave of failed sends with no explanation. That gap alone costs teams days.
The review request — what it is and what it decides
- Locate the violation recordBusiness Support Home holds the specific violation attached to your WhatsApp Business Account. This is the item under review, not your account in general.
- Choose the violation and request reviewThe flow offers a review request against that individual violation, with a field for supporting details.
- Submit supporting detailThis is the entire case. The reviewer is deciding one thing: whether the violation as recorded was correct. Generic apologies and promises to do better do not address that question.
- The item moves to In ReviewMeta states the appeal decision is sent through Business Manager and typically takes 24 to 48 hours.
- Outcome is Unchanged or ReversedIf issues are reversed following the appeal, the account returns to its previous status. If unchanged, the restriction runs its course.
Number-level and template-level problems are a different job
| Layer | What actually happens | What resolves it |
|---|---|---|
| Template | Low quality triggers automatic pausing — three hours on the first instance, six on the second, disabled on the third. Paused templates are rejected by the API and are not billed. | Fixing the content and targeting that produced negative feedback. On unpause, the template returns to active and its quality rating resets based on the most recent customer feedback. |
| Phone number | Status reflects quality rating and current messaging capacity. Sustained low-quality template sending can eventually affect the number itself. | Quality recovery over time. Meta notes template pausing does not initially impact the number — the damage is cumulative. |
| WABA | Policy enforcement. Sending blocked account-wide for a fixed duration, or locked indefinitely. | A review request against the specific violation — or waiting out the block where no appeal is available. |
| Portfolio | Messaging limits are calculated at portfolio level and shared by all numbers within it. Limits scale one level at a time. | Business verification and sustained high-quality volume — a growth problem, not an enforcement one. |
Note that the old per-number tier language is out of date. Messaging limits are portfolio-level now, and the messaging_limit_tier field has been deprecated in favour of the account-level messaging limit field. Content still teaching "Tier 1 / Tier 2 / Tier 3 per number" is describing a model that no longer exists.
Why businesses stall here
- Treating a template pause as an account restriction — rewriting copy while an account-level block runs untouched
- Treating an account restriction as a capacity issue — waiting for a limit reset that is never coming
- Submitting a review request that argues intent rather than addressing the specific recorded violation
- No
account_updatewebhook handling, so the restriction is discovered through failed sends instead of the notification - Admins not monitoring Business Support Home, so the appeal window opens and closes unattended
- Rebuilding on a fresh number or a new WABA, which does not resolve the recorded violation and can compound the problem
- Following BSP help articles written for one partner's dashboard, which do not match the underlying Meta flow
What a correct response looks like
If your WhatsApp Business Account is restricted right now, the first hour matters more than the next week. Diagnosing the layer correctly, then preparing a review request that speaks to the recorded violation, is the work — and it is the part most teams get wrong under pressure.
This is exactly the kind of case I handle as part of WhatsApp Business Platform account support. Related reading: why WhatsApp message templates get rejected and how Meta app-level enforcement and appeals work.
This article is policy-aligned guidance based on Meta's published WhatsApp Business Platform documentation as of July 2026. Platform policies and enforcement change; always confirm against Meta's current documentation for your account. Review outcomes are determined solely by Meta and no specific outcome or timeline can be guaranteed.