Glossary

What is a Messaging Limit?

Free forever plan · No credit card required · Cancel anytime

Quick definition

A messaging limit is the cap on how many unique WhatsApp users a business can deliver messages to outside an open customer service window in a moving 24-hour period. Since October 7, 2025 Meta sets it per business portfolio and shares it across all of the portfolio's phone numbers, in steps of 250, 2,000, 10,000, 100,000 and unlimited, and a falling quality rating no longer lowers it.

In a single sentence: it counts people you reach outside an open service window, not messages you send.

What changed in 2025-2026
  • October 7, 2025. Messaging limits moved from each phone number to the business portfolio. Every number in the portfolio shares one limit, existing portfolios took the highest limit any of their numbers had, and a newly registered number gets the portfolio's limit immediately (Meta: messaging limit changes).
  • October 7, 2025. The first step above 250 became 2,000 instead of 1,000, so the ladder is now 250, 2,000, 10,000, 100,000 and unlimited, and automatic increases land within 6 hours instead of 24 (Meta: messaging limits).
  • October 7, 2025. The Flagged phone number state was retired, and a drop in quality rating no longer downgrades a messaging limit (Meta: messaging limit changes).
  • February 2026. The per-phone webhook fields max_daily_conversation_per_phone and current_limit were due to be removed, according to Meta's reference pages. Read the portfolio limit from max_daily_conversations_per_business, and request whatsapp_business_manager_messaging_limit instead of the deprecated messaging_limit_tier field (Meta: business_capability_update).

Last updated: . Every rule on this page was checked against Meta's developer documentation that day.

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:

  1. 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.
  2. High-quality messages. Automatic scaling looks at message quality across all of your phone numbers and templates, and quality rating is evaluated continuously.
  3. 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

  1. 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.
  2. 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.
  3. 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.
  4. 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_update with the new value in max_daily_conversations_per_business. Any scheduler that does not recalculate plans against a cap that no longer exists.
  • 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.

Cheat sheet · the tier ladder

Five steps, from 250 to unlimited.

Tier names are the values Meta returns in max_daily_conversations_per_business and the whatsapp_business_manager_messaging_limit field, set per business portfolio. Meta adjusts the ladder, so read the live value rather than trusting a number you memorised. Source: Meta, Messaging limits, checked November 5, 2026.

TierWhat it allowsHow you get there
TIER_250Deliver to up to 250 unique users per moving 24 hours outside service windows. Where every new business portfolio starts.The default for a newly created business portfolio. A newly registered number shares its portfolio's limit from the start.
TIER_2KUp to 2,000 unique users per moving 24 hours.One of three scaling paths: verify the business, have the Meta partner that onboarded you verify it, or deliver 2,000 messages outside service windows to unique users within 30 days using high-quality templates. Meta then reviews your message quality.
TIER_10KUp to 10,000 unique users per moving 24 hours.Automatic scaling: high-quality messages across all of your numbers and templates, and at least half of the current limit used in the last 7 days. The step lands within 6 hours.
TIER_100KUp to 100,000 unique users per moving 24 hours.Automatic scaling again, one level at a time. The tier where most large senders operate comfortably.
TIER_UNLIMITEDNo cap on unique recipients. Throughput, not the limit, becomes the constraint.Automatic scaling from 100,000, under the same quality and usage conditions.
Four errors that all look like rate limits

Only one of them should be retried right away.

CodeWhat it really meansCorrect response
130429API throughput rate limit. You are calling the endpoint faster than the number is provisioned to accept.Back off and retry with jitter. This is about requests per second, not about unique recipients.
131048Spam rate limit hit. Sending is restricted because previous messages were blocked or flagged.Stop the campaign. This is a quality problem wearing a rate-limit costume, and retrying makes it worse.
131049Meta declined to deliver this marketing message to protect ecosystem engagement, a per-user frequency cap.Not retryable for this user right now. Reduce marketing frequency per contact and prioritise what matters.
131056Pair rate limit: too many messages between this business number and this one recipient in a short period.Almost always a loop in your own automation. Deduplicate before you retry anything.
Planning a campaign against the tier

Read the capacity, then size the batch.

# A limit change arrives as a webhook (Meta also emails you).
# The limit belongs to the business portfolio, not to one number.
{
  "field": "business_capability_update",
  "value": {
    "max_daily_conversations_per_business": 2000
  }
}

// Capacity planning, in plain terms. Meta's reference lists tier
// names (TIER_2K) and its payload example shows a number (2000),
// so normalise both before you plan.
const TIER_CAPACITY = {
  TIER_250: 250, TIER_2K: 2000, TIER_10K: 10000,
  TIER_100K: 100000, TIER_UNLIMITED: Infinity,
};
const capOf = (v) => (typeof v === 'number' ? v : TIER_CAPACITY[v]);

function plan(campaign, portfolio) {
  const cap = capOf(portfolio.messagingLimit);
  // Unique users reached outside service windows in the last 24h,
  // across EVERY number in the portfolio. Not messages sent.
  const spent = uniqueOutsideWindowSince(portfolio, Date.now() - 86400e3);
  const room  = cap - spent;

  if (campaign.audience.length <= room) return sendAll(campaign);

  // Split across days instead of collecting restricted errors.
  return schedule(campaign, { perDay: Math.floor(room * 0.9) });
}

// Retry policy, by error class
const RETRYABLE = new Set([130429]);          // throughput only
const STOP_CAMPAIGN = new Set([131048]);      // quality enforcement
const SKIP_CONTACT = new Set([131049, 131056]); // per-user caps
Scaling checklist

Six rules for growing capacity without losing it.

  • Complete business verification before you need the reach, not during the campaign.
  • Go live with the number weeks early, so real volume accumulates before the big send.
  • Read the current tier from the API at plan time and size the audience against it.
  • Pace sends across the rolling window rather than firing everything at once.
  • Classify every send error: retry throughput, stop on quality, skip per-user caps.
  • Plan capacity per business portfolio: a second number shares the same limit rather than adding to it.

Messaging limits: FAQ

Capacity questions that decide whether a campaign can actually ship.

Unique WhatsApp users your business delivers messages to outside an open customer service window in a moving 24-hour period, counted across every phone number in your business portfolio, not messages. Sending forty messages to one person costs you one against the limit. Sending one message each to forty people costs forty. Replies inside an open customer service window do not consume it either, because the customer started that conversation, not you. This is why a support-heavy number rarely notices its tier while a broadcast-heavy number hits the ceiling constantly.
The first step, from 250 to 2,000, takes one of three scaling paths: verify your business, 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 step. After that Meta scales automatically, one level at a time and within 6 hours, once two conditions hold: you send high-quality messages across all of your phone numbers and templates, and you used at least half of your current limit in the last 7 days. No support ticket speeds it up. Practically it means you cannot jump straight to a big launch: you have to build volume through the tiers first, which is why an integration should go live weeks before the campaign that needs it.
Messages to additional unique users outside open service windows stop going out for the rest of the moving period, while replies inside open windows keep working normally. Nothing is permanently damaged, and capacity returns as the oldest conversations age out of the 24-hour window, so a queue that spreads sends across the day rather than firing them all at once will often never notice the cap at all.
No, and confusing them sends people down the wrong debugging path. The messaging limit is about how many unique people per day. Throughput is about how many API calls per second the number will accept, which Cloud API provisions at a default level and can raise for high-volume senders. A 130429 error is a throughput problem, solved by pacing and retries. Hitting the tier is a capacity problem, solved by verification, quality and time.
Per business portfolio, since October 7, 2025. Before that date each phone number carried its own tier. Now Meta sets one limit on the business portfolio and every number in it shares that limit, so one busy number can use up the whole portfolio's reach for the period. Existing portfolios were set to the highest limit any of their numbers had, and a newly registered number gets the portfolio's limit immediately. Adding a second number therefore no longer adds capacity, and spinning up numbers to get around a cap gains nothing.
Not because of quality any more. Until October 7, 2025, a number that stayed flagged for low quality for 7 days dropped one level. Since that date the Flagged state no longer exists and Meta does not downgrade a messaging limit when quality drops. Low quality still costs you: automatic scaling needs high-quality messages, red templates are paused and then disabled, and repeated policy violations can bring messaging restrictions under Meta's policy enforcement. The cost of a bad campaign is now a stalled climb rather than a lost tier.

Ready to ship

Answer WhatsApp chats inside the window.

Pinlyx puts WhatsApp in one shared inbox with Telegram, Instagram and email, where your team or an AI agent replies inside Meta's 24-hour window. Those replies never count against your messaging limit.

WhatsApp is on Pro, $24.99/month · Replies inside Meta's 24-hour window · Free plan covers Telegram only

We value your privacy

We use cookies to improve our site, analyze traffic, and personalize ads. You can accept all, reject non-essential, or customize your choices. Read our Cookie Policy.