WhatsApp Broadcast Limits and Quality Rating, Explained

WhatsApp doesn't cap broadcasts with a single number — it runs two separate systems that interact. Every WhatsApp Business number sits in a messaging tier that caps how many new unique customers it can message first (business-initiated) within a rolling 24-hour window, commonly starting near 1,000 and expanding toward 10,000, 100,000, or unlimited. That tier only holds, or climbs, if the number's quality rating — a live read on blocks, reports, and read rates — stays healthy. A number can be cleared to reach 100,000 people today and still get throttled at 20,000 into a broadcast if the list was stale or unengaged. This guide explains exactly how both systems work, how they collide, and the actual playbook for scaling volume without getting caught out by either one.

Two separate limits, not one#

The single most common misunderstanding about WhatsApp broadcasting is treating "how many people can I message" as one number. It's actually two numbers, owned by two different systems, and a real-world broadcast is bound by whichever one is smaller at that moment.

The first is Meta's messaging tier — a WhatsApp Business Platform rule that caps how many new, unique customers a phone number can message first (business-initiated, not customer-initiated replies) inside a rolling 24-hour window. This lives entirely on Meta's side and is tied to the phone number itself.

The second is your SabNode plan's message quota — a monthly allowance tied to your subscription and billing, covering messages across every channel you use, not just WhatsApp. Starter is free forever with 500 messages a month; Growth is ₹2,499/mo (or ₹24,990/yr) with 50,000 messages a month across any channel; Scale is ₹9,990/mo (or ₹99,900/yr) with 500,000 messages a month and burst headroom; Enterprise is custom-priced for larger volumes. If you go over your plan's monthly allowance, overage is billed at ₹0.10 per extra message rather than hard-stopping your account.

These two ceilings do not know about each other, and they don't reset on the same clock — Meta's tier is a rolling 24-hour unique-customer count, while your SabNode plan quota is a monthly message count. A broadcast is throttled by whichever cap is hit first. A Growth-plan account with plenty of monthly messages left can still be capped mid-broadcast by a lower Meta tier on a newer number. Equally, a number sitting in Meta's highest tier gains nothing if the account has already burned through its plan quota for the month. Plan your send size against both, not just the one you remember to check.

How Meta's tiered messaging-limit system works#

Meta's tier system exists to protect WhatsApp users from spam while letting legitimate senders grow. Every WhatsApp Business Platform number starts in a lower tier and moves up automatically as it proves, over time, that it sends messages people actually want. The tier caps unique customers contacted first within a rolling 24 hours — replies from customers who messaged you first, and ongoing conversations within an open 24-hour service window, don't count against it the same way a cold business-initiated broadcast does.

Two things about this table matter more than the exact numbers. First, movement is automatic and behavior-based — there's no request form, no support ticket, no dashboard button that bumps you a tier. Meta's systems watch sending volume and recipient reaction over time and move a number up when both look healthy. Second, the numbers above are the commonly cited starting shape of the system, and Meta has adjusted specifics before — always confirm your number's current tier and limit directly in Meta Business Manager rather than assuming the figures here are exact on the day you're reading this.

What counts against the rolling 24-hour window, and what doesn't#

"Rolling 24 hours" trips people up because it isn't a calendar day that resets at midnight — it's a continuously moving window measured from each message. A customer you message at 9am today comes off the count around 9am tomorrow, not at midnight. That matters when you're planning a multi-day campaign: sending 800 people on Monday and another 800 on Tuesday doesn't simply add up to 1,600 against a 1,000-tier number if the windows overlap, so pacing needs to account for the rolling nature of the limit, not a fixed daily reset.

What actually counts toward the tier is narrower than "every message you send." It's unique customers you contact first — a business-initiated conversation opened by your broadcast, template, or outbound message. It is not: replies from a customer who messaged you first, ongoing back-and-forth inside an already-open 24-hour customer service window, or repeat messages to someone you've already counted as a unique contact within the current window. In practice this means an active support conversation or a customer replying to last week's order update doesn't eat into your broadcast headroom — only genuinely new, cold outbound contact does. Knowing this distinction is useful when you're trying to figure out why your "used" tier count doesn't match your gut sense of total messages sent that day.

What Quality Rating is, and what actually damages it#

If the tier is your ceiling, Quality Rating is the live gauge of whether Meta trusts you enough to let you send toward it. It's shown in Meta Business Manager as a simple traffic light — green (High), yellow (Medium), red (Low) — attached to your phone number, and it moves much faster than the tier does, because it's driven by recent recipient signals rather than long-run history.

The inputs are blunt and behavioral. People blocking your number, tapping "report as spam," consistently not reading what you send, and giving explicit negative feedback on recent templates all push the rating down. Replies, opens, and a low complaint rate hold it up or push it back toward green. Because the signal window is recent rather than lifetime, a rating can drop within a single bad campaign and recover within a few good ones — it reflects the last stretch of sending, not a permanent verdict.

Where the two systems collide: tier doesn't protect you from a quality crash#

This is the part senders learn the hard way, usually once. A number can be sitting comfortably in a high tier — cleared to message 100,000 unique customers today — and still have a broadcast interrupted before it finishes, because quality rating is evaluated continuously, in near real time, against the messages going out right now.

Picture a typical failure: a business exports its entire multi-year contact list, most of it never explicitly opted in to WhatsApp, and fires one marketing template at all 80,000 of them in a single batch because the tier technically allows it. Within the first few thousand sends, unfamiliar recipients start blocking the number and tapping "report as spam" at a rate Meta's systems read as a spam signal. Quality rating drops from green to yellow, then toward red, while the broadcast is still running. Meta can respond by pausing the specific template, slowing delivery, or restricting further business-initiated sends from that number — leaving tens of thousands of contacts unmessaged and the number's reputation worse than before the campaign started.

Nothing about the tier changed in that scenario. The ceiling was still 100,000. What collapsed was the permission to send toward it, because permission is a function of how recipients react in real time, not a fixed allowance. This is why "how do I send to more people without getting blocked" is the wrong framing — the honest version of the question is "how do I keep my quality rating healthy while I scale," and the answer is list hygiene and pacing, not a technical workaround.

Now run the same 80,000-contact campaign through a different process and the outcome looks nothing alike. The sender splits the list into recency-based segments, sends first to the 6,000 people who opened or replied to a message in the last 30 days, and holds for an hour. Reads come back healthy, blocks stay near zero, and the quality rating stays green. The next segment — a slightly older but still-engaged group — goes out, gets watched the same way, and clears. By the time the campaign reaches the coldest, least-recently-engaged slice of the list, the sender already knows enough to either trim that segment down, warm it with a lighter utility message first, or drop it entirely rather than risk the whole number's standing on contacts who were unlikely to respond well anyway. Same list, same tier, same 80,000 names — a completely different result, because the process respected quality rating as the actual constraint instead of treating the tier as the only number that mattered.

app.sabnode.com

Your SabNode plan quota: the other cap on the same send#

It's worth being explicit about this because it trips people up: your SabNode plan's message allowance and Meta's messaging tier are not the same limit, and neither one substitutes for the other. Meta's tier governs how many new unique WhatsApp customers your number can reach per rolling 24 hours. Your SabNode plan governs how many total messages — across WhatsApp, SMS, email and every other connected channel — your account can send in a billing month.

Say your account is on Growth with 50,000 messages/month, and your WhatsApp number just moved into Meta's 10,000-unique-customer tier. A single broadcast to 15,000 people would run into Meta's tier limit first, regardless of how much of your monthly SabNode quota is unused — the send would need to be split across more than one day, or trimmed to fit the rolling window. Conversely, if you'd already used 48,000 of your 50,000 monthly messages on other campaigns and channels, a fresh 10,000-recipient WhatsApp broadcast could hit your plan's quota before Meta's tier ever became the constraint (billed as overage at ₹0.10/message past the quota, rather than blocked outright). Before sizing any large send, check both numbers — Meta Business Manager for the tier and quality rating, and your SabNode billing page for remaining plan quota — and plan around whichever is tighter. If you're consistently bumping into either, pricing has the plan breakdown, and sabnode.com/signup gets you into a plan with no card required to start.

It's worth noting that the SabNode plan quota is the friendlier of the two limits to live with day to day, because it fails soft rather than hard — cross it and you're billed overage at ₹0.10 per extra message rather than having sends refused outright. Meta's tier and quality rating don't offer that same grace: cross the tier and a send simply won't reach new recipients until the rolling window clears room, and let quality rating fall far enough and Meta can restrict the number regardless of how much plan quota or budget you have left. Treat the plan quota as a cost-planning number and the Meta tier plus quality rating as the hard operational ceiling you design campaigns around.

How to scale your broadcast volume safely#

Scaling a WhatsApp broadcast program isn't a workaround you apply once — it's a discipline you repeat every time you grow the audience. Here's the sequence that actually moves both numbers, tier and quality, in the right direction.

1. Audit your opt-in before you touch volume. Go through your contact list and confirm every recipient explicitly agreed to hear from you on WhatsApp — a checkout checkbox, a keyword opt-in, a form tick, an initiated chat. Strip out anything scraped, purchased, or vaguely sourced. This single step prevents more quality-rating damage than any send-time tactic.
2. Segment before every large campaign. Split your audience by recency of engagement, purchase history, or lifecycle stage rather than treating the whole list as one block. A segment of people who opened your last three messages behaves completely differently from a segment that's been dormant for a year — don't send them the same way.
3. Send a first batch and watch it, don't fire the whole list. Push the campaign to a few hundred or a few thousand of your most-engaged, most-recently-opted-in contacts first. Give it 30–60 minutes and watch delivery, read rate, and — critically — block/report signals before deciding to continue.
4. Set a stop rule before you start, not during. Decide in advance what block or report rate pauses the send — for example, "pause if reports exceed 0.5% of the first batch." Deciding this ahead of time means you act on the number instead of talking yourself out of pausing mid-campaign.
5. Favor utility and transactional templates while you build volume. Order updates, appointment reminders, and payment confirmations get opened and rarely reported, because customers expect them. Let these carry your quality rating while marketing sends stay smaller and better targeted.
6. Keep marketing copy relevant even inside an approved category. An approved template can still read as spammy if the copy is generic or overly frequent. Personalize with real data, keep frequency sensible, and match the offer to the segment receiving it.
7. Make opt-out effortless and honor it instantly. A visible "reply STOP to unsubscribe" or a quick-reply opt-out button turns an unhappy recipient into a clean unsubscribe instead of a block or a report — and blocks and reports are what actually damage quality rating, not opt-outs.
8. Warm up new numbers deliberately. A freshly registered number sending its full tier allowance on day one is asking for a quality-rating drop before it's earned any trust. Ramp volume over one to two weeks, watching quality rating at each step.
9. Re-check tier and quality rating before every large send, not just once. Both can change between campaigns. Build a habit of glancing at Meta Business Manager (or your WaChat number settings) before you schedule anything above your usual volume.
10. Let engagement, not ambition, set your next ceiling. If a fully-sent campaign holds a green rating and strong reads, you have room to grow the next one. If reads dipped or reports ticked up, hold volume flat or trim the segment before trying again.

Common mistakes that cap broadcasts before they should#

Almost every "why did my broadcast get throttled" story traces back to one of these avoidable habits.

• Blasting a stale or unengaged list at full volume immediately. Sending your entire historical contact base in one go — instead of a watched first batch — is the single fastest way to crash a quality rating mid-campaign.
• Ignoring an early quality-rating dip. A slide from green to yellow is a warning, not background noise. Continuing to send at full volume after the first sign of trouble is how yellow becomes red.
• Making opt-out hard or ignoring "STOP." If unsubscribing is buried or doesn't work, frustrated recipients reach for block and report instead — both of which hurt quality rating far more than a clean opt-out ever would.
• Treating the tier as permission to send everything at once. A 100,000-person tier is a ceiling for a healthy number over time, not a green light to fire 100,000 messages in a single uncontrolled batch.
• Forgetting the SabNode plan quota exists alongside Meta's tier. Sizing a broadcast against Meta's limit alone and then hitting your monthly plan quota mid-campaign is an easy, avoidable surprise — check both before scheduling.
• Buying or scraping numbers to "grow the list fast." Contacts who never opted in block and report at far higher rates, and there's no volume of sending that offsets the quality damage they cause.
• Sending a brand-new number at established-account volume. Skipping the warm-up period means a fresh number gets judged on its first big send with no track record to soften a rough patch.
• Disguising marketing content as low-scrutiny utility messaging. Beyond the template-approval risk, recipients notice when a "your order shipped" template is actually a promotion — and that mismatch generates reports.

Conclusion#

WhatsApp's broadcast limits aren't one number to memorize — they're two systems working together: a messaging tier that caps how many new customers you can reach per day, and a quality rating that decides, in near real time, whether Meta will let you send toward that cap at all. Layered on top is your own SabNode plan quota, a separate monthly allowance that can bind before or after Meta's limit depending on how you've been sending. Treat all three as one picture before you schedule a large campaign, and you'll stop being surprised mid-broadcast.

The actual lever for scaling safely was never a clever workaround — it's the unglamorous discipline of opt-in hygiene, segmentation, watching a first batch before committing the rest, and making it effortless for unhappy recipients to leave quietly instead of blocking and reporting. Numbers that follow that discipline climb tiers on their own; numbers that skip it get capped, paused, or restricted regardless of how generous their theoretical ceiling looked on paper.

If you're building out a broadcast program from scratch, pair this with the practical setup in how to run WhatsApp broadcast campaigns that convert and the template mechanics in the message templates guide — both feed directly into keeping the quality rating this article is built around actually green. When you're ready to put the tier and quality-rating visibility in front of your own team, SabNode's signup is free and takes no card to start, and pricing has the full plan breakdown if you're comparing message quotas against your expected volume.