Summary
Every WhatsApp Business number carries a quality rating that most teams never look at until something breaks. It's a green, yellow or red status Meta assigns based on how recipients have reacted to your messages recently, and it directly controls how many people you're allowed to reach in a day. This post explains what the rating measures, how it sets your messaging limit, what actually moves it, where to check it, and what to do if it drops.
TL;DR
- WhatsApp scores every business number green, yellow or red based on recent blocks, spam reports and negative recipient feedback, and that score is not the same thing as WhatsApp Business verification.
- The rating sets your messaging tier directly, starting around 250 business-initiated conversations in 24 hours and climbing to 1,000, 10,000, 100,000 or unlimited as trust builds.
- A dropping rating and a blocked number are different problems with different fixes. One throttles you, the other stops you, and confusing the two wastes time you don't have.
- You can check your current status in WhatsApp Manager before it becomes visible in your send volume, and recovering a dropped rating is a matter of changing behaviour, not filing an appeal.
Somewhere in the account blocks piece we wrote for this site, there's a line about "a falling quality score from spam reports or blocks" as one of the things that gets a number restricted. That line does a lot of quiet work and never actually explains itself. The quality rating is the mechanism underneath almost everything else in this cluster: it's what bulk sending damages when it's done carelessly, what mod apps wreck instantly, and what determines whether a growing team can actually send the volume its business needs. It deserves its own explanation instead of a passing mention.
What the quality rating actually is
WhatsApp assigns every business phone number a quality rating of high (green), medium (yellow) or low (red). Meta calculates it from a rolling window of recent recipient behaviour on that specific number: how many people blocked you, how many reported a message as spam, and how many simply stopped responding or reacted negatively. It updates continuously, not once a month or once a quarter, so a bad week of sending can move the number within days.
It's easy to confuse this with WhatsApp Business verification, the blue or green checkmark a business can apply for once it's on the official Business Platform rather than the free App. Verification is a one-time trust badge about who you are. The quality rating is an ongoing, moving score about how you actually behave, and a verified business can still carry a red rating if its sending habits are bad enough.
How the rating decides how much you can send
This is the part most teams don't realise until they hit it. WhatsApp sets a messaging limit, the number of business-initiated conversations you can start in a rolling 24 hours, and that limit is tied to your quality rating rather than being a fixed number every account gets. New and lower-tier numbers typically start around 250 conversations a day. Sustain a healthy rating and Meta scales that up through 1,000, then 10,000, then 100,000, and eventually unlimited. Let the rating fall and the tier drops with it, sometimes straight back to the bottom.
| Quality rating | 24-hour messaging limit |
|---|---|
| New / lower tier | ~250 business-initiated conversations a day |
| Tier 2 | 1,000 conversations a day |
| Tier 3 | 10,000 conversations a day |
| Tier 4 | 100,000 conversations a day |
| Top tier | Unlimited |
What that means in practice: a number can be technically working, not blocked, not banned, and still be unable to send a campaign to the audience it used to reach, simply because the rating slipped and the tier came down with it. Teams often mistake this for a delivery bug when it's really a messaging limit doing exactly what it's designed to do.
What actually moves the rating
Meta doesn't publish an exact formula, but the patterns are consistent enough to be genuinely predictable rather than random. Sending to people who never opted in is the single biggest driver, the exact failure mode covered in our piece on bulk and broadcast messaging compliance. Blasting an entire contact list instead of a relevant segment produces the same effect at a slower burn: fewer people report you outright, but more quietly block you, and blocks count against the rating just as heavily as reports do.
Mod apps deserve a separate mention, because they don't move the rating so much as bypass the whole system. WhatsApp detects an unofficial build and can shut the number down directly, which is a different and faster failure than a rating slide. We've covered why GB WhatsApp and similar mods are a bad bet on their own, and it's worth reading if a rating drop is what sent you looking for this article in the first place, since the two problems get confused constantly.
Template quality matters too, in a smaller way than most teams assume. A poorly written template that reads as spammy can drag on the rating over time, but our view is that this gets blamed far more often than it deserves. A number sending relevant messages to people who opted in rarely drops its rating over wording alone. It drops because the list behind the send was wrong.
Checking your own rating
The rating is visible in WhatsApp Manager (formerly Facebook Business Manager) under the phone number's details, shown as the same green, yellow or red status described above, alongside your current messaging limit tier. If you're running WhatsApp through a Business Solution Provider rather than raw API access, that same information usually surfaces inside the provider's own dashboard, which is where most teams actually check it day to day. Saysimple's reporting shows delivery and engagement patterns at the number level for exactly this reason: catching a slide before it shows up as a support ticket about messages not sending.
If your rating drops
Recovering a dropped rating is behavioural, not procedural. There's no appeal form to fill out and no support ticket that fixes it directly, unlike a full account block, where requesting a review is the actual mechanism. Instead:
- Pause the campaign or list that likely triggered the drop rather than sending through it and hoping the numbers recover on their own.
- Check whether the audience was properly opted in and segmented, since this is the root cause behind most drops we see.
- Send only to genuinely engaged recipients for a stretch, and let positive interactions rebuild the rating before scaling volume back up.
- Rewrite the template if it reads as generic or promotional rather than specific and expected.
Ratings do recover. They're a rolling measure, so clean sending behaviour over the following window pulls the score back up the same way bad sending pulled it down.
Closing thoughts
Most teams meet the quality rating for the first time when it's already a problem, a campaign that underperformed for no obvious reason, or a send that suddenly caps out lower than expected. The teams that don't hit that wall are usually the ones whose opt-in flow, template approval and list segmentation were built properly from the start, which is a large part of what a real WhatsApp broadcasting setup and shared inbox are actually built to enforce, rather than leaving it to whoever happens to hit send that day.
Saysimple runs on the official WhatsApp Business Platform as a Meta-approved provider, which means opt-in handling, template compliance and delivery reporting are part of the setup rather than something a team has to remember on their own. Book a demo to see how that setup keeps a growing team's number in the tier it actually needs.
Sources
- WhatsApp's Business Messaging Policy, which governs the business-initiated conversation rules that quality ratings and messaging limits are built around.