WhatsApp quality rating: the warning you get before the ban

Almost nobody gets restricted without warning. Meta publishes a quality rating for every number, it moves days before an account is limited, and most teams only look at it after something has already gone wrong. Read as a leading indicator it is the cheapest protection you have.

What the rating actually measures

Not delivery. The rating is built from how recipients react — blocks, reports, and “not useful” feedback over a rolling window. That is why a campaign can show a clean delivery report and still take the number amber: the messages arrived, and people did not want them.

It sits on the number, not the account, and it drives your messaging limit. Three states, in WhatsApp Manager:

• Green — High. Normal. Your limit can tier up.
• Amber — Medium. Recipients are reacting badly. Nothing has been taken away yet. This is the moment that matters.
• Red — Low. A reduced messaging limit usually follows, and a restriction after that if the sending does not change.

Reading it as a signal, not a score

The useful question is never “what is the rating” but “what changed just before it moved”. In practice it is almost always one of four things, and you will usually recognise yours immediately:

1. A new list. Numbers you did not collect yourself — imported, purchased, scraped from orders years old. People who did not ask report faster than anything else on this list.
2. A category change. Content that used to go out as utility is now being sent as marketing, so it lands under a different bar and a different tolerance.
3. A volume step. The number went from a few thousand to tens of thousands in a day. The content may be fine; the shape of the send is not.
4. A template rewrite. New copy, more promotional, more aggressive call to action — the same audience reacting differently.

Look at what shipped in the 48 hours before the drop. That is your cause, and it is nearly always the whole answer.

Getting a Low rating back

The recovery is unglamorous and it works: stop, narrow, wait.

• Stop the campaign that caused it. Not pause tomorrow — stop now. Every further send on a Low number is evidence against you.
• Narrow to traffic people expect. Order updates, delivery alerts, OTPs, to recipients who have engaged recently. Utility and authentication traffic is what a recovering number should be carrying.
• Hold it for about a week. Most Low ratings return to Medium within seven days of clean sending. The window is rolling, so the bad signal ages out — but only if nothing new replaces it.

The one move that reliably makes it worse is sending more marketing to prove the number is healthy. It is the equivalent of testing a fuse by loading the circuit.

Why one number should never carry everything

A rating sits on a number. If your entire programme runs through one WABA, a single bad campaign takes your order updates and your OTPs down with your promotions — and the recovery week costs you all three.

Spreading load across a pool of senders changes the blast radius. So does keeping a DLT-registered SMS route behind your authentication so a login does not depend on the health of a marketing number.

What QuickAuth does with the rating

We treat it as a control input rather than a dashboard number.

• A canary batch before the list — 1% on campaigns over 1,000, bounded 50 to 1,000 recipients, and a flat 20-message probe below that — so a template that is going to draw reports does it at probe scale.
• Health re-checked between waves. WABA and template quality are read again after each batch, and the campaign halts if the template goes RED or the whole pool does. The rating stops the send; you do not have to be watching.
• Load spread across pooled senders, so no one number carries a campaign alone.
• Opt-outs enforced at send time and never billed — removing the reports that move the rating fastest.

None of that makes a number immune; Meta decides and does not publish the criteria. It means the rating is being acted on continuously rather than noticed after the fact. If prevention is what you need, the fuller version is in how to avoid a WABA ban in India. If the account is already down, start at what actually works to get it back.

Questions