Guide · Sending · For the owner planning a send to the whole list

How fast can our WhatsApp number send? Meta's throughput, how it differs from the daily limit, and the one case where it is fixed low

An owner planning a send to the whole customer list asks two questions and usually gets them muddled: how many people may we message today, and how fast will it go out? Meta answers them separately. The first is the messaging limit, a daily count of new customers. The second is throughput, the number of messages a business number can push through per second. Here is what Meta's throughput page says about the speed, who gets more of it, and the one case where the speed is fixed low.

Published 1 October 2026

Two different limits

Messaging limit: How many different customers a number may start conversations with in a rolling 24 hours. It grows with volume and quality in tiers, up to unlimited. It is about reach, not speed, and it is covered in its own guide.
Throughput: How many messages per second a number can send and receive, counting every direction and every type. Meta's page says each registered business number starts at up to 80 messages a second and can be raised automatically to up to 1,000. It is about speed, and it never raises the messaging limit.

So a send of several thousand messages is bounded twice: the messaging limit decides whether all those customers may be contacted today at all, and throughput decides how many minutes the sending takes. The messaging limits guide covers the first; the rest of this page is the second.

The fixed case

Meta's page says a number that is used with both the WhatsApp Business app and the connected system, the arrangement where the owner keeps the app on the phone, has a fixed throughput of 20 messages a second, to stay compatible with the app. It is plenty for a shop's daily traffic and a real ceiling for a campaign: a send to several thousand people from such a number is measured in minutes, not seconds, and no upgrade applies.

What happens at the ceiling

Messages above the level are refused, not queued. Meta returns a specific throughput error until the sending rate is back within the level. A proper system paces the send and retries; a careless one reports hundreds of failures that were never really failures. The code appears in the failure reasons guide.
Speed is for many people, not one person. Meta says throughput levels are intended for campaigns to different customers, and that sending too many messages to the same customer triggers a separate per-pair limit. A reminder sequence that fires five messages at one person in a second is the wrong shape regardless of throughput.
The daily limit still applies. Meta is explicit that numbers, whatever their throughput, remain subject to the account rate limit and the template messaging limits.

Who gets the faster level, and what it costs

Nothing, in money. Meta's page says the upgrade to the higher level is automatic and free once a number is eligible, and does not change pricing. Eligibility is three things together: the business portfolio is already on an unlimited messaging limit; the number has messaged 100,000 or more different customers outside a service window within a moving 24-hour period; and its quality rating is medium or better, as explained in the quality rating guide. That is a large sender's profile. Most small and mid-sized businesses will live at the default level, which is already far faster than they need.

The upgrade itself has one operational wrinkle: Meta says it can take up to a minute, during which the number cannot be used and sends are refused with a maintenance error. After the first upgrade, later increases happen with no downtime, and Meta sends the connected system a notice that the upgrade happened.

The faster the send, the heavier the replies

Speed cuts both ways. Meta tells providers that the servers receiving delivery updates and replies must handle three times the outgoing rate in status updates plus the incoming replies, answering quickly and concurrently, and that Meta keeps retrying any update it could not deliver for up to 7 days. An owner does not run those servers, but should know that a campaign which goes out fast produces its replies fast, and the people answering them need to be ready at the same moment.

Questions

Can our provider buy us more speed?

No. Meta's page says the higher level is granted automatically when the number meets the eligibility conditions, at no cost, and that higher throughput does not affect pricing. There is nothing to buy.

We keep the WhatsApp Business app on the phone. Does that slow sending?

For campaigns, yes. Meta fixes a number used with both the app and the connected system at 20 messages a second. For everyday customer conversations it makes no practical difference.

Our campaign showed lots of errors in the first minute and then went fine. Why?

The likely cause is sending faster than the number's level; Meta refuses the excess with a throughput error until the rate drops. The system should pace the send so this never reaches the report as failures.

Does an image or video count the same as a text?

For throughput, Meta counts every message type and both directions. Meta does advise providers to upload media to Meta first and send it by reference, or to cache it, so that the attachment does not slow a large send.

Sources

Meta's developer documentation: throughput, read 1 October 2026.

More plain-language notes like this one are on the guides page.

Planning a send to the whole list and want it paced properly?

We set up a business's WhatsApp number on a proper system that knows the number's throughput level, paces a campaign under it so nothing is refused, keeps within the daily messaging limit, and has the replies routed to the people who will answer them. A short call is the easiest way to see whether it fits your business.

Book a demo