Why Your WhatsApp Business Account Is Blocked From Sending

Meta exposes a health_status field on three objects: the WhatsApp Business account, the business phone number and the message template. Requesting it returns a summary of every node involved in a send, so you can tell before you send whether the attempt will work. The call is a plain read of the form GET /<NODE_ID>?fields=health_status, which your provider makes on your behalf.

Each node carries one of three values on its can_send_message property. AVAILABLE means the node meets all messaging requirements. LIMITED means it meets them but something is capped — Meta attaches an additional_info note explaining what. BLOCKED means one or more requirements are not met, and Meta attaches an errors entry with a code, a description and a possible solution.

The overall status is deliberately pessimistic. If any single node is blocked, the aggregate is BLOCKED. If nothing is blocked but something is limited, it is LIMITED. Only when every node is clear does it read AVAILABLE (Meta, Messaging and Calling Health Status, retrieved 2026-10-07). That is why a merchant can see one red flag and a dozen green ones and still send nothing. For the surrounding platform rules — limits, the 24-hour window, template categories — we keep a dated reference on the WhatsApp Business Platform facts page.

The response contains an entities array, and that array is the whole diagnosis. Reading it in order saves you from guessing:

1. PHONE_NUMBER — the number you send from. Included when you query a number. It also carries a separate status for receiving calls over SIP.
2. MESSAGE_TEMPLATE — included when you query a template. A template that is still pending review cannot be sent.
3. WABA — the WhatsApp Business account itself. This is where a policy restriction usually lands.
4. BUSINESS — the business portfolio that owns the account. A portfolio-level problem affects every number under it.
5. APP — the application sending on your behalf. Always included.

The last three are always present; the first two appear depending on what you queried. Meta's own worked examples make the difference between the two non-green states concrete. A phone number whose display name has not been approved yet comes back LIMITED, with the additional_info line "Your display name has not been approved yet. Your message limit will increase after the display name is approved." An unapproved template comes back BLOCKED with error code 141002, the description "Message templates can only be sent out if they are approved" and the solution "Edit or appeal the message template review decision" (Meta, Messaging and Calling Health Status, retrieved 2026-10-07).

The practical rule: read which entity is blocked before you change anything. A template problem and an account-level restriction look identical from inside your shop — nothing sends — and the remedies have nothing in common.

This is the part that costs merchants a day. Your WhatsApp tool checks that it can reach Meta on your behalf — that the credentials are valid and the number is attached to your account. That check passes right up until Meta pulls your permission to send, because the credential is still perfectly valid. What changed is not the connection, it is the authorisation behind it.

So a connected-but-blocked account and a genuinely disconnected one are different failures with different fixes. If the integration itself has dropped, the remedy is to reconnect, which we walk through in WhatsApp Business account disconnected. If the connection is intact and the health status says BLOCKED, reconnecting changes nothing and costs you the time you need for the appeal. The setup itself is documented step by step in connecting your WhatsApp account, and it is worth comparing against what you actually see before concluding anything.

There is a third state that looks like both and is neither: an account still under review. Nothing is wrong, nothing has been taken away, and the only correct action is to wait — which we cover in WhatsApp account under review.

Meta enforces against accounts that repeatedly breach the WhatsApp Business Messaging Policy, the Commerce Policy or the Business Terms of Service. The first step is a warning naming the policy. Beyond that, restrictions escalate in duration (Meta, WhatsApp Business Platform policy and spam enforcement, retrieved 2026-10-07):

• A 1 or 3 day block on sending marketing, utility and authentication templates, and on adding phone numbers to the account.
• A 5, 7 or 30 day block on sending any messages at all, and on adding numbers.
• An account lock — an indefinite block on sending, removable only via an appeal.
• Permanent removal from the platform, after multiple warnings and limits have not changed behaviour.

Two shortcuts bypass the ladder. Evidence of a violation causing severe harm leads to immediate offboarding, and an account that collects excessive negative feedback from users may be limited or removed without the usual sequence. For a Shopify store the realistic triggers are mundane: messaging people who never opted in, and sending promotional content under a utility template.

One distinction is worth holding on to, because it misleads people constantly. Messaging limits driven by your quality rating are a different mechanism entirely — Meta says so explicitly in the enforcement guide. A low quality rating lowers how many people you may reach; a policy violation blocks you from sending at all. The limit ladder and its thresholds are documented on the facts page, and a quality rating flagged for seven days drops your limit by one level on its own.

Every violation and every active restriction is visible in Business Support Home, inside Meta Business Suite or Business Manager. Open Meta Business Suite, click All tools in the left menu, then Business Support Home, then Account Overview. The entry tells you which policy was breached, what is allowed and disallowed under it, whether a restriction is active, and what happens if it recurs.

If you believe you are compliant, request a review:

1. In Business Support Home, select the relevant WhatsApp Business account.
2. Pick the violation from the list and click Request Review.
3. Enter supporting detail in the Business Manager dialog and submit.
4. The request moves to the In Review tab. Meta's decision arrives via Business Manager, typically within 24 to 48 hours, and sets the violation either Unchanged or Reversed.

Reversal restores the account to its previous status. Not every spam violation can be appealed, though — in some cases the only option is to wait out the restriction period (Meta, policy and spam enforcement, retrieved 2026-10-07).

Meta notifies you through four channels at once: the Business Manager Notifications Center, a banner in WhatsApp Manager, an email to every admin listed in Business Manager, and the account_update webhook for anyone subscribed to it. The email is the one most stores miss, because the admin on file is often a founder's old address. Check it now rather than during an outage.

• Reconnecting before reading the error. Disconnecting and reconnecting a working integration does not clear a Meta-side block, and you lose hours you could have spent on the appeal.
• Blaming the provider. If the credentials still authenticate, the provider is doing its job. The blocked node named in the response tells you where the problem actually sits.
• Treating LIMITED as BLOCKED. An unapproved display name caps your volume; it does not stop you sending. Fixing the display name in your WhatsApp profile settings is the right response to that one.
• Re-sending the same campaign the moment a restriction expires. The content that triggered the first warning will trigger the second, and the second block is longer.
• Letting the Business Manager admin list go stale. If nobody reads the notification email, the first sign of a block is a silent campaign.
• Assuming a block and a ban are the same thing. A business account restriction, a personal account ban and an account under review are three different states with three different remedies.

Almost every avoidable block traces back to one of two habits. The first is loose opt-in. Meta requires an opt-in before you message anyone, and it has to name your business. Collecting consent at a point where the customer clearly expects messages from you — at checkout, in the chat widget, on a QR code at the counter — produces lists that do not generate complaints.

The second is template drift. A utility template has to be non-promotional and either specific to the user or essential to them. Slipping a discount code into an order-status template reclassifies it as marketing and, repeated often enough, reads as misuse. Keeping promotional and transactional messages in separate templates costs nothing and removes the whole category of risk. The message types a Shopify store actually needs are laid out on our templates page.

Beyond that, subscribe to the account_update webhook so a violation reaches your systems rather than an inbox nobody opens, and glance at the health status before a large send instead of after it. Both are cheap. A 30-day block in the week before Black Friday is not.