Guides / Deliverability

WhatsApp messaging limits, and how tiers move

Your messaging limit is how many different people you may start a conversation with in a rolling 24 hours. It starts at 250 and rises on quality and usage, not on payment.

Checked against Meta’s published documentation on 15 August 2026.

In short

A new business portfolio starts at 250 unique recipients per rolling 24 hours. Verifying your business, or delivering 2,000 messages in a 30-day window with high-quality templates, moves you to 2,000. Above that the tiers rise automatically — 10K, 100K, unlimited — provided message quality stays high and you use at least half your current limit in seven days.

What the limit counts

The limit counts unique people you message first, outside an open customer service window, in a moving 24-hour period. It does not count replies inside an open window, and it does not count how many messages each person receives.

That distinction matters more than the number. A support team answering hundreds of inbound conversations a day never touches its limit; a marketing send to a fresh list of 300 people hits a 250 limit immediately.

The ladder

Meta publishes five tiers. The account screen shows which one a number is on, read from Meta rather than assumed.

  • 250 unique recipients / 24h — where every new business portfolio starts.
  • 2,000 — reached by business verification, partner-led verification, or by delivering 2,000 messages in a 30-day moving window using high-quality templates.
  • 10,000 — automatic, on quality and usage.
  • 100,000 — automatic, on the same two conditions.
  • Unlimited — the top of the ladder.
“Send 2,000 delivered messages outside of customer service windows to unique WhatsApp user phone numbers within a 30-day moving period, using templates with a high quality rating.”
Meta, Messaging limits — one of the three ways to reach 2,000

What moves you up, and what does not

Above 2,000 the progression is automatic, and it has exactly two conditions. Meta looks for high-quality messages across all your numbers and templates, and for actual use of the tier you are on — at least half of your current limit in the last seven days.

Nothing about the ladder is purchasable. No platform can raise your tier for you, and any vendor implying otherwise is selling you Meta’s own process.

“You are sending high-quality messages across all of your business phone numbers and templates, and in the last 7 days, your business has utilized at least half of your current messaging limit.”
Meta, Messaging limits — the automatic scaling conditions

Living inside the limit

Two things in the product bear on this directly. Sending is paced rather than dumped, so a large campaign spreads across the window instead of colliding with the rate ceiling, and each recipient carries its own status, so an audience that is failing shows up as failures rather than as silence.

The account screen shows the tier a number is on. As with quality rating, that figure is read from Meta when you look — nothing is polled or stored, and nothing will notify you when it changes.

Questions this raises

Does the limit cap how many messages I can send in total?

No. It caps how many distinct people you may start a conversation with in a rolling 24 hours. Replies inside an open customer service window do not count against it, which is why a busy support inbox and a small marketing list can look nothing alike at the same tier.

Can I pay to raise my tier?

No, and nobody can. The ladder moves on business verification and on Meta’s own quality and usage conditions. A platform can help you verify your business and can keep your quality high; it cannot buy you a tier.

Why did my tier drop?

Tiers move in both directions. Sustained quality problems bring a tier down the same way quality brings it up, and a number that stops being used can lose the tier its usage justified.

Does Messago tell me when my tier changes?

No. The tier is read from Meta when you open the account screen and is not stored or polled, so there is nothing to notify from. That is a deliberate limitation rather than an oversight — the product does not synthesise signals the API does not provide.

Talk to a person

Tell us what your team is dealing with.

We will walk your own use case through the product on a call. Pick a plan and your workspace is live as soon as payment clears, or book a demo and we will pick it up from there.