Short answer: Your broadcast ceiling counts unique recipients in a moving 24-hour period, not messages. It starts at 250 and climbs through 2,000, 10,000 and 100,000 to unlimited. It is shared by every phone number in your business portfolio, so a second number buys no headroom. Quality rating gates the climb.
What the limit actually counts
Two numbers get confused constantly. A messaging limit is, in Meta’s words, “the maximum number of unique WhatsApp user phone numbers your business can deliver messages to, outside of a customer service window, within a moving 24-hour period”. The same page is blunt about what it does not do: “The messaging limit does NOT limit the number of messages your business can send.” Ten messages to one person cost one slot; one message to ten people costs ten.
Throughput is how fast you may hand messages to the API — a per-second cap on requests, saying nothing about how many distinct people you may reach. Most “WhatsApp broadcast without ban” guides blur the two, so people buy capacity they already have and ignore the ceiling that binds.
The ceiling is also portfolio-wide. Meta’s developer documentation says messaging limits “are shared by all business phone numbers within a portfolio”, and that “it’s possible for one number to consume all of the portfolio’s messaging capability within a given period”. The Help Centre agrees. Adding a number does not add reach — it adds a way for one campaign to eat another’s allowance. Same finding, from the number-supply side: getting a +91 number for the WhatsApp API.
The ladder depends on which Meta page you read
We read three Meta pages on 15 October 2026. They do not agree. We show all three rather than picking the one we like, and we do not explain the discrepancy, because we cannot.
| Meta Business Help Centre | Developer docs, Messaging Limits (/docs/whatsapp/messaging-limits) | Developer docs, Messaging Limits (/docs/whatsapp/api/rate-limits/) | |
|---|---|---|---|
| Starting limit | not stated | “Newly created business portfolios have a messaging limit of 250” | not stated |
| Rungs above it | 2,000, 10,000, 100,000, Unlimited | “can be increased to:” — followed by no values on the day we read it | “Tier 1 … 1K”, “Tier 2 … 10K”, “Tier 3 … 100K” |
| Scope | shared by all numbers in the portfolio | shared by all numbers in the portfolio | described per business phone number |
| Quality window | “the past 7 days” | not stated | “a rolling window of the past 24 hours” |
| Flagged / Restricted statuses | “discontinued as of Oct 7th, 2025” | not mentioned | described as current |
Three things follow. The starting limit of 250 appears on only one of the three. The full ladder appears on only one, and it is the Help Centre rather than the developer documentation. And /docs/whatsapp/api/rate-limits/ still describes the Flagged and Restricted phone-number statuses that the Help Centre says were “discontinued as of Oct 7th, 2025” — over a year before we read it.
That last one matters. If your agency’s playbook or your provider’s onboarding deck warns about a number going “Flagged” or “Restricted”, it rests on a page Meta’s own Help Centre has superseded.
Our own reading of the /docs/whatsapp/messaging-limits page on 4 October 2026 listed rungs at 10,000 and 100,000; on 15 October it showed none. We have not carried those forward.
Your send speed is not the problem
Meta’s throughput page, read the same day:
| Figure, read 15 October 2026 | |
|---|---|
| Cloud API default, per registered number | “up to 80 messages per second (mps) by default” |
| Automatic upgrade | “1,000 mps at no cost to you” |
| Upgrade eligibility | an unlimited messaging limit, 100,000+ unique users messaged outside customer service windows in a moving 24-hour period, and a quality score of “YELLOW or higher” |
| WhatsApp Business app numbers | “a fixed throughput of 20 mps” |
| Time to exhaust a 250-per-day limit at 80 mps | 3.13 seconds |
| Time to exhaust a 2,000-per-day limit at 80 mps | 25.00 seconds |
A new portfolio can transmit its entire daily allowance of unique recipients in a little over three seconds. Throughput constrains nobody below six figures a day, and the upgrade is gated on already holding an unlimited messaging limit — so speed cannot be bought ahead of reach.
Quality rating: seven days, or twenty-four hours
The Help Centre defines quality rating as “a rating based on the recent messages that your customers have received over the past 7 days”, determined by “feedback from your customers like the reason they blocked your number and other reporting issues”. The developer page says it reflects “a rolling window of the past 24 hours”. Both were live on 15 October 2026.
The states are Green (high), Yellow (medium) and Red (low), and what drives them is visible: when a user blocks a business they pick a reason, and the published list is “No longer needed”, “Didn’t sign up”, “Spam”, “Offensive messages” and “No reason”. Hover over a Yellow or Red rating in WhatsApp Manager for block reasons where available, and for the lowest daily score over 30 days.
“Didn’t sign up” is the one to watch: it is the one your own list hygiene controls, and it flags a list bought, scraped, or inherited from a channel the recipient never consented to.
The limits that bite before the daily cap
Two mechanisms usually bite before the daily ceiling does.
Template pausing. When a template reaches the lowest quality rating, Meta pauses it: “1st Instance: Paused for 3 hours”, “2nd Instance: Paused for 6 hours”, “3rd Instance: Disabled”. A paused template cannot be sent at all. Nine hours of pausing is 12.50% of a three-day promotion, and it lands on the template you were relying on.
Per-user marketing limits. Meta caps how many marketing templates an individual may receive from any business, set “based on several factors, including a dynamic view of an individual’s recent marketing message read rate”. No number is published and we will not invent one. What is published: blocked deliveries surface on the messages webhook as failed with error code 131049, marketing sent inside a customer-initiated 24-hour window does not count, and Meta advises waiting “at least 24 hours before attempting to resend”.
Repeated policy violations escalate on a published schedule: a 1- or 3-day block on templates, then 5-, 7- or 30-day blocks on sending anything, then an account lock removable only by appeal, then permanent disablement. Appeals “typically take 24 to 48 hours”. Template misclassification is a listed cause; we cover categorisation in utility versus marketing templates.
Worked example: 60,000 contacts and a three-day window
Suppose you have 60,000 opted-in contacts and a three-day sale. One pass over the base takes:
At ₹1.09 per delivered marketing message — AiSensy’s published India rate, read 15 October 2026 — the per-message cost does not change with your tier. What changes is how much of the base you reach inside the window — and so what every fixed cost works out to per person reached.
No provider’s plan fee could be verified on the day of writing (Interakt’s card would not load that day), so the fee column below is an illustration at ₹2,500 a month, not a quote. Use your own invoice instead.
| Portfolio limit per day | Unique contacts reached in 3 days | Share of the 60,000 base | Message spend at ₹1.09 | Illustrative ₹2,500 fee, per reached contact | All-in per reached contact |
|---|---|---|---|---|---|
| 250 | 750 | 1.25% | ₹817.50 | ₹3.3333 | ₹4.4233 |
| 2,000 | 6,000 | 10.00% | ₹6,540.00 | ₹0.4167 | ₹1.5067 |
| 10,000 | 30,000 | 50.00% | ₹32,700.00 | ₹0.0833 | ₹1.1733 |
| 100,000 | 60,000 | 100.00% | ₹65,400.00 | ₹0.0417 | ₹1.1317 |
Over a 30-day month rather than a 3-day window, that same ₹2,500 is ₹0.3333 per reachable unique contact on the 250 tier against ₹0.0417 on the 2,000 tier — exactly 8.00 times as much for the same fee. The rate card is identical in both rows; the bill per outcome is not.
So 60,000 contacts and a three-day deadline do not fit WhatsApp broadcast at any rung below 100,000 per day. If the deadline is real, the reach must come from a channel with no platform cap on daily unique recipients. Plivo’s published India domestic voice carriage was ₹0.38 per minute on 15 October 2026 on a 30-second pulse, so one 30-second dial is ₹0.19: 60,000 dials are ₹11,400.00 against ₹65,400.00 for the same 60,000 as marketing messages — about 5.74 times. Voice brings its own compliance layer, set out in bulk voice call pricing, and the channel view is in SMS vs WhatsApp vs voice. The reverse holds too: at ₹0.145, 60,000 utility messages are ₹8,700.00, or about 0.76 times the voice figure. Category decides the comparison, not channel.
What actually raises your ceiling
Per the Help Centre, a portfolio moves to the next rung if “More than 50% of your current limit was used in the last 7 days” and “You are sending high-quality messages across all your business phone numbers and templates”, landing “within 6 hours after these criteria are met”. The developer page gives two routes to the 2,000 rung: verify your identity, or send 2,000 delivered messages to unique numbers outside customer service windows over 30 days using high-quality templates.
Read together, those conditions are uncomfortable: you must use at least half your allowance to earn more of it, while keeping quality high. Sending under half your limit to stay safe is what keeps a portfolio at 250 indefinitely; sending your worst list to fill the quota is what takes quality down. Only a consistently used, consistently clean list satisfies both.
Where this sits on the bill
The four layers of your WhatsApp bill — platform rate, intermediary markup, plan and seat fees, compliance and tax — give a cost per message. Broadcast limits are the fifth thing, the one that never reaches an invoice: the gap between sent and reached. A messaging limit does not raise your rate by a paisa. It decides how many people your fixed costs are divided by, and whether a dated campaign is possible at all. Hence a cost per reached customer rather than a cost per message, here and on our pricing page.
Frequently asked questions
Does a second WhatsApp number double my broadcast limit? No. Both Meta pages we read on 15 October 2026 state the limit is shared across every business phone number in the portfolio, and that one number can consume all of it. Extra numbers separate brands, departments and display names — they do not add reach.
What is the broadcast limit on a brand-new account? “Newly created business portfolios have a messaging limit of 250” — that is 250 unique recipients in a moving 24-hour period, not 250 messages.
Will one bad campaign get my number banned? Not on the published mechanics. A low quality rating pauses templates for 3 then 6 hours before disabling them, and violations escalate through 1-, 3-, 5-, 7- and 30-day blocks before an account lock. The realistic damage is a stalled template and a rating that takes days of clean sending to recover — on a deadline, the same thing as a ban.
How many marketing messages can I send to one person? Meta publishes no number. The cap adapts to the individual’s recent engagement, and blocked deliveries return error code 131049. Marketing sent inside a 24-hour window the customer opened does not count against it.
Does DLT registration apply to WhatsApp broadcasts? We have looked for a TRAI instrument extending DLT to WhatsApp, or exempting it, most recently for our DLT guide, and found neither. It demonstrably applies to SMS and voice. We will not tell you it applies to WhatsApp without an instrument to cite.
Verification note
Every figure on this page was verified against a live primary source on 15 October 2026 and is dated to that reading. Where two of Meta’s own pages disagree, we publish both and explain neither. We publish no engagement statistics of our own and no xreach51 rates.
What we could not verify. A single Meta source for the full messaging-limit ladder: the Help Centre gives it, the developer documentation does not. Any numeric per-user marketing cap — Meta publishes none. A current platform plan fee from an Indian provider: Interakt’s card would not render on the day, so the ₹2,500 monthly fee used above is a labelled illustration, not a quote. A dated government citation for the 18% GST on telecom services, which is the rate providers’ cards apply but which we have not yet pinned to a dated schedule entry.
Sources. Meta Business Help Centre, About your WhatsApp Business phone number’s quality rating; Meta for Developers, Messaging Limits (/docs/whatsapp/messaging-limits); Meta for Developers, Messaging Limits (/docs/whatsapp/api/rate-limits/); Meta for Developers, Throughput; Meta for Developers, Template pausing; Meta for Developers, Per-user marketing template message limits; Meta for Developers, WhatsApp Business Platform policy and spam enforcement; AiSensy pricing page (India card); Plivo India voice pricing. All read 15 October 2026.