WhatsApp Broadcast Limits: What Actually Constrains a Send
The real WhatsApp broadcast limits: per-number daily caps, hourly ceilings, warm-up and plan allowances - versus the myths.
Search “WhatsApp broadcast limits” and you will find conflicting magic numbers: 256 contacts, 5 chats a day, 1,000, 10,000 - each stated with total confidence and none of them the actual answer. The real constraints are different in kind: most of them are not numbers the platform publishes, and the ones that are numbers belong to your setup, not to WhatsApp’s rule page.
This guide separates the four constraints that actually govern a send from the folklore, and shows what reaching each limit looks like when your tooling handles it properly.
The myth of the magic number
The 256 figure - the size of a WhatsApp broadcast list on the phone app - is the most persistent, and it describes a feature nobody doing real campaigns uses: hand-built broadcast lists on a personal phone. Campaign tools do not use broadcast lists at all; each message is an individual send, which is why the 256 ceiling does not apply to them.
The other numbers - how many messages a day WhatsApp “allows” - confuse platform tiers for the official API with the practical ceiling any careful sender observes. Official API messaging limits are published by Meta and raise with the number’s quality tier (see the current table), and they apply to a product most campaign-focused businesses do not use. What constrains a real sender is the set below.
The four real constraints
| Constraint | What it bounds | What reaching it looks like |
|---|---|---|
| Consent and engagement | Whether messages land at all | Falling read rates, blocks, restrictions |
| Per-number daily + hourly caps | Messages per number per day/hour | Queue parks, announces resume |
| The warm-up ramp | A new number’s early ceiling | Cap grows ~1.6x daily from 20 |
| The plan allowance | Total messages per month | Campaigns pause until the month rolls over |
Two of these are yours to configure; two of them are physics. The sections below take each in order, because confusing them is how businesses either fear the channel or burn numbers.
Constraint 1: consent and engagement
The binding constraint - the one no configuration can raise - is whether recipients want the messages. A number whose sends get read, replied to, and forwarded sustains its ceiling indefinitely. The same ceiling on a number sending unwanted messages collapses into blocks, reports, and eventually restriction, because engagement is what enforcement reads.
This is why “how many can I send” is the wrong first question. The right one is “how many can I send while the read rate holds” - and the answer is discovered per number, watched in the health report, not looked up.
Constraint 2: per-number daily and hourly caps
The configurable layer. A mature number sustainably carries 100-300 messages a day; Automate’s default daily cap is 100, with an hourly cap of 30 on top of it - because a number that spends its whole allowance in one 9 AM burst and idles for 23 hours produces a shape no human does.
Both sent and failed dispatches count, and the counters live outside your delivery history: clearing history never refreshes a quota, so the caps cannot be eroded accidentally or otherwise. Set per connected number, raised as a number earns it - the caps are guardrails sized to what a business number can carry, not arbitrary throttling.
Constraint 3: the warm-up ramp
A brand-new number has no ceiling yet - it has to earn one, which is why warm-up starts it at 20 messages a day and grows the cap about 1.6x daily until it reaches the configured limit, typically within a week. The full warm-up schedule explains the day-by-day mechanics.
Skipping the ramp does not remove this constraint; it removes the number. The volume spike on day one is one of the clearest restriction signals there is.
Constraint 4: the plan allowance
The commercial layer: each Automate plan includes a monthly message allowance - 15,000 on Starter, 37,000 on Growth, 75,000 on Enterprise - at one flat yearly price with no per-message fees.
The allowance is a ceiling, not a target, and it sits far above what a single number can healthily carry (a mature number’s 300 a day is only ~9,000 a month). That gap is deliberate: real volume is built from several numbers running in parallel, each inside its own comfort zone, and the plans are shaped - 2, 5, 10 connected lines - to match that reality. Reach the plan ceiling and campaigns pause until the month rolls over or you move up a tier.
What happens when a limit is hit
This is where tooling quality shows. The wrong behavior - and the behavior of crude tools - is to fail silently, drop contacts, or push through into a ban. A properly built queue:
- Parks itself when a daily or hourly cap is reached, with the resume time stated in the activity feed.
- Sleeps through quiet hours (10 PM to 8 AM by default, in your timezone and the recipient’s) and resumes after.
- Survives interruptions - a campaign interrupted by a restart or a dropped session resumes on its own, with queued contacts intact for a full year.
- Trips a circuit breaker on five consecutive failures or one hard signal, rather than pushing a struggling number into a permanent ban.
A limit reached should look like a pause with a plan, never like data loss. That is the difference between limits that protect the campaign and limits that destroy it.
Building real volume, legitimately
Put the four constraints together and the path to high volume is not “raise the limits” - it is:
- Consent-first lists, so engagement stays positive and constraint 1 never binds. The opt-in guide covers the collection.
- Several warm numbers in parallel, each inside its 100-300 a day, audiences split across them.
- A plan shaped for it - 37,000 or 75,000 a month with 5 or 10 lines - so the allowance never binds before the numbers do.
- Queues that park, resume, and never lose their place, so a large campaign is a calm schedule instead of a race.
That is the entire system, and the limits are not its enemy - they are the reason numbers on it survive season after season. The campaign playbook covers the full system these constraints live inside, the deliverability pillar explains the protection stack, and the plans show the allowances and line counts when you are ready to size it.