How Long Does It Take to Send 10,000 WhatsApp Messages?
Between two minutes and 40 days, and your messaging limit decides which. The tier math for a 10,000-person campaign, why the 24-hour window moves rather than resets, and what shortens the timeline.
A campaign of 10,000 WhatsApp messages takes anywhere from about two minutes to just over a month, and the deciding factor is not your internet connection or your sending software. It is the messaging limit Meta has assigned to your business portfolio. At an unlimited tier, pushing 10,000 messages at the default 80 per second takes roughly two minutes of wall-clock time. At the 250 starting tier, the same list takes 40 days.
That gap surprises people, and it wrecks launch plans. Below is how the timeline actually works out, where the real bottleneck sits, and what shortens it.
The two numbers that decide your timeline
There are two separate caps, and almost everyone confuses them.
Your messaging limit is the maximum number of unique WhatsApp users your business can deliver to, outside a customer service window, within a moving 24-hour period. Meta sets it at the business portfolio level, so every phone number in that portfolio draws from the same allowance. This is the cap that decides how many days your campaign runs.
Throughput is how fast you can push messages out once you are allowed to send them. Business phone numbers can send up to 80 messages per second by default, with capacity upgrades available, and it is set per phone number rather than per portfolio. This is the cap that decides how many minutes each day's batch takes.
For a 10,000-message campaign, throughput is almost never the constraint. Ten thousand messages at 80 per second is a little over two minutes of actual sending. The messaging limit is what stretches that into days.
How long 10,000 WhatsApp messages take at each tier
| Messaging limit | Days to reach 10,000 people | Sending time per day at 80/sec |
|---|---|---|
| 250 | 40 days | About 4 seconds |
| 2,000 | 5 days | About 25 seconds |
| 10,000 | 1 day | About 2 minutes 5 seconds |
| 100,000 | 1 day | About 2 minutes 5 seconds |
| Unlimited | 1 day | About 2 minutes 5 seconds |
Look at the right-hand column. Even on the slowest tier, the machine finishes its work in seconds. The other 23 hours and 59 minutes of every day are spent waiting for the rolling window to free up capacity. If you want the arithmetic for your own list size and tier, the WhatsApp messaging limits calculator works it out live.
The window moves, it does not reset at midnight
This detail catches out anyone who plans a campaign like a cron job. Meta measures your limit across a moving 24-hour period, not a calendar day. Capacity does not come back in one lump at midnight. It returns gradually, as individual sends from the previous day age past the 24-hour mark.
In practice that means a campaign which hits its ceiling at 2pm on Tuesday does not resume in full on Wednesday morning. It resumes at 2pm on Wednesday, and it trickles rather than bursts. Scheduling day two for 9am and finding almost nothing goes out is a normal, confusing first experience.
What actually slows a real send
The tier math above assumes a clean run. Three things commonly add time on top.
The pair rate limit. You can send 1 message every 6 seconds to the same WhatsApp user, which works out to roughly 10 messages a minute or 600 an hour. Going past it returns error code 131056 until you are back inside the allowed rate. This almost never affects a broadcast, where each recipient gets one message, but it reliably bites during testing when you fire repeatedly at your own number. Bursts of up to 45 messages in 6 seconds are tolerated, though they borrow from future quota: Meta's own example is that a burst of 20 needs about a two-minute wait afterwards.
Retries and failures. Invalid numbers, users who have not opted in, and transient errors all consume attempts. A sender that implements Meta's suggested backoff, retrying after 4 to the power of X seconds and increasing X on each failure, will pace itself correctly but will also take longer than the theoretical minimum. Other codes you might hit mid-campaign are collected in our WhatsApp error codes reference.
Template approval. Nothing sends until the template is approved, and Meta says a decision can take up to 24 hours. On a five-day campaign that is a meaningful chunk, and it is entirely avoidable by submitting early.
How to shorten the timeline
The only real lever is your messaging limit, and there are three routes off the 250 starting tier. You need one of them.
- Verify your business. Free, and the fastest route for most companies. Our Meta business verification guide covers the accepted document types.
- Have your partner verify it. If a solution partner or tech provider onboarded you, they can complete verification for you.
- Send your way there. Deliver 2,000 messages outside customer service windows to unique users within a 30-day moving period, using templates with a high quality rating.
Above 2,000, increases are automatic. Meta raises the portfolio one level within 6 hours when two conditions hold together: message quality is high across all your numbers and templates, and the business used at least half of its current messaging limit in the last 7 days.
That second condition is why cautious senders stay stuck. A business sitting at 2,000 and sending 400 messages a day will never scale, because it never touches the halfway mark. If your goal is a 10,000-person campaign next quarter, the ramp has to start now, and it has to be big enough to register. Protecting the quality rating while you ramp is the other half of the job.
Plan the send, then watch it
A campaign that runs across five or forty days is not something you fire and forget. Delivery receipts and replies arrive on your webhook, and Meta expects that endpoint to return HTTP 200. When it does not, Meta retries with decreasing frequency for up to seven days, which means a quiet outage on your side turns into missing conversation data you only notice much later. Putting the endpoint behind a service that checks the URL every 30 seconds and alerts you when it stops responding costs nothing meaningful and removes the worst failure mode of a long campaign. If the webhook itself is not set up yet, our WhatsApp webhook setup guide walks through the handshake.
Beyond that, the practical advice is unglamorous: submit templates days ahead, start the ramp weeks before a seasonal peak, keep the list clean so failures do not eat your allowance, and pick a bulk messaging platform that paces sends against your tier instead of firing everything at once and collecting errors.
Frequently asked questions
How long does it take to send 10,000 WhatsApp messages?
Between about two minutes and 40 days, depending on your messaging limit. At a 10,000 tier or higher the whole list goes out in one rolling 24-hour period, taking roughly two minutes of actual sending at 80 messages per second. At the 2,000 tier it takes five days, and at the 250 starting tier it takes 40.
How many WhatsApp messages can I send per second?
Business phone numbers can send up to 80 messages per second by default on the Cloud API, and capacity upgrades are available. Throughput is set per business phone number, unlike the messaging limit, which is set at the business portfolio level and shared across every number in it.
Does the messaging limit count messages or recipients?
Recipients. Meta defines it as the maximum number of unique WhatsApp user phone numbers you can deliver to in a moving 24-hour period. Sending one customer four messages uses one slot, not four. That is why the cap constrains broadcasts far more than it constrains conversational support.
Can I send 10,000 WhatsApp messages in one day?
Only if your business portfolio is on the 10,000 tier or higher. On the 2,000 tier the same list takes five rolling 24-hour periods. There is no way to buy a one-off increase for a single campaign, so the tier has to be earned before the launch date, not during it.
Why did my WhatsApp campaign stop halfway through?
Most likely you reached your messaging limit for the moving 24-hour window, so sends to new recipients began failing. Capacity returns gradually as older sends age past the 24-hour mark rather than resetting at midnight, which is why a stalled campaign resumes in a trickle at roughly the time of day it stopped.