Throughput
Throughput is the rate at which the WhatsApp Business API accepts and sends your outbound messages — measured in messages per second (MPS) for a given phone number. It is one of the most misunderstood constraints in high-volume WhatsApp messaging: businesses often confuse it with their daily messaging limit (how many unique users you can start conversations with), when in fact throughput governs how fast those messages leave the queue. For Indian businesses running OTP flows, order updates, or large campaign blasts, understanding throughput is the difference between a promo that reaches customers in seconds and one that trickles out over hours.
In one line
Throughput is the messages-per-second (MPS) rate your WhatsApp Business API number can send, set by Meta and shaped by your phone-number quality rating and business verification — separate from your daily unique-user messaging limit.What throughput actually measures
Throughput is the sustained send rate of a single WhatsApp Business phone number, expressed in messages per second. When your application hands a batch of template messages to the API, throughput is the ceiling on how quickly Meta will accept and dispatch them. On the WhatsApp Cloud API, numbers commonly start at a default of around 80 messages per second and can be raised on request — in tiers — up to roughly 1,000 MPS for numbers with strong volume and quality. Crucially, throughput counts every message you send, regardless of category: marketing, utility, and authentication templates all draw from the same per-second budget. If you push messages faster than your throughput allows, the API doesn't silently drop them — it returns rate-limit errors (HTTP 429) and expects your system to back off and retry.
- Unit: messages per second (MPS) per phone number
- Applies to all message categories combined, not per category
- Default is roughly 80 MPS; can scale toward 1,000 MPS
- Exceeding it triggers rate-limit (429) errors, not silent drops
Throughput vs. your daily messaging limit
The single most common mistake is treating throughput and the messaging limit as the same thing — they are not. Your messaging limit is the number of unique customers you can initiate marketing or utility conversations with in a rolling 24-hour period (the tiers most people know: 2K, 10K, 100K, and unlimited). Throughput is orthogonal: it is the speed at which messages flow, not the count of distinct recipients. A number sitting in the 100K daily tier can still be throttled if it tries to fire all 100,000 messages within a few seconds. Conversely, authentication and service messages don't consume your daily unique-user tier the same way, yet they absolutely count against throughput. When you plan a campaign, you need both numbers to line up: enough daily limit to reach everyone, and enough MPS to reach them in an acceptable window.
What raises and lowers your throughput
Meta doesn't grant peak throughput automatically. It scales with demonstrated, healthy sending: as your number handles higher volumes while keeping a good quality rating, you become eligible for higher MPS tiers, and providers can request an increase on your behalf. The biggest drag on throughput is a declining quality rating — driven by users blocking your number or marking messages as spam. A number that drops to a low quality state can be capped, flagged, or restricted, which effectively strangles your practical throughput no matter what tier you were assigned. Completed business verification and a registered, well-configured number also matter, because Meta reserves the higher tiers for accounts it trusts. In short, throughput is earned through consistent, opt-in, low-complaint messaging — not bought.
- Higher sustained volume with good quality unlocks higher MPS tiers
- Poor quality rating (blocks, spam reports) caps effective throughput
- Business verification and proper number registration are prerequisites
- A provider can request a throughput increase for eligible numbers
How to plan campaigns around throughput
To send a large blast without hitting rate limits, divide your audience size by your MPS to estimate the send window, then build in headroom. At 80 MPS, 100,000 messages take at least ~21 minutes of continuous sending; at 1,000 MPS, under two minutes. The practical fix is a queue-and-drip architecture: your system meters messages out at a rate just below your ceiling, respects 429 responses with exponential backoff, and spreads time-sensitive sends so recipients aren't all messaged in the same instant. For authentication (OTP) traffic especially, low latency matters more than raw volume — a user waiting on a login code notices a two-second delay. InfiQ's platform handles this metering, retry, and backoff logic for you, so you specify the audience and template and the delivery pacing is managed against your number's live limits.
Frequently asked questions
Is throughput the same as my WhatsApp messaging limit?+
What is the default throughput for a new WhatsApp Business number?+
How do I increase my throughput?+
What happens if I send faster than my throughput allows?+
Does throughput count marketing, utility, and authentication messages separately?+
Does using more phone numbers increase my total throughput?+
How long will it take to send a large campaign?+
Can a low quality rating reduce my throughput?+
Send at the speed your business needs
Talk to an InfiQ onboarding specialist about scaling your throughput safely — we manage metering, retries, and quality so your OTPs and campaigns land on time, with transparent ₹ pricing.