---
title: "WhatsApp Business Message Limits and Tiers, Explained"
slug: whatsapp-business-message-limits-and-tiers
author: "Leonardo Maldonado"
category: "Safety & Platform Limits"
articleType: how-to-guide
tags: ["WhatsApp messaging limit 250","WhatsApp business portfolio messaging limit"]
publishedAt: 2026-10-25T09:00:00.000Z
updatedAt: 2026-10-25T09:00:00.000Z
canonical: https://setluca.com/blog/whatsapp-business-message-limits-and-tiers
---# WhatsApp Business Message Limits and Tiers, Explained

> WhatsApp Business message limits and tiers cap how many different people your business can start a conversation with in a rolling 24 hours. New portfolios begin at 250. The limit belongs to your whole business portfolio, not to one phone number, and replies you send inside an open 24-hour window don't count against it at all. Most coaches never touch the ceiling.

## Key takeaways

- The limit counts unique WhatsApp numbers you message outside a customer service window in a moving 24-hour period. Replies to inbound messages don't count toward it, and the first 1,000 a month per number are free.
- Limits sit at the business portfolio level and are shared by every phone number inside it. A second number does not buy a second allowance.
- Meta's current documentation names two figures plainly: a starting limit of 250 and a next level of 2,000. Meta describes everything above those as one-level increases, not a published ladder.
- Automatic scaling needs two things at once: high-quality messages across all your numbers and templates, and use of at least half your current limit in the last 7 days.
- Throughput and per-person pacing are separate limits. You will usually hit those, or template review, long before you hit 250.

---

## What are WhatsApp Business message limits and tiers?

WhatsApp Business message limits cap reach rather than volume. Meta's definition is precise. The limit is "the maximum number of unique WhatsApp user phone numbers your business can deliver messages to, outside of a customer service window, within a moving 24-hour period."

Read that twice, because three words in it do all the work. _Unique_ means the same person messaged nine times counts once. _Outside_ means a reply to someone who just wrote to you doesn't count. And _moving_ means there is no midnight reset. The clock rolls forward all day, and yesterday's recipients age out one by one.

### Is the limit per phone number or per portfolio?

Per portfolio, and this is the part that surprises people. Meta states that limits "are calculated and set at the business portfolio level and are shared by all business phone numbers within a portfolio." Older guides describe the limit as a property of a phone number. It isn't. Register a second number for a second offer and both numbers draw from the same daily pool.

All of this covers the WhatsApp Business Platform, the API product, and nothing else. The WhatsApp Business app on your phone has its own separate constraints, which the [WhatsApp Business setup guide for coaches](/blog/whatsapp-business-setup-for-coaches) walks through. Every third-party setter that sends through the Platform, the kind weighed up in this [Appointwise review](/blog/appointwise-review), sends inside these same limits, because the allowance belongs to your portfolio rather than to the software.

## What counts against your messaging limit?

Business-initiated contact counts. Customer-initiated conversation does not.

When someone messages you, a 24-hour customer service window opens. Everything you send inside it is free-form and invisible to your messaging limit. Since October 1, 2026, Meta charges for service messages after the first 1,000 per number each month (WhatsApp Business FAQ). Once that window closes you can only send an approved template, and that send eats one of your unique-recipient slots for the next 24 hours. The [WhatsApp 24-hour rule](/blog/whatsapp-24-hour-window) breakdown walks through the mechanics of that clock in full.

| What you send | Counts toward the limit? | Charged? |
| --- | --- | --- |
| Free-form reply inside an open window | No | No |
| Utility template inside an open window | No | No |
| Utility or marketing template outside any window | Yes | Yes |
| Any message inside a free entry point window (up to 7 days) | No | No |
| A second, third or ninth template to the same person that day | No (same unique number) | Yes, each time |

Source: Meta for Developers, messaging limits and pricing documentation, retrieved September 25, 2026.

### Your limit and your bill are separate meters

Your recipient count and your invoice move independently now, and older writing gets this wrong. Meta's pricing page says conversation-based pricing "was replaced with per-message pricing on July 1, 2025." So you can sit under 250 recipients and still run a real bill, because Meta prices every individual template you send.

## What are the actual tiers?

Meta's own page names two numbers and stops. A new business portfolio starts at 250. The first documented increase takes it to 2,000. Beyond that, the page describes further increases as one-level steps granted by automatic scaling, without publishing what those levels are.

| Level | Unique recipients per rolling 24 hours | How you get there |
| --- | --- | --- |
| Starting limit | 250 | Register a business phone number under an approved display name |
| Next documented level | 2,000 | Complete a scaling path, or deliver 2,000 messages outside customer service windows to unique numbers using high-quality templates within 30 days |
| Higher levels | Not enumerated in current docs | Automatic scaling raises the portfolio "by one level within 6 hours" when the criteria are met |

Source: Meta for Developers, "Messaging Limits," retrieved September 25, 2026.

If you have read a post listing a neat ladder of 250, 1K, 10K, 100K and unlimited, treat it as history. Meta's current page does not print those figures, and a number with no live home does not belong in your planning.

### Where do you find your own current limit?

Read your limit rather than infer it. WhatsApp Manager inside Meta Business Suite shows the figure set for your portfolio, and the API returns it on the `whatsapp_business_manager_messaging_limit` field.

## How do you move up a tier?

You earn it by sending well and sending enough. Meta lists two criteria, and both have to hold at the same time:

- "You are sending high-quality messages across all of your business phone numbers and templates"
- "In the last 7 days, your business has utilized at least half of your current messaging limit"

Meet both, and the portfolio's limit rises "by one level within 6 hours."

The second criterion is the one coaches miss. At a 250 limit, half is 125 unique business-initiated recipients a day, sustained for a week. Almost no coaching pipeline does that, and there is nothing wrong with that. You simply stay at 250 indefinitely, which is a fine place to live.

When Meta declines a requested increase, it fires an `account_alerts` webhook. The `alert_type` and `alert_description` fields on it name the alternate route open to you. When a limit does change, a `business_capability_update` webhook reports the new figure. Wire both into wherever you actually read notifications. A limit change nobody sees surfaces later as a mystery delivery failure.

## Does your coaching business actually need a higher tier?

Almost certainly not, and the honest answer is worth more to you than an upgrade guide.

### Work out your real daily number first

Count the people you have to message _first_ on a given day:

- booked-call reminders where the lead last wrote to you more than a day ago
- rescue touches to leads who went quiet
- any list send

That total is what the limit governs. Everything else in your inbox is reply traffic. It doesn't count toward the limit, and the first 1,000 service messages a month per number are free. Most of that traffic starts somewhere other than WhatsApp (an ad, a story, an [Instagram call to action to drive DMs](/blog/instagram-call-to-action-to-drive-dms)) and none of it touches your allowance once the person has written to you first.

**Stay at 250 if** your business-initiated sends run under about a hundred a day and your list sends are smaller than your limit. **Pursue 2,000 if** you run a genuine broadcast motion. That means a launch list of several hundred opted-in past clients, messaged on the same afternoon, month after month. **Do neither and split the send** if you cross the line twice a year at launch time. Two afternoons cost you nothing. A forced volume push to trigger scaling costs you quality.

### Where a human setter still beats the software

There is a real limit to what any [WhatsApp AI appointment setter](/blog/whatsapp-ai-appointment-setter) fixes here. It can pace sends, respect windows and hold a queue. The judgment call about whether a quiet lead deserves a paid marketing template is yours. A good human setter reads a thread, decides that this person is grieving or simply done, and sends nothing. Software defaults to sending. That is why Luca's rescue cadence stops rather than continuing. If a paid marketing template worries you, approve each one yourself before it goes out.

## What does 250 a day look like in a real coaching pipeline?

Take Marisol, an illustrative nutrition coach running click-to-WhatsApp ads at a modest daily budget. Her numbers, worked through:

- **40 new inbound conversations a week.** Every one opens a customer service window. Her setter answers inside it, qualifies, and offers a slot. Limit consumed: zero.
- **11 calls booked a week.** Each gets a reminder the day before. Roughly seven of those leads have gone quiet long enough that the window closed, so seven reminders a week go out as templates. That's one a day.
- **18 leads go quiet.** Each gets up to three business-initiated touches over ten days. About 54 template sends per ten-day cycle, so five or six unique recipients a day.
- **Typical day: 7 unique recipients** against a limit of 250. She is using under 3% of the starting tier.
- **Launch day: she messages 140 opted-in past clients** with one marketing template in an afternoon. Add the day's usual seven and she lands at 147. Still clear.

### Where Marisol's ceiling actually shows up

Marisol's ceiling only becomes real when her past-client list passes about 240 people, and splitting that send across two afternoons dissolves it. She will never hit the 125-a-day average automatic scaling wants, so she will never be offered a level up. Nothing about her business is broken. The arithmetic that does hurt her sits on the cost meter: 140 marketing templates is 140 charged messages, whatever her tier says.

## Which limit will stop you first?

Throughput and per-person pacing will stop you first, nearly always. These are separate systems from the daily recipient cap, and they bite at completely different scales.

### How fast can you send, and how fast to one person?

Meta's Cloud API documentation says numbers send "up to 80 messages per second (mps) by default," with automatic upgrades to as much as 1,000 mps. Exceed your current allowance and the API returns error 130429. During an upgrade, error 131057 appears and the number goes quiet for roughly a minute.

The one that catches conversational tools is the pair rate limit. You may send one message every six seconds to the same WhatsApp user, with a burst allowance of up to 45 messages inside six seconds. Go past it and you get error 131056. A setter that fires a greeting, a question and a calendar link in one instant trips this long before it nears a tier ceiling.

### Template review is the third gate

Submit early, because review is not instant. A template sits at `PENDING` until Meta marks it `APPROVED` or `REJECTED`, so build your rescue cadence a week before you need it. The same principle applies across every Meta surface, which is why the [Meta business messaging automation policy](/blog/what-meta-allows-for-dm-automation) rewards patience over cleverness.

## What does hitting a limit look like?

It happens quietly, and you notice from the wrong end. Nobody gets a banner saying "you are out of recipients."

Your inbound conversations keep working perfectly. Replies inside open windows send, arrive and read normally, because they never counted in the first place. What stops is business-initiated contact to people you haven't reached yet today. Reminders fail. The rescue cadence stalls. A list send lands for the first several hundred people, then goes silent. If your tooling logs errors where you don't look, the first sign is a coach wondering why nobody confirmed tomorrow's calls.

A quality slide looks different again. Sends still succeed. Then Meta starts rejecting your templates on submission. A scaling request comes back declined with an `account_alerts` payload explaining why, and delivery quietly worsens. The pattern mirrors the other Meta surfaces, where the warning signs run days ahead of the penalty. It is the same slow slide covered in [how to avoid getting banned on Instagram](/blog/how-to-avoid-getting-banned-on-instagram).

## How do you get your limit back?

### The five-rung failure and recovery ladder

1. **Recipient cap reached.** Business-initiated sends to new unique numbers fail for the rest of the moving 24-hour period. Meta doesn't punish you for it, and capacity returns as yesterday's recipients age out, so sends resume on their own. Stop retrying and let the clock move.
2. **Throughput or pacing errors.** Errors 130429 and 131056 mean your sender is going too fast, not that you did something wrong. Queue the messages, add spacing between sends to the same person, retry.
3. **Quality decline.** Meta starts rejecting your templates, or it declines your scaling request. Pause the cadence that drew negative feedback. Read the `account_alerts` description. Rewrite or delete the offending template rather than resubmitting it with the punctuation changed.
4. **Policy enforcement.** Meta's messaging policy is direct: "We may limit or remove your access to or use of the WhatsApp Business Services if you receive significant amounts of negative feedback, cause harm to WhatsApp or our users, violate or encourage others to violate our terms or policies." Recovery here means stopping all business-initiated sending for several days, auditing your opt-in evidence, and appealing with that evidence attached.
5. **Termination.** The policy warns that after a termination for violations, "we may prohibit you and your organization from all future use of WhatsApp products and services." There is no reliable route back from this rung. Everything above it exists to keep you off it.

### What recovery actually looks like

The way back from rungs one through three is always the same shape. Stop sending. Find the template or cadence responsible, fix that one thing, then resume at a fraction of your old volume for a week. Resuming at full speed the moment sends work again is what turns a bad week into a locked account. The same instinct does the same damage when [recovering from an Instagram shadowban](/blog/how-to-recover-from-instagram-shadowban).

## Troubleshooting: symptom, cause, fix

| Symptom | Likely cause | Fix |
| --- | --- | --- |
| Reminders stop sending mid-afternoon, replies still work | Daily unique-recipient cap reached | Wait for the rolling window to advance; move reminders earlier in the day so they queue first |
| A second phone number sends far less than expected | Both numbers share one portfolio limit | Plan sends across the portfolio, not per number |
| Error 131056 on a multi-message greeting | Pair rate limit: one message per six seconds to the same person | Space messages to a single recipient; use one longer message instead of three short ones |
| Error 130429 during a list send | Throughput allowance exceeded | Queue and pace the send; the automatic upgrade path raises throughput over time |
| Scaling request declined with no obvious reason | Quality across numbers and templates, or under-use of the current limit | Read the `account_alerts` description; fix quality first, volume second |
| Template stuck at `PENDING` on the day you need it | Review is not instant | Submit templates days ahead; never build a cadence around an unapproved template |

## Five mistakes that cost coaches their limit

**The Portfolio Blind Spot.** Registering a second number for a second offer and expecting a second 250. The pool is shared. You split one allowance and feel throttled at half the volume you planned.

**The Blast Test.** Pushing a large, low-relevance send specifically to trigger a tier increase. The scaling criteria require high-quality messages _and_ volume. Volume alone with poor quality moves you the wrong way.

**The Silent Ceiling.** Configuring a setter to throttle inbound replies because you think they count. They don't. It is a self-inflicted wound on WhatsApp: a coach throttles the one thing that doesn't count toward the limit and is most likely to book a call.

### Mistakes that come from sending too much

**The Cold List Import.** Uploading numbers you collected somewhere else and templating them. The policy is unambiguous. You may only message people who gave you their number, and who gave "opt-in permission from the recipient confirming that they wish to receive subsequent messages or calls from you." A purchased or scraped list fails both halves.

**The Rescue That Won't Quit.** Running a five- or six-touch template cadence at someone who has never replied once. Each touch costs money, spends a slot, and invites the block that degrades everything else you send. Settle whether automation of this kind is acceptable at all before you build it. [Instagram automation and the terms of service](/blog/is-instagram-automation-against-terms-of-service) covers the same reasoning on the other Meta surface.

## Edge cases worth planning for

**The launch bigger than your tier.** You have 400 opted-in past clients and a 250 limit. Split the send across two consecutive afternoons, oldest cohort first. Do not request an increase the day before a launch. Scaling takes up to six hours _after_ you meet the criteria, and Meta measures those criteria over seven days. Decide the shape of that send while you are doing your [Q4 planning for a coaching business](/blog/q4-planning-for-coaching-business), not in the week you press go.

**The lead who replies at 2am from another timezone.** Their message opens a fresh window regardless of the hour. Your 8am answer is free-form and uncounted, and it's free while the number is inside its 1,000 free service messages for the month. There is no reason for a setter to hold a reply until "business hours" on WhatsApp, though there is a good reason to sound awake.

**The client who already bought.** A paying client in your onboarding group who gets a marketing template about your offer is your fastest route to a "report business" tap. Suppress current clients from every marketing send. Your CRM should own that flag, not your memory.

### Edge cases around migrated and test numbers

**The number you migrated from the Business app.** Messages sent from the app do not create or extend a Cloud API customer service window. A conversation that feels open on your phone may already be closed as far as the API is concerned. What you assumed was a free reply becomes a template send against your limit.

**The test number.** Meta's test business number sends free messages to at most five recipients. It is for wiring, not for a pilot. Treat any volume conclusion drawn from it as meaningless.

## What to do this week

Open WhatsApp Manager and read your current limit. Then count, honestly, how many people you start a conversation with on an average day. If the second number is under half the first, your limits are not your problem, and no amount of tier chasing books another call. Spend that attention on reply speed and on the first message, which is where a [multi-channel DM strategy](/blog/multi-channel-dm-playbook) earns its keep.

If you want software answering those threads, hold it to the limits. Pick one that treats WhatsApp Business message limits and tiers as design constraints rather than fine print. That means replies inside the window at human pace, a rescue cadence that stops, and an approval step before anything reaches a lead. Luca is built this way on purpose: auto-send is on by default on every channel, and you can switch any channel to review. WhatsApp in Luca is coming soon; Telegram, Instagram and Messenger are live today. Plans are [$99, $249 or $499 a month](/pricing) for 1,250, 4,000 or 8,500 replies, and every Luca plan comes with a 7-day free trial (card required). Before you buy anything, read [is Instagram DM automation safe](/blog/is-instagram-dm-automation-safe) and hold every vendor to the same standard on WhatsApp.


## FAQ

### What is the WhatsApp Business messaging limit for a new account?

A new business portfolio starts at 250. That means you can deliver messages to 250 unique WhatsApp user phone numbers outside a customer service window in a moving 24-hour period. Replies to people who messaged you first are not counted, and the first 1,000 a month per number are free.

### Is the WhatsApp messaging limit per phone number or per account?

Per business portfolio. Meta states that limits "are calculated and set at the business portfolio level and are shared by all business phone numbers within a portfolio." Registering a second number gives you a second identity, not a second allowance. Both numbers draw from the same daily pool.

### Do replies to incoming messages count against my WhatsApp limit?

No. The limit only counts unique numbers you message outside a customer service window. When someone writes to you, a 24-hour window opens, and everything you send inside it is free-form and uncounted, and the first 1,000 service messages a month per number are free. This is why fast replies cost you so little.

### How do I increase my WhatsApp Business messaging limit?

Meta raises it automatically when two conditions hold together: you are sending high-quality messages across all your phone numbers and templates, and in the last 7 days your business has used at least half of its current limit. When both are met, the limit rises by one level within six hours.

### What happens when you hit the WhatsApp messaging limit?

Business-initiated sends to new unique recipients stop working for the rest of the rolling 24-hour period. Inbound conversations continue normally. Capacity returns gradually as earlier recipients age out of the moving window, so sending resumes without any appeal or intervention from you.

### Does WhatsApp still use conversation-based pricing?

No. Meta's pricing documentation states that conversation-based pricing "was replaced with per-message pricing on July 1, 2025." Cost and messaging limits are now separate meters. You can sit well under your recipient cap and still run a meaningful bill from individual template sends.

### Can my WhatsApp messaging limit be lowered?

Meta's current messaging limits page describes increases only and does not publish a downgrade path or a "flagged" quality state, despite what older articles claim. What is documented is that poor quality blocks increases and that policy violations can restrict or remove access entirely.


## Sources

1. [Meta for Developers. "Messaging Limits: WhatsApp Business Platform."](https://developers.facebook.com/docs/whatsapp/messaging-limits)
2. [Meta for Developers: Pricing on the WhatsApp Business Platform (billed per delivered message by category and recipient country; conversation pricing deprecated; 1,000 free service messages per business number per month from October 1, 2026; free entry point window up to 7 days for click-to-WhatsApp ad clicks in the mobile app). Updated September 30, 2026. Retrieved October 17, 2026.](https://developers.facebook.com/documentation/business-messaging/whatsapp/pricing)
3. [Meta for Developers. "Cloud API Overview" (throughput, pair rate limits, error codes).](https://developers.facebook.com/docs/whatsapp/cloud-api/overview)
4. [Meta for Developers. "Message Templates" (template statuses and review).](https://developers.facebook.com/docs/whatsapp/business-management-api/message-templates)
5. [Meta for Developers. "Business Phone Numbers" (display name status).](https://developers.facebook.com/docs/whatsapp/cloud-api/phone-numbers)
6. [Meta for Developers. "Business Phone Numbers Reference."](https://developers.facebook.com/docs/whatsapp/cloud-api/reference/phone-numbers)
7. [Meta for Developers. "Cloud API Get Started" (test number recipient limit).](https://developers.facebook.com/docs/whatsapp/cloud-api/get-started)
8. [WhatsApp. "WhatsApp Business Messaging Policy." Retrieved October 17, 2026.](https://whatsappbusiness.com/policy/)

---

Published by SetLuca.