# WhatsApp messaging limits and quality rating

> Meta's WhatsApp messaging limit tiers, throughput, the 131056 pair rate limit and quality rating, and how to pace sends so you stay inside them.

Source: https://whabuzz.com/blog/whatsapp-quality-rating-messaging-limits/
By Smaran Challapalli. Published 16 Oct 2026. Updated 16 Oct 2026.

A WhatsApp messaging limit is the number of unique customers your business can start conversations with in a moving 24-hour period. Meta sets it for the whole business portfolio, raises it in steps from 250 to unlimited, and enforces three other limits on top: throughput per number, one message per six seconds to the same person, and quality-based restrictions. This post covers each one.

## What is a WhatsApp messaging limit?

A messaging limit caps how many different people you can message outside a customer service window. According to [Meta's messaging limits page](https://developers.facebook.com/documentation/business-messaging/whatsapp/messaging-limits):

> Messaging limits are 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.
>
> Source: [Meta: Messaging limits](https://developers.facebook.com/documentation/business-messaging/whatsapp/messaging-limits)

Three details matter in practice.

- It counts unique recipients, not messages. Sending one customer ten templates uses one slot.
- Replies inside an open 24-hour window do not use the limit, because they are not "outside of a customer service window". The window rules are in the [24-hour window post](https://whabuzz.com/blog/whatsapp-24-hour-window/).
- Per Meta's page, limits are calculated at the business portfolio level and shared by all business phone numbers in that portfolio. Adding a second number does not double your daily reach.

## Which messaging limit tiers does Meta list?

Meta lists five levels. Per the same page: "Newly created business portfolios have a messaging limit of 250, but this messaging limit can be increased to" the following.

| Level | How you get there (per Meta) |
|---|---|
| 250 | Starting point for a new portfolio |
| 2,000 | Complete a scaling path |
| 10,000 | Automatic scaling |
| 100,000 | Automatic scaling |
| Unlimited | Automatic scaling |

There is no 1,000 level on the current page. Older posts and some provider docs still mention one, so check the date on anything you read.

## How do you move up a tier?

The first jump, to 2,000, needs one of three things. According to Meta's page: verify your business, have your partner verify your business (if a partner onboarded you), or 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 that the climb is automatic. Meta's criteria are that you are sending high-quality messages across all your numbers and templates, and that in the last 7 days you used at least half of your current limit. When both hold, "your portfolio's limit increases by one level within 6 hours."

The practical lesson: size a campaign against your current level, and read that level before you send.

You can see the current level in WhatsApp Manager, or through the API: Meta says to request the `whatsapp_business_manager_messaging_limit` field on the phone number, because the older `messaging_limit_tier` field has been deprecated. WhaBuzz forwards Meta's phone-number quality and limit webhook as a [`number.quality` event](https://docs.whabuzz.com/events/number-quality/), so a tier change reaches your endpoint without polling.

## How fast can one number send?

Throughput is a separate limit from the daily one. According to [Meta's throughput page](https://developers.facebook.com/documentation/business-messaging/whatsapp/throughput):

> For each registered business phone number, Cloud API supports up to 80 messages per second (mps) by default, and up to 1,000 mps by automatic upgrade.
>
> Source: [Meta: Throughput](https://developers.facebook.com/documentation/business-messaging/whatsapp/throughput)

Meta counts inbound and outbound messages together, across all message types. If you go over, you get error `130429`.

The automatic upgrade to 1,000 mps has three conditions per Meta: the portfolio has an unlimited messaging limit, the number has messaged 100K or more unique users outside a customer service window within a moving 24-hour period, and its `quality_score` is YELLOW (shown as Medium in WhatsApp Manager) or higher. Meta adds that higher throughput does not incur additional charges or affect pricing.

For most businesses the binding constraint is the daily limit, not the per-second one.

## What is the pair rate limit and error 131056?

The pair rate limit protects one person from getting a burst of messages from one number. Per [Meta's platform overview](https://developers.facebook.com/documentation/business-messaging/whatsapp/about-the-platform), a business number can send 1 message every 6 seconds to the same WhatsApp user, which Meta equates to about 10 messages per minute or 600 per hour. Going over triggers error `131056`.

Meta's error page describes it as too many messages sent from the sender phone number to the same recipient number in a short period, and says to wait and retry if you intend to message that person. You can still send to other people straight away.

This one catches teams that fire an order confirmation, a payment receipt and a shipping update within a second of each other. Queue per recipient, not globally. A simple rule: keep a short delay between consecutive sends to the same number. The retry rules for every code are in [the error codes post](https://whabuzz.com/blog/whatsapp-api-error-codes/).

## What does quality rating do?

Quality rating is Meta's signal of how recipients react to your messages. Meta's phone numbers page says business phone numbers have a status that reflects their quality rating and current messaging limit. Meta ties it to tier growth (automatic scaling needs high-quality messages) and to throughput (the YELLOW or higher requirement above).

The colour definitions for phone-number ratings that circulate online come from third-party help pages, not from the Meta pages this post relies on, so it does not repeat them. Read the rating and its explanation in WhatsApp Manager and in the `number.quality` event payload, which carries Meta's own values unchanged.

What you can do without knowing the exact thresholds is the same advice Meta's own error text gives: send to people who expect the message, use the right template category, and watch for restriction errors such as `131048`, which Meta describes as restrictions on how many messages can be sent from the number, possibly because too many earlier messages were blocked or flagged as spam.

## How should you pace sends in code?

Pace by recipient and by number, and treat `130429` and `131056` as "slow down", not as failures. WhaBuzz does not throttle your `/v1` calls in v1; per the [rate limits guide](https://docs.whabuzz.com/guides/rate-limits/), Meta's limits pass through with `"source":"meta"`.

For bulk sends, use the batch endpoint. The docs say WhaBuzz paces batches at 20 messages per second for a standard number and 50 for a high-throughput one, with a scheduler that sends at most 900 items per run each minute. Failed items are not retried, so list them with `?status=failed` and decide what to resend.

For single sends, a minimal back-off looks like this with the Node SDK, which throws `WhaBuzzError` with Meta's error object under `meta`:

```js
import { WhaBuzz } from 'whabuzz';
const wb = new WhaBuzz();

async function send(body, key, tries = 4) {
  for (let i = 0; i < tries; i++) {
    try {
      return await wb.messages.send(body, { idempotencyKey: key });
    } catch (e) {
      const slowDown = e.source === 'meta' && [130429, 131056].includes(e.meta.code);
      if (!slowDown || i === tries - 1) throw e;
      await new Promise((r) => setTimeout(r, 2000 * 2 ** i));
    }
  }
}
```

The same `Idempotency-Key` on each attempt means a retry that Meta accepted the first time is not sent twice. See the [idempotency guide](https://docs.whabuzz.com/guides/idempotency/).

## Messaging limits for Indian businesses

Nothing on Meta's messaging limits page is India-specific, so the tiers above apply to an Indian portfolio the same way. What differs is cost. According to Meta's rate card effective 1 Oct 2026, a marketing message to India is ₹0.8631 and a utility message ₹0.115, billed by Meta to your own Meta account. The [pricing post](https://whabuzz.com/blog/whatsapp-business-api-pricing-india/) has the full table, and the [numbers guide](https://docs.whabuzz.com/guides/numbers/) covers connecting a number and what makes it `connected`.

## Frequently asked questions

### Is there a 1,000-customer messaging limit on WhatsApp?

Not on Meta's current messaging limits page. It lists 250 for new portfolios, then 2,000, 10,000, 100,000 and unlimited.

### Is the messaging limit per number or per business?

Per business portfolio. Meta says limits are calculated at the portfolio level and shared by all business phone numbers in it.

### What is the default WhatsApp Cloud API throughput?

80 messages per second per registered business phone number by default, with an automatic upgrade to 1,000 mps when Meta's conditions are met.

### What does error 131056 mean?

You sent too many messages from one number to the same recipient in a short period. Meta's limit is 1 message every 6 seconds to the same user. Wait and retry; other recipients are unaffected.

### Does WhaBuzz add its own rate limit?

No request quota applies to `/v1` in v1. Meta's limits pass through unchanged, and batch sends are paced for you.

## Related reading

- [WhatsApp API error codes and what to do](https://whabuzz.com/blog/whatsapp-api-error-codes/)
- [The WhatsApp 24-hour window](https://whabuzz.com/blog/whatsapp-24-hour-window/)
- [WhatsApp Business API pricing in India](https://whabuzz.com/blog/whatsapp-business-api-pricing-india/)
- [Rate limits and pacing](https://docs.whabuzz.com/guides/rate-limits/)
- [Numbers and Embedded Signup](https://docs.whabuzz.com/guides/numbers/)
- [Errors reference](https://docs.whabuzz.com/errors/)