What is an account restriction?
An account restriction is a temporary penalty Meta applies to a WhatsApp Business Account (WABA) when the business breaks WhatsApp's rules — sending spam, misclassifying templates or messaging about high-risk goods. It is the middle rung of Meta's enforcement ladder: a warning comes first, a restriction follows repeated or more serious problems, and an indefinite account lock or a WhatsApp Account Ban sits above it. Restrictions get longer each time a violation repeats.
Meta uses two sizes. A 1- or 3-day restriction blocks sending marketing, utility and authentication templates and adding phone numbers, so the business cannot start conversations but can still answer customers who write in during the 24-Hour Customer Service Window. A 5-, 7- or 30-day restriction blocks sending any messages and adding numbers, so even replies stop. When the period ends the block lifts automatically; an account lock, by contrast, lasts until an appeal succeeds.
Systems learn about it through the Account Update Webhook: an account_update notification with event: ACCOUNT_RESTRICTION and a restriction_info array, each item holding a restriction_type, an expiration Unix timestamp and sometimes remediation advice. Common types are RESTRICTED_BIZ_INITIATED_MESSAGING, RESTRICTED_CUSTOMER_INITIATED_MESSAGING and RESTRICTED_ADD_PHONE_NUMBER_ACTION; others cover calling and utility templates. A restriction is not the same as a low Quality Rating or a messaging limit, which cap reach without any finding that a policy was broken.
Key takeaways
- An account restriction is a temporary enforcement action Meta places on a WhatsApp Business Account after policy violations.
- A 1- or 3-day restriction blocks marketing, utility and authentication templates and adding phone numbers; replies to customers still work.
- Repeat violations bring 5-, 7- or 30-day restrictions that block sending any messages at all.
- Meta announces each restriction in the account_update webhook as ACCOUNT_RESTRICTION, with a restriction_type and an expiration time.
- Appeals go through Business Support Home and are typically decided in 24 to 48 hours; not every spam violation can be appealed.
An account restriction: key facts and limits
- Short restriction
- 1 or 3 days: no templates, no new numbers
- Long restriction
- 5, 7 or 30 days: no messages at all
- Account lock
- Indefinite; removed only by appeal
- Webhook
- account_update · event ACCOUNT_RESTRICTION
- Expiry field
- restriction_info[].expiration (Unix time)
- Appeal decision
- Typically 24–48 hours (Unchanged or Reversed)
How does an account restriction work?
- Step 1
A violation is recorded
Meta's review flags a Policy Violation such as spam or a misclassified template. The first one usually brings a warning describing the policy that was broken; you see it in Business Support Home, WhatsApp Manager and admin emails.
- Step 2
The restriction is applied
Further violations trigger a restriction. Meta sends
account_updatewithACCOUNT_RESTRICTION, listing eachrestriction_typeand itsexpiration, and sends that the restriction covers fail with an integrity error. - Step 3
Pause exactly what is blocked
Map each type to your queues: stop template campaigns for
RESTRICTED_BIZ_INITIATED_MESSAGING, stop everything forRESTRICTED_CUSTOMER_INITIATED_MESSAGING, and freeze number onboarding forRESTRICTED_ADD_PHONE_NUMBER_ACTION. Move OTPs to a fallback channel. - Step 4
Fix the cause, then appeal if it was wrong
Remove the list, template or content behind the violation. If the finding is mistaken, select it in Business Support Home and click Request Review; the outcome is Unchanged or Reversed, typically within 24 to 48 hours.
- Step 5
Resume deliberately
When the expiration passes, or a reversal returns the account to its previous status, restart sends gradually. Another violation brings a longer restriction, then an account lock or permanent disablement.
Example: Three quiet days for a Surat saree seller
A Surat saree seller uploads a purchased list of 8,000 numbers for a festive sale. Blocks and reports pile up, the account already has a warning, and Meta applies a 3-day restriction. The account_update webhook lists RESTRICTED_BIZ_INITIATED_MESSAGING and RESTRICTED_ADD_PHONE_NUMBER_ACTION, so the integration pauses every template queue: the sale, but also dispatch updates and login OTPs, which move to SMS for three days. Customers who message the shop still get answers from the support team. The seller deletes the bought list, keeps only customers with a recorded opt-in, and decides not to appeal, because the violation was real — and a longer restriction next time could block every message, replies included.
An account restriction in code
{"object": "whatsapp_business_account","entry": [{"id": "{WABA_ID}","time": 1760925600,"changes": [{"field": "account_update","value": {"event": "ACCOUNT_RESTRICTION","restriction_info": [{ "restriction_type": "RESTRICTED_BIZ_INITIATED_MESSAGING", "expiration": 1761184800 },{ "restriction_type": "RESTRICTED_ADD_PHONE_NUMBER_ACTION", "expiration": 1761184800 }]}}]}]}
One item per restriction. expiration is a Unix timestamp; entry.id is the restricted WABA.
Common mix-ups
Common mistakes with an account restriction
Assuming only marketing is blocked
A template block covers utility and authentication templates too. Keep an SMS or email fallback ready for OTPs and critical order updates so a restriction does not stop logins and deliveries.
Retrying failed sends
Every send during the restriction fails, and a retry loop only fills logs and queues. Read
restriction_typeandexpiration, pause the affected queues, and schedule the restart for the expiry time.Promising customers replies will always work
Only the 1- and 3-day restrictions leave customer-initiated chats open. Check for
RESTRICTED_CUSTOMER_INITIATED_MESSAGINGand tell support straight away when replies are blocked too.Waiting it out without fixing the cause
Restrictions escalate. If the list, template or content that caused the violation is still in use, the next restriction is longer and the one after can be a lock or a ban.
Why the difference matters
Why does an account restriction matter?
A restriction stops more than marketing. Login OTPs, order confirmations and payment reminders are templates too, so a three-day block can halt sign-ups and deliveries along with the offer that caused it. Knowing exactly which restriction type applies — and when it expires — tells the team whether support can keep replying, which sends to pause, which to move to another channel, and whether an appeal is worth filing before the next violation turns three days into seven or thirty.
Rules of thumb
Best practices for an account restriction
- Subscribe to
account_updateand routeACCOUNT_VIOLATIONwarnings to a named compliance owner — the warning is your cheapest chance to fix things. - Show restriction status and time left in your admin screens, next to each WABA.
- Keep a written record of what you changed after each violation; it is the evidence a Policy Appeal needs.
- Treat repeat restrictions as a business-model signal, not bad luck.