Summarise this article with:
On this page
- What a WhatsApp messaging limit actually is
- Why messaging limits are now set at the business portfolio level
- The tier ladder: 250 to Unlimited
- Throughput: the second ceiling, measured per second
- Per-user marketing limits: the third ceiling nobody sees
- Diagnose it: symptom, ceiling, fix
- Worked example: an illustrative Kota coaching institute
- A 60-day plan to climb from 250 to 100,000
- What most teams get wrong about messaging limits
- Get started with InfiQ
WhatsApp Messaging Limits & Tiers: 250 to Unlimited (2026)
Your broadcast went out at 10:30 IST to 18,000 contacts. By 10:34 the dashboard shows 9,800 sent and then a wall of failures, and the marketing lead is asking whether the number is banned. It almost certainly is not. You hit a ceiling — and there are three of them, enforced by three different systems, with error messages that rarely say which.
Most teams assume there is one number: "we're on tier 10,000, so we can send 10,000 messages a day." That is wrong three ways. The limit counts unique users, not messages. It is shared across every phone number in your business portfolio. And it is not the only thing that can stop a send. This guide covers all three ceilings in the order you should check them.
Key points
- A WhatsApp messaging limit counts unique users contacted outside an open customer service window in a rolling 24-hour period, not messages sent.
- Messaging limits are set at the business portfolio level and shared across every phone number in it, so adding a number does not add capacity.
- The ladder runs 250 → 2,000 → 10,000 → 100,000 → Unlimited; the step to 2,000 comes from business verification, partner verification, or 2,000 high-quality messages in 30 days.
- The
messaging_limit_tierfield is deprecated; readwhatsapp_business_manager_messaging_limit, which returns values such asTIER_250. - Throughput is a separate ceiling reaching 1,000 messages per second for eligible numbers with a Medium or higher quality rating.
- Per-user marketing limits are a third, dynamic ceiling that applies in India and surfaces as error 131049.
What a WhatsApp messaging limit actually is
A WhatsApp messaging limit is the maximum number of unique users a business can message outside an open customer service window in a rolling 24-hour period. Each part of that definition is a place teams miscount.
Unique users, not messages. Four utility templates to the same customer in one day consume one unit, not four. A portfolio on the 10,000 tier can send 36,000 messages to 9,000 customers and stay inside its limit.
Outside an open customer service window. A customer service window (CSW) is the 24-hour period that opens when a user messages your business, during which you can reply freely. Traffic inside an open CSW does not consume your limit — which is why a support-heavy business barely notices a low tier while a campaign-led business fails on day one.
Rolling, not calendar. There is no midnight IST reset. A send finishing at 23:50 still occupies your allowance at 09:00 next morning, which is why "half tonight, half tomorrow" usually fails on the second half.
Meta's primary reference is the messaging limits documentation, updated 21 May 2026.
Why messaging limits are now set at the business portfolio level
Messaging limits are set at the business portfolio level and shared across all phone numbers in that portfolio. This breaks the model most teams inherited: each number gets its own tier.
If you run three numbers under one portfolio (sales, support, transactional) and the limit is 10,000, all three draw from one allowance of 10,000 unique users per rolling 24 hours. A fourth number buys zero headroom and one more quality rating to defend.
The second-order effect matters more. Because the allowance is pooled, a campaign on your marketing number consumes capacity your order notifications needed. We see this most in D2C teams where a growth pod owns the campaign number and engineering owns the transactional one, and nobody has agreed who gets the last 2,000 slots. Reserve a floor: gate the campaign scheduler behind a check that reads current utilisation before it fires. Our WhatsApp Business API platform overview shows how both views fit together.
The tier ladder: 250 to Unlimited
| Tier | Unique users per rolling 24h | How you reach it |
|---|---|---|
| TIER_250 | 250 | Default for every new business portfolio |
| 2,000 | 2,000 | Business verification, or partner verification, or 2,000 high-quality messages in 30 days |
| 10,000 | 10,000 | Automatic scaling on quality and utilisation |
| 100,000 | 100,000 | Automatic scaling on quality and utilisation |
| Unlimited | No cap | Automatic scaling on quality and utilisation |
Notice what is absent: there is no 1,000 tier. Teams searching for "WhatsApp messaging tier 1000" are working from an older ladder or an unmaintained vendor post. If a page still describes a 1K tier, treat the rest of it as suspect.
The three routes to 2,000
The step to 2,000 is the only rung you can force. You need one of these.
- Business verification. Verify the portfolio in Meta Business Manager — for an Indian private limited company, usually the certificate of incorporation plus address proof matching the legal name exactly. Mismatched names are the most common rejection we see: "AIO Infinity Pvt Ltd" against "AIO INFINITY PRIVATE LIMITED" costs a cycle.
- Partner verification. Your Business Solution Provider vouches for the portfolio. Usually the fastest route, and one reason to onboard through an official Meta Business Solution Provider rather than a reseller.
- Organic quality volume. Deliver 2,000 high-quality messages in 30 days. Works if you already have conversation volume and have not filed paperwork.
Do business verification regardless: it also gates the Official Business Account badge and the higher template cap — 6,000 templates per WABA with an approved display name, against 250 if the parent portfolio is unverified.
Automatic scaling above 2,000
Above 2,000 you do not apply. Meta raises the limit automatically through 10,000, 100,000 and Unlimited based on sustained quality and utilisation. Both words carry weight.
Quality is the user-feedback signal expressed as your quality rating: GREEN (high), YELLOW (medium, "may soon be paused or disabled"), RED (low, "in danger of being paused or disabled soon") and UNKNOWN (pending, no feedback yet). It is driven by blocks and report taps, not delivery success — high delivery with a high block rate will hold your tier down. Our WhatsApp quality rating guide has the recovery runbook.
Utilisation is whether you use the allowance you have: a portfolio at 2,000 sending 300 unique users a day gives the scaling system nothing to act on.
Reading your tier from the API
The messaging_limit_tier field is deprecated. Read whatsapp_business_manager_messaging_limit instead, which returns values in the form TIER_250. A stale tier reading during an incident is worse than none. Pipe that value into monitoring alongside quality rating and template status, and subscribe to webhooks so a downgrade reaches your on-call channel rather than sitting in WhatsApp Manager. The WhatsApp webhooks guide covers the plumbing; the InfiQ developer docs show where these fields surface.
Throughput: the second ceiling, measured per second
Throughput is the rate at which the API accepts and dispatches messages, measured in messages per second, and it is separate from your messaging limit. You can be nowhere near your daily unique-user allowance and still fail because you pushed too fast.
Throughput can scale to 1,000 messages per second for numbers with a Medium or higher quality rating that meet Meta's eligibility conditions: an unlimited messaging limit plus more than 100,000 unique users per 24 hours, or unlimited initiation capability. High throughput is downstream of topping the ladder: you cannot buy 1,000 messages per second on TIER_250.
For anyone building a sender: a configurable rate limiter, exponential backoff, and idempotency keys so a retry does not double-send. If you use a managed broadcast campaign tool, ask the vendor how it paces sends and what it does with failures. Pacing is one of the least-discussed differences between platforms.
Per-user marketing limits: the third ceiling nobody sees
A per-user marketing limit is a dynamic cap WhatsApp applies to how many marketing template messages any single user receives across all businesses, based on that user's recent read-rate and inbox load. It is not a fixed number, it is not published, and it adapts automatically per person.
It is invisible from your side and varies by recipient. Two customers on the same list, both opted in — one gets your campaign, one does not, because the second has been ignoring marketing templates from other businesses.
| Behaviour | Detail |
|---|---|
| Where it applies | Not active where sender or recipient is in the EEA, UK, Japan or South Korea. India is not excluded — the cap applies here |
| US numbers | WhatsApp does not currently deliver marketing templates to +1 US numbers at all |
| What is exempt | Messages inside a 24-hour CSW, opened by a user reply, do not count |
| Error and retry | A throttled send surfaces as error 131049; retrying before 24 hours risks further failures |
The retry rule turns small problems into large ones. When a chunk of a campaign fails, the instinct is to re-queue immediately. Do not — repeated undelivered marketing attempts are the pattern that pushes a quality rating toward YELLOW. Meta's per-user marketing limits documentation, updated 17 June 2026, is the primary reference.
The structural answer is to stop treating marketing templates as your main reach mechanism. They face all three ceilings; messages inside an open CSW face none. Anything that earns a reply — a useful utility notification, a WhatsApp Flow that completes a task in-chat, a question worth answering — converts a capped send into an uncapped conversation, and InfiQ's flow builder and shared inbox handle that reply side for you.
Diagnose it: symptom, ceiling, fix
Work this table top to bottom the next time a send fails.
| Symptom | Ceiling you hit | Fix |
|---|---|---|
| Send stops at a round number (250, 2,000, 10,000); the rest fail | Messaging limit on the portfolio | Read whatsapp_business_manager_messaging_limit; wait for the rolling window; verify the business if on TIER_250 |
| Failures spread evenly across the list, no round-number cliff | Per-user marketing limit (error 131049) | Do not retry inside 24 hours. Segment out low-engagement contacts |
| Errors start seconds into a fast send, stop when you slow down | Throughput | Add a rate limiter and backoff; check quality rating |
| A second number fails though it has sent almost nothing | Portfolio pooling | The allowance is shared. Raise the tier or leave a transactional floor |
| One template fails; others on the same number send fine | Template pausing (3h → 6h → disabled) | Fix content or audience before the second strike |
Marketing templates to +1 US numbers never arrive |
Regional non-delivery | Not a limit. Reach US contacts another way |
| A utility template starts costing more with no change from you | Auto-recategorisation | Content, not intent, decides category. See the template categories guide |
Two rows are not messaging limits at all — during incidents, half the "we've been throttled" reports are a paused or recategorised template. Template pausing escalates on a fixed schedule: a first RED-quality instance pauses the template for 3 hours, a second for 6 hours, a third disables it. Meta's template quality docs list every status.
Worked example: an illustrative Kota coaching institute
Take a hypothetical test-prep institute in Kota with 38,000 parent contacts, all opted in at admission, running one business portfolio with two numbers. Portfolio tier: 10,000, quality rating GREEN. The academic team wants to send a mock-test result notification to all 38,000 parents on a Sunday evening.
The naive plan. Queue 38,000 sends at 19:00 IST. Roughly 10,000 unique parents receive it; the rest fail. Because the window rolls, re-queuing at 07:00 Monday fails again, and the team concludes the number is banned.
The arithmetic that applies. At 10,000 unique users per rolling 24 hours, 38,000 contacts need four rolling windows. The announcement lands over roughly four days, so the last cohort hears on Wednesday about a test their child sat on Saturday — a product problem, not a throttling problem.
The plan that works. Send by batch in cohorts of about 9,000 — under 10,000, leaving roughly 1,000 unique users of headroom for fee receipts and absence alerts. Then engineer replies: end the notification with a Flow that opens a scorecard or books a counselling slot. Every parent who taps opens a 24-hour CSW, and everything sent inside it sits outside the messaging limit entirely. Across a month the uncapped conversation volume exceeds the capped broadcast volume, and utilisation stays high enough for automatic scaling to act on.
On cost, price follows category, not tier, and from 1 October 2026 the calculus shifts because Meta resumes charging for service messages and for utility messages sent inside an open CSW — both free today. InfiQ's current India rates are utility ₹0.19 and marketing ₹0.94 per delivered message (ex-GST). Model both before you redesign around CSW volume. Our cost breakdown, 2026 pricing guide and Meta Business Agent Platform analysis cover the October change.
A 60-day plan to climb from 250 to 100,000
- Days 1–3: file business verification. Submit the portfolio with the legal name matching your certificate of incorporation character for character. Enable two-step verification on every number.
- Days 1–3: ask about partner verification. If your provider is an official Meta Business Solution Provider, this is often the shortest path to 2,000.
- Days 4–7: instrument before you scale. Put
whatsapp_business_manager_messaging_limit, quality rating and template status in one view. Alert on any move to YELLOW and any template pause. - Days 7–14: earn the organic route in parallel. Deliver 2,000 high-quality messages over the 30-day window using wanted utility notifications — order updates, confirmations, receipts. Not marketing templates.
- Days 14–30: build reply mechanics into every send. Add a Flow, a quick-reply button or a real question to your highest-volume templates. This decouples reach from tier.
- Days 21–45: raise utilisation deliberately. Approach your current allowance consistently, not once, while holding GREEN. Automatic scaling watches sustained behaviour.
- Days 30–45: prune the list holding you down. Suppress contacts who have not engaged across recent marketing sends. They drive per-user failures and block-driven quality damage.
- Days 45–60: only now tune throughput. With the limit rising, add rate limiting, backoff and idempotency so throughput does not become the new failure mode.
Keep template hygiene tight throughout — the common template rejection reasons post covers the review-side failures that stall step 4.
What most teams get wrong about messaging limits
They add phone numbers. The reflex response to throttling does nothing, because the limit is pooled, and it adds a quality rating you now have to defend.
They treat the limit as a message budget. It is a unique-user budget. Count people.
They retry immediately. Failed sends get re-queued within minutes, risking further failures and feeding the quality signal that keeps the tier down. Error 131049 means wait.
They optimise the wrong ceiling. Engineering time goes into parallel workers when the real constraint is a 2,000 limit that a document upload would have lifted in days.
They ignore utilisation. A portfolio that never approaches its allowance never scales. To reach 100,000 you earn it at 10,000, visibly and repeatedly.
They confuse a paused template with a throttled number. Different fixes, different clocks — 3 hours then 6 then disabled, versus a rolling 24-hour window. The state of WhatsApp business messaging in India post has wider context.
Get started with InfiQ
Messaging limits punish teams that scale by guesswork. If you can see your portfolio tier, quality rating and template status in one place, and your sender paces itself and handles 131049 correctly, the ladder climbs on its own.
Ready to scale past the 250 messaging limit without risking your number? Start your 7-day free trial — InfiQ gets you live on the official WhatsApp Business API in about 2 hours, with quality and tier analytics in one dashboard and InfiQ Flows to turn capped broadcasts into uncapped conversations. Or book a walkthrough to see it mapped to your own send volumes first.
