256 contacts per list, 250 recipients to start on the API, and five messaging tiers. Here is how WhatsApp's limits work and how to design around them.
If you are building customer notifications, reminders or campaigns on WhatsApp, the first thing that trips people up is the word "limit". There are two different systems with two different kinds of limit, and mixing them up leads to bad architecture decisions.
Two systems, two kinds of limit
WhatsApp Business App. This is the app a small business uses on a phone. Its traditional broadcast lists hold up to 256 contacts each. You can create many lists, but every recipient must have saved your number to receive the message.
WhatsApp Business Platform (the API). This is the infrastructure you integrate with. There are no lists here. Capacity is tier-based, which means it is measured in unique customers you can start conversations with in a rolling 24-hour window.
| Business App | Business API | |
|---|---|---|
| Limit model | Per list (256 contacts) | Per tier (unique recipients / 24h) |
| Automation | Limited | Through connected software |
| Consent | Required | Required |
| Templates | Not required for traditional broadcasts | Required for business-initiated messages outside the customer service window |
| Best for | Small, manual sending | Growing, integrated workflows |
A third option is Business Broadcasts, a newer feature inside the Business App. It is separate from traditional lists, and availability and commercial terms can vary by account.
The API messaging tiers
A newly created business portfolio starts at 250 unique recipients per rolling 24 hours. Eligible accounts can move up through these tiers:
| Tier | Unique customers / rolling 24h |
|---|---|
| Initial | 250 |
| Tier 2 | 2,000 |
| Tier 3 | 10,000 |
| Tier 4 | 100,000 |
| Final | Unlimited |
Three details matter when you design around this:
- The limit applies to the business portfolio. It is shared across eligible phone numbers in that portfolio. Sending from a second number does not give you fresh capacity.
- Tiers count unique customers, not messages. Messaging the same person ten times does not use ten units of capacity.
- A tier is not a throughput guarantee. It does not mean messages per second, and it does not guarantee delivery.
"Unlimited" does not mean unrestricted
Reaching the top tier removes the numeric cap. It does not remove consent requirements, template approval, quality controls or technical throughput limits. Treat it as headroom, not permission.
How accounts move up a tier
Meta assesses eligibility, and meeting a requirement does not guarantee an upgrade. The documented path looks like this:
- Complete business verification where your onboarding path requires it.
- Keep message quality high. Watch blocks, reports and template quality.
- One documented route to the 2,000 tier is delivering 2,000 qualifying template messages to unique users within a rolling 30 days.
- After 2,000, Meta can evaluate you for automatic increases. Two factors are quality across numbers and templates, and using at least 50% of your current limit in the previous seven days.
Why messages still get throttled
Even on a high tier,
Top comments (0)