WhatsApp Business account restricted: what to do

What does it mean when a WhatsApp Business account is restricted?

Meta's Business Help Centre puts it in one sentence: "A restricted WhatsApp Business account cannot send new messages to customers or respond to incoming customer messages" (Meta Business Help Centre — troubleshoot a restricted WhatsApp Business account).

Two details matter while you are panicking. The restriction sits on the WhatsApp Business account — the account behind your number — not on your handset, your ad account or your personal WhatsApp. And nothing is being deleted while you work out what happened: Meta states that "your account data, message history and business profile remain intact", and that "customers may still send you messages, but you will not be able to reply until the restriction has been lifted".

It also applies whichever way you reached WhatsApp: Meta's article covers the account you use "through the WhatsApp Business platform or the WhatsApp Business app". If you are unsure which of those you are on, the difference between the WhatsApp Business app and the API settles it, and the WhatsApp Business API explained end to end covers how the platform is governed.

Checked against Meta's Business Help Centre, WhatsApp's Help Centre and Meta's developer documentation on 22 August 2026.

• What does it mean when a WhatsApp Business account is restricted?
• Is a restriction the same as a ban?
• How do you tell which restriction you actually have?
• Why do WhatsApp Business accounts get restricted?
• What are the restriction levels, and how long does each last?
• What should you do in the first hour?
• How do you request a review, and how long does it take?
• Can anyone get a WhatsApp restriction lifted for you?
• How do you avoid being restricted again?

Is a restriction the same as a ban?

No, and three genuinely different things get called by the same word. Working out which you have is the first useful thing you can do, because the route out differs for each.

An in-app restriction on your WhatsApp account. If you saw "Your account is restricted right now" or "Your account may be restricted soon" inside the app, that is WhatsApp's consumer-side enforcement, and the guidance is to do nothing: "you don't need to take any action to remove the account restriction. The restriction automatically ends once the allocated time passes and you'll receive a notification in WhatsApp when it ends" (WhatsApp Help Centre — about restricted accounts).

Meanwhile you can keep talking to contacts and groups you have exchanged chats or calls with before, but you cannot start chats or calls with new contacts, create new groups, add members, or use linked devices. To see the time remaining, WhatsApp says to tap New Chat and pick a contact you have never messaged.

A ban on the WhatsApp Business app. Here there is a button, with one very direct sentence attached. WhatsApp says to "tap Request review in the app to submit the request", and that "if you don't see an option to request a review, it means the ban is final and can't be appealed" (WhatsApp Help Centre — account bans on the WhatsApp Business app).

The 24-hour figure people quote comes from the in-app ban message itself — "You can request a review of this number. Most reviews are completed within 24 hours" — not from a published service level.

The same page closes the side doors: "Contacting WhatsApp support by email or chat can't reverse an account ban or change the outcome of the review", and "third party services can't ban your WhatsApp Business account or remove your account ban."

A restriction on a WhatsApp Business account on the Platform. This is the one that stops an API integration dead, and it is appealed in Meta Business Suite rather than in any app. The rest of this article is about that one.

How do you tell which restriction you actually have?

Read the error code your platform recorded against the failed sends. Every description below is quoted from Meta's Cloud API error code reference, checked 22 August 2026.

One diagnostic almost nobody mentions: Meta's Health Status API reports AVAILABLE, LIMITED or BLOCKED for each layer of a send — app, business portfolio, WhatsApp Business account, phone number and, where relevant, the template — and where a layer is BLOCKED it returns an errors property carrying the reason for that status and a possible solution (Meta — messaging and calling health status). It answers what an error code cannot: which layer is restricted.

Why do WhatsApp Business accounts get restricted?

Meta names three rulebooks — the WhatsApp Business Terms of Service, the Business Messaging Policy and the Commerce Policy — and gives as common examples "sending messages to people who have not opted in to receive them, sending prohibited content, or selling items that violate the Commerce Policy". Four things produce nearly all of them.

Sending without a valid opt-in. The policy is unusually blunt: "You may only contact people on WhatsApp if: (a) they have given you their mobile phone number; and (b) you have received opt-in permission from the recipient confirming that they wish to receive subsequent messages or calls from you" (WhatsApp Business Messaging Policy). A bought or scraped list fails both halves at once.

Blocks and reports from the people you messaged. Your quality rating is "a rating based on the recent messages that your customers have received over the past seven days", and is "determined by feedback from your customers, such as the reason why they blocked your number and other reporting issues" (Meta — about your quality rating).

Someone blocking a business picks from a fixed list — No longer needed, Didn't sign up, Spam, Offensive messages, No reason — and two of those are exactly what a cold list produces. Where the rating is Yellow or Red, Meta says hovering over it in WhatsApp Manager shows the block reasons if they are available.

Template misclassification, and high-risk categories. Meta's enforcement documentation names "sending spam, template misclassifications, or high-risk policy categories such as adult content, sale of alcohol and tobacco, drugs, gambling and unsafe supplements". Dressing a promotion up as a utility message to pay the cheaper rate is the misclassification that catches most businesses.

Unofficial senders. Tools that automate WhatsApp Web or the consumer app are the most common cause on the app side, and the least recoverable, because the behaviour is itself the violation. WhatsApp's own wording on a restricted account is that activity "showing signs of engaging in spam, automated, or bulk messaging … violates our Terms of Service".

A fifth trigger breaks no specific rule at all, and Meta states it separately: "We might also limit or offboard your business from WhatsApp if your account receives excessive negative feedback from users."

What are the restriction levels, and how long does each last?

Meta's developer documentation sets out an escalating ladder and quotes durations for most rungs. It is the closest thing to a published timeline that exists.

Source: Meta — WhatsApp Business Platform policy and spam enforcement, read 22 August 2026. Meta publishes no revision date on that page, so treat the durations as current-as-read rather than pinned. Note also its own disclaimer: "This document does not include information on messaging limits based on quality rating." Policy enforcement and quality throttling are separate systems with separate remedies, which is why advice about one is useless against the other.

Pages telling you a restriction "lasts 24 to 48 hours" have taken the appeal review time and attached it to the wrong thing.

There is one place Meta states your restriction and when it ends, and it is not a screen. The account_update webhook fires an ACCOUNT_RESTRICTION event whose restriction_info carries a restriction_type, an expiration timestamp, and a remediation string where remediation steps exist (Meta — account_update webhook reference).

Those types are far more specific than anything the interface shows, which is why "my account is restricted" is usually too coarse a description to act on. Meta's reference lists nine.

Values read from Meta's webhook reference on 22 August 2026. The right-hand column is a plain reading of each identifier — Meta names the values but does not gloss them. If you send through a platform, that payload is the only place the type and the expiry appear together.

What should you do in the first hour?

Stop sending. Every further attempt is another data point in the file Meta is reading, and if a campaign triggered this, the campaign is probably still running.

Then read the violation rather than guessing at it. Meta surfaces the detail in Business Support Home, the Business Manager Notifications Center, a banner in WhatsApp Manager, and an email "to all admins set in Business Manager" — if nobody received that email, your admin contact details are out of date.

Only then decide whether you are appealing or fixing. Appealing while the behaviour that caused the restriction is still running is the one approach that reliably fails.

How do you request a review, and how long does it take?

Meta documents two routes, and which you use depends on what has been restricted.

For a restricted WhatsApp Business account: go to Business Support Home, scroll down and click the restricted account, click Request review, tick the box confirming you are a real person, enter a mobile number to receive a confirmation code by SMS or WhatsApp, then upload a photo of a valid, unexpired government-issued ID — Meta names a driving licence, passport or national identity card, photographed clearly with all four corners visible.

For an individual policy violation on an account that still works, there is a different path: in Business Support Home, open the business portfolio, find the WhatsApp Business account, and in the Available for review tab of Activity issues click the policy issue, then Request review, pick an appeal reason and submit. The request moves to the In review tab.

Only the account-level route carries the ID upload, which is the mechanical reason no agency or platform can file it for you.

There is a deadline on this, and almost nobody prints it. Meta's Business Help Centre states: "All policy violations can be appealed within 90 days of being received" (Meta — view policy violation details for your WhatsApp Business account). Sit on a violation longer than that and the appeal route closes on its own.

The timings differ slightly, and Meta gives two figures. For a restricted account it "aims to provide a decision within 48 hours, but some reviews may take longer", and the account stays restricted throughout. For a policy-violation appeal the Business Help Centre says reviews "typically take 24 hours" while the developer documentation says the decision "typically takes 24 to 48 hours", after which the violation will "either remain Unchanged or be set as Reversed".

Three outcomes are possible: lifted; upheld, in which case you correct the issue and may request another review; or permanently restricted, where "you will not be able to request further reviews for this account". A reversal restores rather than resets — "if issues are reversed following the appeal or acknowledgment, the account returns to its previous status", meaning the same messaging limit and quality rating as before.

One line ends most people's hope of a shortcut: "Not all spam violations might be appealed. Businesses might have to wait until the restriction period ends to begin messaging again."

Can anyone get a WhatsApp restriction lifted for you?

No, and this is the part worth being blunt about.

There is no back channel, no partner-tier override and no paid escalation that reverses a Meta enforcement decision. WhatsApp's Help Centre states that "WhatsApp Support does not provide support related to account bans and restrictions on the WhatsApp Business Platform" (WhatsApp Help Centre — ban appeals on the WhatsApp Business Platform), and on the app side that "only WhatsApp can ban or unban a WhatsApp Business account".

The account-level review also needs a government ID belonging to the person who runs the business. A service selling a guaranteed unban is selling something Meta does not offer, and its method is filing the same appeal you could have filed yourself.

What a platform can legitimately do is narrower and duller: tell you which error code you are hitting, whether the problem is the account, the number or one template, and what the account_update webhook said.

On the shared inbox and campaign tools, a quality downgrade, a disconnection or an expiring token emails the workspace owners and admins once per condition, so the first person to notice is not a customer whose message went unanswered. That is early warning, not a cure, and nobody should sell it as one.

How do you avoid being restricted again?

Nothing here is clever, which is rather the point.

Collect opt-in the way the policy describes, and record when and where each was given. Honour opt-outs immediately: the policy requires you to respect all requests "(either on or off WhatsApp)" to block, discontinue or opt out, "including removing that person from your contacts list". A STOP reply is not the only form one takes.

Categorise templates honestly. An order update is a utility message; a promotion bolted onto one is not, and that is the misclassification Meta names by name.

Watch the quality rating in WhatsApp Manager and treat yellow as the warning it is. Stop broadcasting to segments that never reply, because that is where blocks concentrate. And send inside your messaging limit, which Meta calculates per business portfolio across a moving 24-hour period rather than per number — what actually caps how much you can send covers that in full.

One correction is overdue, because it invalidates a lot of published advice. Meta's Business Help Centre now carries this note: "The phone number statuses of Flagged and Restricted have been discontinued as of 7 October 2025." Pages still telling you to look for a Flagged status in WhatsApp Manager, or to wait out a 24-hour Restricted status on a phone number, are describing a screen that no longer exists.

What remains is the quality rating, the error code, the account_update payload and the violation record in Business Support Home. Between them they will tell you what happened. None of them will tell you it can be undone quickly, and that is the honest shape of this problem.