WhatsApp messaging limits: how the tiers actually work

Messaging limits are the constraint people discover after building everything else. The number of unique customers you can start conversations with in a rolling day is capped, that cap starts low, and it rises only when Meta is satisfied with how your existing volume is being received.

It is a reputation system rather than a billing tier, which is why paying more does not raise it and why a campaign that annoys people can lower it.

What we'll cover

• What the limit actually counts
• The tiers
• Portfolio-level, not per number
• Building it with CodeWords
• Quality rating and what moves it
• How advancement works
• What stalls a tier upgrade
• Planning a launch around the limit
• Throughput, which is the other ceiling
• Making it survive
• Limits worth knowing about
• What to do first
• Frequently asked questions

What the limit actually counts

Unique customers you start a conversation with in a rolling 24-hour period, not total messages sent.

Replies within an open service window do not count against it, which is why a responsive support use case rarely hits the ceiling.

It is outbound-initiated messaging that consumes the allowance, which means marketing and notification use cases are the ones constrained.

Hitting it stops sends rather than queuing them silently, so an automation needs to handle the rejection.

It is separate from throughput, which is a different limit expressed in messages per second.

Understand which one you are hitting, since the remedies are unrelated.

The tiers

Limits progress through defined steps — commonly described as 250, 1,000, 10,000 and 100,000 unique customers per rolling day, with an unlimited tier beyond.

Everybody starts low, regardless of company size or spend.

The unlimited tier is not unconditional, since throughput limits still apply and quality still governs.

Meta's documentation is the authority on the current steps, which have changed and may change again.

Do not design assuming a tier you do not have, which is the most common planning error on this channel.

Verification matters. An unverified business is capped lower, and verification takes time you should start early.

Portfolio-level, not per number

A change worth knowing about, because it invalidates a common workaround.

Since October 2025 limits are shared across all WhatsApp numbers in one Meta Business Portfolio.

Adding numbers no longer adds capacity within the same portfolio, which was previously how people scaled around the constraint.

Plan capacity at portfolio level, and understand which numbers are drawing on the same allowance.

Separate portfolios have separate limits and separate verification, which is a real structure rather than a trick — and using it to evade limits is the sort of behaviour that attracts attention.

Check how your provider has structured things, since a Business Solution Provider may have made this decision on your behalf.

Budget the allowance between use cases, because marketing and transactional messaging now compete for the same pool.

Building it with CodeWords

CodeWords connects to more than 3,000 integrations, and the connection is made once and reused.

1. Open CodeWords and start a new automation.
2. Describe what should happen in plain language to Cody, the automation builder: which messages go out, to whom, and what happens when the limit is reached.
3. Authorize the connection to your WhatsApp Business Platform account.
4. Describe the exceptions: a limit reached, a template rejected, a quality rating drop, a customer who opted out.
5. Run it at low volume and watch the quality rating for a fortnight before increasing.

You describe the outcome; Cody builds it, connects it, and deploys it. The free plan covers light use, with Pro at $39 per month and Business at $100 per month as usage grows; details are on the pricing page.

Quality rating and what moves it

It is customer feedback, not delivery success. Blocks and spam reports are the primary inputs.

Three states — commonly shown as green, yellow and red — over a rolling recent window.

Blocks are the heaviest signal, and a single campaign to a poorly chosen audience can move the rating within a day.

Low engagement contributes, which means messages nobody responds to are not neutral.

It is per number and visible in your Business Manager, where you should be looking at it before a restriction tells you.

Recovery is possible and takes sustained better behaviour rather than an appeal.

How advancement works

Meta evaluates periodically, and advancement requires actually using a meaningful share of your current limit while maintaining quality.

Volume alone is not enough and neither is quality alone — you need both.

Sending nothing keeps you where you are, which surprises businesses waiting to be upgraded before launching.

Growth is stepwise, so plan for the step rather than a gradual ramp.

There is no purchase path. Spending more does not buy a higher tier.

Time is a component, so a launch that needs a high tier should start the climb well in advance.

What stalls a tier upgrade

A poor quality rating, which prevents advancement regardless of volume.

Not using enough of the current limit, which is the other half of the requirement.

Incomplete business verification, which caps you below where behaviour would otherwise take you.

Policy violations, which reset progress and can restrict the account.

An audience that blocks you, which is the underlying cause of most of the above.

Fix the audience before the volume, since pushing more messages to people who do not want them moves you backwards.

Planning a launch around the limit

Start the climb early, weeks before the campaign that needs the capacity.

Warm up with the messages people actually want — transactional, requested, expected — which build rating rather than risking it.

Segment by engagement, sending first to people most likely to respond well.

Stagger a large send across days rather than hitting the ceiling and failing.

Handle the rejection in your automation, with a queue and a retry, rather than losing the messages.

Have a fallback channel for anything that must arrive, since the limit is not yours to override.

Throughput, which is the other ceiling

The daily limit governs how many people you can reach; throughput governs how fast. Teams hitting one frequently believe they are hitting the other.

Throughput is messages per second, applied at the account level, and it is what a large simultaneous send runs into.

A burst fails differently from a daily cap — you see rate errors rather than a limit rejection, and retrying immediately makes it worse.

Pace the send rather than dispatching everything at once, which also looks less like bulk messaging.

Back off on the rate error with increasing delays, and never retry in a tight loop.

Media messages are heavier than text and consume more of whatever headroom you have.

Test at realistic volume before a launch, since a send that works for fifty recipients tells you nothing about five thousand.

Making it survive

Track your consumption against the limit continuously, not at the point of failure.

Alert before the ceiling, at a proportion of it, so somebody can decide rather than discover.

Watch the quality rating daily during any campaign, since the signal moves faster than the consequence.

Queue rather than drop when the limit is reached.

Report the outcome: conversations started, limit consumed, quality rating, and messages deferred.

Limits worth knowing about

Meta changes this, including the portfolio-level change in October 2025, so treat any specific figure as current rather than permanent.

Throughput and daily limits are different constraints with different remedies.

A provider cannot raise your tier, whatever the sales conversation implies.

Quality is opaque in its detail, and you see the rating rather than the calculation.

Limits do not fix targeting. A high tier used to message uninterested people is a faster route to a low rating.

What to do first

Find your current tier and your current quality rating in Business Manager, and check whether your numbers share a portfolio allowance. Most teams building on this channel do not know all three, and every capacity plan depends on them.

Two habits make the difference. Warm up with messages people asked for rather than with a campaign, since quality rating is built by wanted messages and damaged by unwanted ones at a rate that is hard to recover from. And alert on consumption before the ceiling rather than handling the rejection, because a send that fails at the limit is a customer who did not receive something you intended.

Frequently asked questions

What do WhatsApp messaging limits count?

Unique customers you start a conversation with in a rolling 24-hour window — not total messages. Replies inside an open service window do not count, so responsive support use cases rarely hit the ceiling.

What are the tiers?

Steps commonly described as 250, 1,000, 10,000 and 100,000 unique customers per rolling day, with an unlimited tier beyond. Everybody starts low regardless of company size, and Meta's documentation is the authority on current values.

Do more numbers give me more capacity?

Not within one Meta Business Portfolio. Since October 2025 limits are shared across all numbers in a portfolio, which invalidates the previous workaround of adding numbers to scale.

How do I move up a tier?

By using a meaningful share of your current limit while maintaining an acceptable quality rating. Both are required — sending nothing keeps you where you are, and volume with poor quality stalls advancement.

What moves the quality rating?

Blocks and spam reports primarily, with low engagement contributing. It is customer feedback rather than delivery success, and a single campaign to a poorly chosen audience can move it within a day.

Can I pay for a higher limit?

No. It is a reputation system rather than a billing tier, and no provider can raise it on your behalf whatever a sales conversation implies.

What happens when I hit the limit?

Sends are rejected rather than queued, so your automation needs to handle it — queue and retry rather than dropping the message, and alert before the ceiling rather than at it.

How should I plan a launch?

Start climbing weeks early, warm up with transactional and requested messages that build rating, segment by engagement, stagger large sends across days, and keep a fallback channel for anything that must arrive.

What is the difference between the daily limit and throughput?

The daily limit is how many unique customers you can start conversations with; throughput is how fast you can send, measured per second. They fail differently — a limit rejection versus rate errors — and the remedies are unrelated.

Why does a large send fail when a small one worked?

Usually throughput rather than the daily cap. Fifty recipients dispatched at once tells you nothing about five thousand, which is why pacing the send and backing off on rate errors matters before a launch rather than during one.

Related reading

• WhatsApp Business Platform vs unofficial APIs
• Why WhatsApp bots get banned
• The WhatsApp anti-ban playbook