WhatsApp messaging limits explained (portfolio tiers, not per number)
Why sending to 300 people stops working on a new WhatsApp Business account: messaging limits count unique customers per portfolio, not per message and not per number. Here is how the tiers actually work.
Why sending to 300 people stops working on a new WhatsApp Business account: messaging limits count unique customers per portfolio, not per message and not per number. Here is how the tiers actually work. In this deep dive, we explore actionable strategies, real-world engineering blueprints, and future-proof patterns to elevate your digital operations.
Most WhatsApp problems I get asked about start the same way: "we sent to about 300 people and half of them never arrived." There is usually no bug. There is a limit, and the reason it confuses teams is that they are guarding the wrong number.
I build BNex, a WhatsApp Business Platform product, so I live inside these rules every day. Everything below is Meta's model, not something specific to my tool, and it holds whether you run the platform directly or through any vendor.
What a messaging limit actually counts
A messaging limit is the maximum number of unique customers you can message outside a customer service window in a rolling 24 hours.
Three words in that sentence do all the work:
- Unique customers, not messages. Sending twenty updates to one person counts as one customer. A small list with lots of back and forth is cheap; a wide list with one message each is what burns the limit.
- Outside the window. The moment a customer messages you, a 24-hour service window opens and your ordinary replies inside it do not consume the limit at all.
- Rolling 24 hours. It does not reset at midnight. The window slides, so a burst yesterday afternoon still counts this morning.
That is why the same campaign can sail through one week and fail the next. It is not the campaign, it is the shape of the traffic around it.
The part most teams missed: limits are per portfolio now
Since late 2025 Meta sets the messaging limit at the business portfolio level, and it is shared by every business phone number in that portfolio. Adding a second or third number does not give you a second or third limit.
The practical consequence is blunt: if your portfolio sits at 10,000, that is 10,000 unique users a day across all your numbers combined, not 10,000 each. One busy number can eat the whole allowance by lunchtime.
This also means the field you may have integrated against is gone. The old messaging_limit_tier value on a phone number is deprecated; the current value is exposed as whatsapp_business_manager_messaging_limit, and it returns the portfolio's limit rather than the number's.
The tiers, and how a portfolio moves up
A newly created business portfolio starts at 250 unique customers per 24 hours. From there the levels climb in steps:
- 2,000 by completing business verification, or by completing the scaling path Meta offers for a portfolio that has not verified yet.
- 10,000, then 100,000, then Unlimited through automatic scaling.
Automatic scaling is not a queue you join. Meta looks at two things: how much of your current limit you actually used over the previous week, and your quality rating (how often customers block or report you). Volume plus good quality moves you up a level; volume plus complaints can move you back down.
One warning from experience: the exact numbers at each step have changed more than once. The first step was 1,000 for a long stretch and is 2,000 for portfolios created under the newer rules. Do not plan against a blog post, including this one. Open WhatsApp Manager, go to Account tools > Messaging limits, and read your own current value. That panel is the only number that matters for your account.
The per-number quota that reads like a limit
Since 1 October 2026 there is a second quota in play, and it is the one that gets mistaken for a messaging limit.
Meta now bills service messages: the ordinary replies you send inside the 24-hour customer service window. Each business phone number gets the first 1,000 service messages per month free, and anything past that is charged per message. The unused portion does not roll over; it resets each month, per number.
Two things make this easy to misread:
- It is per business phone number, not per portfolio. Reach limits are shared, this free allowance is not.
- It covers service messages only. Utility, marketing and authentication templates are billed on their own rules and are not counted against the 1,000.
So the two quotas live at different levels, and mixing them up is why a team will swear their limit is 1,000 when their actual reach is 250, or the reverse. The pricing guide walks through how per-message billing interacts with the free allowance, and the template rejection guide covers what happens to the messages you were told not to send.
A worked example
An ecommerce team on a portfolio at 2,000 sends a restock alert to 1,500 customers at 9am, then a courier-delay notice to another 900 at 2pm.
- The 9am send consumes 1,500 of the 2,000.
- The 2pm send has only 500 left. Roughly 400 recipients silently get nothing, even though the API returns success for the messages that fit.
No error, no warning on the send screen. The fix is either to spread the sends across the day or to raise the limit. It is not to add another phone number, which changes nothing under the portfolio model.
What to actually do
- Verify the business early. Verification is the documented route from the starting tier to 2,000, and it unlocks the rest of the scaling path. It also cannot be rushed later when a campaign is already scheduled.
- Protect quality rating. The limit is not only about volume. A high block rate holds you at a tier just as firmly as low volume does.
- Track the window per contact. Teams that cannot see who is inside a 24-hour window send templates they did not need, burning limit and money on messages that could have been free.
- Check the real value, not the remembered one. Limits at the portfolio level, the free service allowance at the number level. Confirm both in WhatsApp Manager before a big send.
If you are just starting out and have not been through the access process yet, the onboarding guide covers verification and the first review Meta runs on a new account.
Where BNex fits
BNex is the WhatsApp Business Platform product I build. It shows the messaging limit your portfolio is on, tracks the service window per contact so you are not wasting allowance, and reports how much of the daily reach you have left before a send goes out rather than after. The rules above are Meta's and apply to everyone; the job of a tool is to make them visible before they cost you a delivery.
If you have hit the 250 wall or watched a send quietly under-deliver, message me on WhatsApp at +91 73587 22745 with roughly how many people you message a day, and I will tell you whether the answer is verification, better pacing, or a different send strategy altogether.
Related Reading
Get more insights like this
Join our list for practical automation, web engineering, and growth strategy — written by builders, for builders.
Manikandan S
Founder & Technical Lead at ZiyncFounder and technical lead at Ziync. I build high-performance websites and web applications for startups and mid-market teams: React, Next.js, Firebase. Based in Chennai, working with clients worldwide.