WhatsApp Messaging Limits Explained for 2026

Most teams discover WhatsApp messaging limits the hard way. They build a list, schedule a broadcast, fire it off, and watch half the messages fail with no obvious error. The campaign looked fine in the dashboard. The reach number just capped out.

That gap between what you sent and what landed is almost always a messaging limit. WhatsApp Business API limits decide how many people your business can reach with business-initiated messages in a rolling 24-hour window, and the rules are stricter than most marketers expect when they first move off the free app.

This is for the people who run these sends - marketers planning broadcasts, support teams worried about throttling, founders forecasting reach, developers wiring up the API. What the limits are, what counts, how to climb the tiers, and the operational traps that throttle accounts even when the numbers look fine.

What the limit actually measures

A WhatsApp messaging limit isn't a cap on total messages. It's a cap on unique customers you can start a conversation with in a moving 24-hour period.

Meta's documentation is specific. The limit counts the maximum number of unique WhatsApp user phone numbers you can deliver business-initiated messages to, outside an open customer service window, within a rolling 24 hours. Message the same customer five times in a day and that's one against your limit, not five. Message 5,000 different people once each and that's 5,000.

That changes how you plan. A retention flow that messages the same engaged buyers repeatedly barely touches your limit. A cold blast to a fresh list burns straight through your tier.

The other thing to burn into memory: limits are set at the business portfolio level, not per phone number. If your portfolio has several numbers, they all draw from one pool. One number running a heavy campaign drains the capacity the others were counting on. Split sends across two numbers expecting double the reach and both slow down at the same time, because they were sharing one limit the whole way.

The tiers

New business portfolios start small on purpose. WhatsApp wants to see that you send messages people want before it lets you scale.

• 250 unique customers per 24 hours, where every new portfolio begins
• 2,000, the first real jump, unlocked by completing a scaling path
• 10,000
• 100,000
• Unlimited

The 250 start feels almost insultingly low if you're used to email, where you can blast 50,000 on day one. That's deliberate. WhatsApp is a permission-heavy channel and the small starting cap is the cost of entry. The climb from 250 to 2,000 is quick if you do it right, and the tiers above can lift on their own.

These are the numbers people mean by the "WhatsApp API limit per day", though "per day" is misleading. It's a rolling window, not a calendar-day reset, and that detail trips up more campaigns than any other rule here.

From 250 to 2,000

The first jump is the one every team has to clear, and it's more procedural than people assume. You don't negotiate your way up, you earn it by hitting one of three scaling paths:

1. Verify your business through Meta Business Verification.
2. Have your solution provider verify your business, if a partner onboarded you.
3. Send 2,000 delivered messages outside customer service windows to unique phone numbers within a 30-day moving period, using templates that hold a high quality rating.

Clear a path and Meta reviews your message quality. If the review is positive, your portfolio jumps to 2,000 and you get an email plus a developer alert. If it's denied, you stay put and get told which alternate route to try, usually identity verification or simply sending more high-quality delivered messages.

"High quality rating" is doing a lot of work there. You can technically send your 2,000 messages, but if customers are blocking you or marking spam, the quality signal tanks and the increase stalls. Volume alone doesn't move you up. It's volume plus an audience that wants to hear from you.

Automatic scaling past 2,000

After 2,000 the manual part is mostly over. WhatsApp shifts you to automatic scaling, watching two things: you're sending high-quality messages across all your numbers and templates, and in the last 7 days you've used at least half of your current limit.

Meet both and Meta bumps you up a tier within about six hours. The second condition is the one teams forget. If you never use more than half your limit, you never get a higher one. WhatsApp has no reason to hand you 10,000 capacity if you're comfortably sending 1,200. The system gives headroom to businesses clearly growing into it, not to pad numbers that sit idle.

So if you want a higher tier before a big seasonal push, grow your send volume in the weeks leading up, not the week of. A team that wants 10,000 for Diwali should be regularly clearing 1,000-plus quality sends well before October, not scrambling in the final fortnight.

What counts, and what doesn't

This is where the rolling window and the customer service window both come in, and getting it wrong is how teams throttle themselves.

Business-initiated messages count. When you start a conversation - template messages, broadcasts, marketing blasts, re-engagement campaigns - it counts against your limit. These are the sends that eat your tier.

Replies inside the customer service window don't. When a customer messages you first, a 24-hour window opens, and free-form replies inside it don't count. This is what makes WhatsApp different from email or SMS: conversation-driven, reactive support is essentially uncapped by the tier system. The limit only bites when you're the one reaching out cold. For a support team that's liberating. Marketing teams get the opposite deal, every proactive campaign draws from the same finite pool.

The practical implication: if your messaging mix leans toward answering customers who reach out, your effective capacity is far higher than your tier number. If it's mostly outbound, your tier number is your ceiling.

Broadcasts and the rolling window trap

Plenty of teams read "per day" and assume midnight reset. It doesn't. The window is a moving 24-hour period, so the message you sent at 11pm yesterday is still occupying a slot at 10am today.

That's a trap with broadcasts. Say you're on the 2,000 tier and schedule a 2,000-person broadcast for 9am. It goes out clean. At 2pm you decide to send a flash-sale follow-up to a different 500 people. Those 500 fail or queue, because you're still inside the 24-hour shadow of the morning send. Nothing's broken. You spent your whole window in one go.

The fix is boring but works: spread your sends. If you're near your ceiling, don't dump your entire capacity in one morning blast. Stagger campaigns so you aren't stranded for the rest of the day. Broadcast limits are your messaging tier seen through the lens of one big send, and teams that plan around the rolling window rarely hit a wall they didn't see coming.

There's a separate constraint too. Meta enforces a per-user limit on marketing template messages, a cap on how many marketing templates a single person receives so their inbox doesn't flood. The thresholds aren't published, but the effect is real: even with tier headroom, a specific customer may not get your marketing message if they've hit their personal limit. That's one reason broadcast reach sometimes comes in under what your tier alone suggests.

Checking your current limit

Two ways. In WhatsApp Manager, go to Account tools, then the Messaging limits panel - your current portfolio limit and scaling status are there. Through the API, query the WhatsApp Business Phone Number API and request the whatsapp_business_manager_messaging_limit field. For developers: the old messaging_limit_tier field is deprecated, so an integration still reading it needs updating. A typical response now returns something like TIER_250.

If you're wiring this into a dashboard, pull the field on a schedule, not once at setup. Tiers change, especially during automatic scaling, and stale capacity assumptions are how scheduled jobs start silently dropping messages.

One related detail: when the platform can't deliver a message it keeps retrying for a set time-to-live, 30 days for most messages and 10 minutes for authentication templates, then drops it. A successful API response only means your request was accepted, not that the message was delivered. You confirm delivery through the status webhook, not the send response. That's exactly why a capped broadcast can look fine in your dashboard while a chunk never arrives.

The mistakes that throttle accounts

Tiers are half the story. Meta's limits interact with quality and policy systems that can throttle or pause you regardless of tier. A few patterns that repeat.

Treating WhatsApp like an email list. Importing a cold list and blasting it is the fastest way to crater your quality rating. Email tolerates low engagement, WhatsApp punishes it. Blocks and spam reports directly suppress your ability to scale, and a bad enough rating gets templates paused.

Ignoring template quality before scaling. Teams rush to hit 2,000 delivered messages to unlock the next tier using whatever templates they have. If those templates are getting flagged, the volume does nothing because the quality review fails. Clean templates first, then scale.

Forgetting the portfolio is shared. A second number to "get around" a limit doesn't work, because the limit lives at the portfolio level. Teams burn a week setting up a parallel number only to find both were always drawing from the same 2,000.

Building campaign plans on a calendar-day assumption. If your scheduling logic assumes a midnight reset, you'll routinely overcommit morning capacity and underdeliver in the afternoon. Plan against the rolling window.

A platform that manages your sends intelligently helps, because it paces broadcasts against your real rolling capacity instead of dumping everything at once. Fufa's WhatsApp automation does exactly this, spreading business-initiated sends so you stay inside your tier instead of slamming into it. If your inbox is already live on Fufa, pacing broadcasts against your tier is the next workflow to configure.

Messaging limits aren't an obstacle to route around. They're a quality gate, and they reward the habits good marketing already runs on: message people who opted in, keep templates clean, build volume steadily instead of in panicked bursts. The teams that struggle treat WhatsApp like a cheaper SMS gun. The ones that do well treat the 250-to-2,000 climb as a short proving period, lean on the uncapped service window for support, and pace broadcasts against the real rolling window.

Verify the business first, then make sure you're using more than half your limit every week. And if Meta has ever reclassified one of your templates, that's the other place these rules bite.

FAQ

What's the messaging limit for a new account?

Every new business portfolio starts at 250 unique customers per rolling 24-hour period for business-initiated messages. It counts unique phone numbers, not total messages, so repeated messages to the same person count once. You raise it to 2,000 by verifying your business or sending 2,000 high-quality delivered messages within 30 days.

Does replying to customer messages count against my limit?

No. When a customer messages you first, a 24-hour customer service window opens, and free-form replies inside it don't count. The tier system only caps business-initiated messages like broadcasts and template campaigns. That's why support-heavy accounts handle far more volume than their tier suggests.

Why are my broadcasts failing even though I'm under my limit?

Usually the rolling 24-hour window. The limit doesn't reset at midnight, so messages sent the previous evening still occupy slots the next morning. Meta's separate per-user limit on marketing templates can also block delivery to specific customers who've already had their cap of marketing messages, even with tier capacity left.

How long does it take to increase limits?

The first jump from 250 to 2,000 depends on completing a scaling path - business verification or 2,000 quality messages over 30 days - then passing Meta's quality review. After 2,000, automatic scaling can bump you a tier within about six hours, but only if you send high-quality messages and have used at least half your current limit in the last 7 days. Idle accounts don't scale.

Are limits set per phone number or per account?

At the business portfolio level, shared across every number in it. Multiple numbers draw from one pool, so one heavy campaign consumes capacity the others need. A second number gives no extra total capacity. For more reach, raise the portfolio's tier.

What's the minimum to reach 2,000 quickly?

Do Meta Business Verification first. It's the fastest path and needs no send volume. If that's not available, send 2,000 delivered messages to unique customers over 30 days with high-quality templates. Either way, keep block and spam-report rates low, since Meta reviews quality before approving. Clean templates and an opted-in audience matter more than speed.