Why WhatsApp Numbers Get Blocked — And What Actually Prevents It

The panic is always the same. A campaign goes out, the quality rating drops to medium overnight, and someone asks whether we sent too many messages.

Almost never. Volume is not what gets a number restricted. Complaints are. Meta watches how recipients react — blocks and "report spam" taps — and a number that people keep reporting will lose quality rating and then messaging capacity, no matter how modest the send was. A thousand messages to people who asked for them is safer than a hundred to people who did not.

How the rating actually works

Meta assigns your number a quality rating — commonly shown as green, yellow or red — based on recent recipient feedback. Separately, your number sits in a messaging tier that caps how many people you can start conversations with in a rolling day. New numbers start low and Meta raises the tier in steps as you keep sending without being reported.

Two things people get wrong here:

• Replies are not capped. The tier limits conversations you begin. Answering someone who messaged you first does not count against it.
• Yellow is a warning, not a punishment. It is the window in which you can still fix things. If you only find out at red, you found out too late.

The four controls that matter

1. Consent you can actually point at

"They gave us their number" is not consent to market to them. Track how each contact opted in — a checkbox at import, an opt-in message, or the agent simply asking in conversation — and gate every send on it. The value of recording the route is that when a campaign goes wrong you can tell which audience caused it.

2. Honouring opt-outs, including Meta's own signal

Meta exposes a preference signal when someone opts out of your marketing. Ignoring it is one of the fastest ways to get reported, because the person has already told Meta they do not want this. We read that signal and drop the number from the next send automatically.

Related, and easy to get wrong: in a drip sequence, consent should be re-checked at every send, not just when someone joined it. Somebody who opts out on day two should not receive day three.

3. Stopping when Meta says stop

If Meta restricts an account, continuing to push sends into that restriction makes everything worse. Sending should halt on its own and resume when the restriction expires. This sounds obvious and is uncommon — plenty of platforms keep sending into a restriction and surface the failures as ordinary errors.

4. Knowing which message failed, and why

"1,200 sent, 63 failed" tells you nothing you can act on. A reason per recipient tells you whether you have a number-quality problem, a template problem or an audience problem. They have completely different fixes.

What to do when the rating drops

1. Stop the sequence. Not tomorrow. The rating reflects recent behaviour, so the cheapest fix is to stop adding to it.
2. Find the audience, not the message. Look at which segment the reports came from. It is usually one imported list.
3. Cut the audience to people who replied recently. Re-engagement to a cold list is the single most reliable way to get reported.
4. Give it time. The rating recovers on recent behaviour. There is no appeal that beats a fortnight of people not reporting you.

The uncomfortable part

Most number restrictions are earned. If a campaign gets reported, the message was usually going to people who did not expect it, or it was the fourth one that week. Deliverability tooling helps you notice sooner and stop faster — it cannot make an unwanted message wanted.

The boring version works: message people who agreed to hear from you, send them something worth reading, and stop when they say stop. Everything above is machinery for making that easy to do at scale.

How we handle it is on the WhatsApp Business API page.