What it means
A messaging limit is WhatsApp's answer to the question "how much reach has this business earned?" It is expressed as a tier set on your business portfolio and shared by every business phone number in it, and it caps the number of unique customers you may deliver messages to outside an open customer service window in a moving 24-hour period. Until October 7, 2025 each number carried its own tier; Meta moved the limit to the portfolio on that date (Meta: messaging limit changes).
The unit is the part people get wrong. The limit does not count messages. It counts distinct recipients you initiated with. A support team that exchanges two hundred messages with forty customers has used forty. A marketing team that sends one template each to five thousand people has used five thousand. And a reply inside an open 24-hour customer service window does not count at all, because the customer opened that conversation.
That single design choice tells you what Meta is optimising for. Conversations people asked for are unconstrained. Interruptions are rationed, and the ration grows only as you prove that your interruptions are welcome.
The tiers, and how you climb them
A newly created business portfolio starts at 250, and the ladder above it is 2,000, 10,000, 100,000 and unlimited. Meta publishes the ladder and has adjusted it more than once (on October 7, 2025 the first step moved from 1,000 to 2,000), so treat the exact figures as current policy rather than as constants, and read the tier your portfolio is actually on from the API instead of assuming (Meta: messaging limits).
The first step, to 2,000, needs a scaling path. Every step after that is automatic:
- Business verification or proven volume. Verify your business portfolio, have the Meta partner that onboarded you verify it, or deliver 2,000 messages outside customer service windows to unique users within a moving 30 days using high-quality templates. Meta then reviews your message quality and approves or denies the move to 2,000.
- High-quality messages. Automatic scaling looks at message quality across all of your phone numbers and templates, and quality rating is evaluated continuously.
- Demonstrated volume. In the last 7 days you must have used at least half of your current limit. An idle portfolio never advances. When both conditions hold, the next level arrives within 6 hours.
Beyond verification there is no application, no form and no support ticket that accelerates this. It is the single most common planning failure we see: a team integrates two weeks before Black Friday, sits on the lowest tiers because nothing has been sent yet, and discovers on the day that reaching their list would take a fortnight. Warming a portfolio takes calendar time, so the integration has to go live long before the campaign that needs it.
Limit is not throughput, and neither is a spam block
Three different constraints produce three different errors, and each needs a different response. Confusing them is why teams "fix" a quality problem by adding retries.
Capacity is the tier: unique recipients per 24 hours, shared across the portfolio. You feel it as messages to new recipients outside open windows stop going out.
Throughput is requests per second. Cloud API provisions numbers at a default messages-per-second level and can raise it for high-volume senders. Exceed it and you get a standard rate-limit error, which genuinely is retryable with backoff.
Quality enforcement is neither. When previous messages have collected blocks and reports, sends can be refused outright with a spam rate-limit error. It looks like a rate limit and behaves like a penalty. Retrying it in a loop is the exact wrong response, because the sends that succeed keep feeding the problem that caused the restriction.
There is a fourth, narrower control worth knowing: a per-user frequency cap on marketing messages. Meta will decline to deliver an additional marketing message to an individual who has already received too many recently, and the send fails for that person while the rest of the batch goes out normally. It is a quiet cap, it is not something you can raise, and it means the correct strategy for a valuable contact is fewer, better marketing messages rather than more.
Why it matters
The messaging limit is the ceiling on what your channel can be worth. Every campaign forecast that assumes you can reach the whole list tomorrow is wrong unless you have checked the tier first, and every quality incident can stall the climb to the reach you were counting on.
The asymmetry has changed shape. Since October 7, 2025 Meta no longer downgrades a messaging limit because quality dropped, so a bad campaign does not take away reach you already have. What it takes away is the next step: automatic scaling needs high-quality messages across all of your numbers and templates, red templates are paused and then disabled (Meta: template pausing), and repeated policy violations still bring messaging restrictions (Meta: policy enforcement). That keeps the limit the clearest financial argument for careful list hygiene: it is not about avoiding a telling-off from Meta, it is about not freezing your reach for a quarter. Our guide to WhatsApp bulk messaging covers the opted-in routes that keep large sends inside the rules.
Real-world examples
- The launch that could not launch. A retailer with 60,000 opted-in contacts sat at the 2,000 tier because the portfolio had only been used for order notifications to a few hundred people a day, well under the half of its limit that automatic scaling asks for. Reaching the list at that tier would have taken a month. The fix was to ramp volume over the preceding quarter, not to send harder in December.
- The support desk that never notices. A SaaS company handles thousands of inbound conversations a week and has never come close to its tier, because inbound conversations do not consume it.
- The retry loop. An integration treated a spam rate-limit error as transient and retried every thirty seconds. Quality fell further, templates were paused, scaling stalled, and the stall was blamed on Meta rather than on the loop.
- The number that added no reach. A group with three brands runs three numbers in one business portfolio. Since October 7, 2025 they share a single limit, so the third number started with the portfolio's limit instead of at 250, and a busy brand can use up reach the other two were planning on. Capacity is now planned per portfolio, not per number.
Common mistakes
- Counting messages instead of unique recipients. Your capacity model is wrong from the start if you do.
- Planning a launch without reading the tier. It is one field on the phone number node. Read it before you promise a date.
- Retrying a spam rate-limit error. That error is a quality signal, not a transient failure.
- Adding numbers to dodge a cap. Since October 7, 2025 every number in a portfolio shares one limit, so a second number adds no capacity at all.
- Firing the whole batch at midnight. Spreading sends across the rolling window means capacity frees up as you go, and it also lands messages at humane local times.
- Ignoring the capability webhook. When the portfolio's limit changes, Meta sends
business_capability_updatewith the new value inmax_daily_conversations_per_business. Any scheduler that does not recalculate plans against a cap that no longer exists.
Related concepts
- Quality rating: the score that decides whether the tier can go up.
- 24-hour customer service window: conversations inside it do not consume the limit.
- Message template: the thing you spend the limit on.
- WABA: the account your numbers and templates sit in, inside the business portfolio that now holds the limit.
- Flood wait: Telegram's equivalent throttling signal, with very different mechanics.
- Drip campaign: pacing designed around a cap rather than against it.
How Pinlyx handles it
Pinlyx does not send WhatsApp campaigns, template messages or broadcasts, so it does not spend your messaging limit. It connects your WhatsApp number to a shared inbox where your team, or an AI agent running on your own OpenAI, Gemini or other provider key, answers the chats customers start, inside Meta's 24-hour window. Replies inside an open window do not count against the limit. See WhatsApp auto replies for how those replies are set up, and WhatsApp CRM for the inbox. WhatsApp is on paid plans, from Pro at $24.99 a month; the Free plan covers Telegram only. If you need opted-in sends at volume, compare tools in our list of the best WhatsApp CRMs.