WhatsApp Messaging Limits: How the Tiers Work and What Your Code Should Watch

This article was checked by the WABB team against Meta's "Messaging Limits" and "Send messages" pages, read on 10 November 2026.

A new WhatsApp Business Platform setup can reach 250 people a day with messages it starts, and not one more. The limit is not a rate limit on requests; it counts people. It also moves up and down on its own, and your code only finds out if it listens. This post covers what the limit counts, how it rises, what message quality has to do with it, and which API field and webhooks report it. Where we add our own advice, we say so.

The short version

• The limit is the number of unique WhatsApp user phone numbers your business can deliver messages to, outside a customer service window, in a moving 24 hours.
• It belongs to the business portfolio, not to a phone number. All numbers in the portfolio share it.
• New portfolios start at 250. The ladder is 250, 2,000, 10,000, 100,000, unlimited.
• The first step (to 2,000) needs verification or 2,000 delivered messages. After that, steps are automatic.
• Message quality, judged from how people react over the past seven days, decides whether you move up.
• Read the limit from the whatsapp_business_manager_messaging_limit field. The old messaging_limit_tier field is deprecated.

What the limit counts

Figure 1. What the messaging limit counts.

Meta defines messaging limits as the maximum number of unique user phone numbers your business can deliver messages to, outside of a customer service window, within a moving 24-hour period. Three consequences follow.

• People, not messages. Sending one person ten templates in a day uses one slot. Sending ten people one template each uses ten.
• Conversations that the customer started are outside it. The limit applies to messages sent outside a customer service window. A reply inside the window does not count against it.
• The portfolio shares it. Limits are calculated and set at the business portfolio level and shared by all business phone numbers in it. Meta notes that one number can use up the whole portfolio's capacity in a period. Our suggestion: if you run a high-volume campaign number and a support number in one portfolio, watch the campaign number's volume, because support is the one that suffers.

Source: Meta for Developers, "Messaging Limits", checked 10 November 2026. Related guide on WABB: WhatsApp Business Broadcast: Lists, Limits & Cost.

How a limit goes up

Figure 2. The ladder and the rules for each step.

A newly created business portfolio has a limit of 250. It can rise to 2,000 by completing a scaling path, then to 10,000, 100,000 and unlimited through automatic scaling.

The first step, to 2,000. Complete one of three scaling paths:

1. Verify your business.
2. Have your partner verify it, if a partner onboarded you.
3. Send 2,000 delivered messages outside customer service windows to unique users within a 30-day moving period, using templates with a high quality rating.

After you finish a path, Meta analyses your message quality and approves or denies automatic scaling. If approved, the limit becomes 2,000 immediately, and you get an email and a developer alert.

The steps after that. Meta moves you up one level, within 6 hours, if both of these are true:

• you are sending high-quality messages across all your numbers and templates, and
• in the last 7 days you used at least half of your current limit.

The second rule matters for planning. A limit you never approach does not grow. Our suggestion: if you expect a bigger campaign next month, send steadily at more than half the current limit in the weeks before it, instead of expecting the limit to rise on the day.

Source: Meta for Developers, "Messaging Limits", checked 10 November 2026. Related guide on WABB: WhatsApp Business API Requirements: What to Prepare First.

Where quality comes in

Quality is the gate for every step above. Meta says WhatsApp determines message quality from how users have received your messages over the past seven days, weighted by recency. The score uses feedback signals such as blocks, reports, mutes and archives, and the reasons people give when they block you.

Meta's list of guidelines for high-quality messages is short:

• follow the WhatsApp Business Messaging Policy;
• send only to people who opted in;
• make messages personalised and useful;
• avoid open-ended welcome or introductory messages;
• avoid sending too many messages a day;
• optimise content and length.

Meta also says numbers with high traffic commonly see quality change within short intervals, even within minutes. The practical reading: a weekly look at the dashboard is too slow for a high-volume number. If you want to know how to collect and store the opt-in these rules assume, we covered it in an earlier post on what Meta requires and what to store.

Source: Meta for Developers, "Send messages" (section "Message quality"), checked 10 November 2026. Related guide on WABB: WhatsApp Coexistence: Use the Business App and API on One Number.

What your code can read

Figure 3. The three places the limit shows up.

The API field. Request whatsapp_business_manager_messaging_limit on the business phone number object. Meta's example response is "whatsapp_business_manager_messaging_limit": "TIER_250". The earlier messaging_limit_tier field is deprecated. You can also see the limit in WhatsApp Manager, under Account tools → Messaging limits.

business_capability_update. This webhook fires when a capability such as the messaging limit is increased or decreased. The value in max_daily_conversations_per_business is one of TIER_250, TIER_2K, TIER_10K, TIER_100K or TIER_UNLIMITED. Meta marked the older max_daily_conversation_per_phone field, which used numbers and -1 for unlimited, for removal in February 2026, so build against the new one.

account_alerts. If a limit increase is denied, deferred or needs more information, this webhook carries alert_type and alert_description. Meta lists three types: INCREASED_CAPABILITIES_ELIGIBILITY_DEFERRED, INCREASED_CAPABILITIES_ELIGIBILITY_FAILED and INCREASED_CAPABILITIES_ELIGIBILITY_NEED_MORE_INFO. The descriptions include "Your messaging quality was too low to unlock more capabilities at this time" and a request for additional business verification.

Source: Meta for Developers, "business_capability_update" webhook reference and "account_alerts" webhook reference, checked 10 November 2026. Related guide on WABB: WhatsApp New Features for Business.

What to handle in code

Meta does not prescribe how to structure this. These are our suggestions, built on the behaviour above.

1. Store the current tier per portfolio, updated from business_capability_update, and compare it with the day's unique recipients before you start a campaign.
2. Count unique recipients, not sends, for messages outside customer service windows. That is the number the limit uses.
3. Subscribe to account_alerts and route denials to a person. The alert text tells them whether the next step is verification or higher quality.
4. Watch for a drop. business_capability_update fires on decreases as well as increases. Treat a lower tier as an incident, not a log line.
5. Pace campaigns. Spread large sends so a burst does not use the whole day's allowance on one number, and so quality signals have time to arrive.
6. Keep opted-in lists clean. Blocks and reports are what Meta measures; a list of people who never asked is the fastest way to lose a tier.

Checklist

• You read the limit from whatsapp_business_manager_messaging_limit, not from the deprecated field
• Both business_capability_update and account_alerts are subscribed
• Campaign size is checked against unique recipients in the last 24 hours, across all numbers in the portfolio
• Business verification is done, or you know when you will reach 2,000 delivered messages
• Someone owns the alert when the tier drops

FAQ

Is the limit per phone number? No. Meta says it is set at the business portfolio level and shared by all numbers in it.

Do replies to customers count? The limit applies to messages sent outside a customer service window, so replies inside the window are outside it.

Do I have to ask Meta to raise the limit after 2,000? Meta says increases after that can happen automatically, when quality is high and you used at least half the current limit in the last 7 days.

Does this page give prices? No. The page is about limits. Pricing is on a separate Meta page.

Where can I read more on the WABB side? See the broadcast guide, the API prerequisites and the comparison of the Business app and the API.

We build tools for WhatsApp messaging at WABB. This post uses only Meta's public documentation. For a business-side view of the same setup, see our guide to WhatsApp customer support automation.