Why Your WhatsApp Messages Need a Queue and a Sensible Pace

Say you have 500 customers and a sale starting tomorrow. You write a script that loops through the list and fires off a message to each one, as fast as the computer can go. It finishes in a few seconds. You feel clever.

Then some messages fail, a few customers complain, and your number gets restricted the next morning. The problem was never the message. It was the speed.

What a queue does

A queue is a waiting line. Instead of sending every message the instant you create it, your system puts each one in line, and a worker takes them out one at a time at a controlled rate. The line gives you three things you can't get otherwise: order, retries, and control over speed.

• Order: messages go out in the sequence you intended.
• Retries: if one fails because of a hiccup, it can be tried again without blocking the rest.
• Speed control: you decide how many messages go out per minute, and can slow down if something looks wrong.

Why pace matters

Real people don't send hundreds of near-identical messages in the same second. Platforms watch for patterns that look automated, such as bursts, repetitive text, and many recipients who've never heard from you. Pacing makes your traffic look less like a flood and, more importantly, gives recipients a chance to react before you've reached everyone.

That second point is the practical one. If your first fifty messages draw a few angry replies or blocks, a paced send lets you pause and fix the problem. A burst sends everything before you see the first complaint.

There is no single magic number

People often ask for the exact messages per minute that are safe. We don't give one, because it depends on your number's age and history, the type of connection, your content, and how recipients react. Official Cloud API accounts also have limits set by Meta that change with your account's standing, so check Meta's current documentation. For QR-linked numbers, the safer approach is simply to start slowly and ramp up as the number builds a clean history.

A sensible routine

1. 1Start with your most engaged contacts, the people who have replied or bought recently.
2. 2Send a small first batch and watch for replies, blocks and failures.
3. 3Add a little random variation to timing between messages instead of a rigid beat.
4. 4Vary the wording where it makes sense, for example by using the customer's name or order detail.
5. 5Spread large campaigns across hours or days rather than one burst.
6. 6Stop immediately if failures or complaints spike, and find out why.

Where queues show up in WA Getway

Message sending in WA Getway goes through a paced queue, so even if your code or a broadcast hands over a big list, the gateway releases the messages gradually. Broadcasts also record results per recipient, and the scheduler lets you set a send for a particular time instead of doing it by hand. Plans carry usage limits on things like numbers and monthly messages, which also acts as a natural ceiling. We go through those in choosing a gateway plan.

Mistakes we keep seeing

• Testing a new campaign on the full list instead of a handful of internal numbers.
• Sending identical text to everyone with no personalisation.
• Retrying failed sends in a tight loop, which multiplies the problem.
• Messaging people who never opted in and then wondering why users hit report.
• Forgetting that an unpaced QR session is the quickest route to a ban.

What to do when you must send a lot

Sometimes you really do have a big list, like a school with thousands of parents or an association with a large member base. Split it. Send to one section on day one, another on day two, and so on. Put the most important notices first. Use the scheduler instead of staying up late pressing buttons, and give yourself a morning check to look at failures before the next section goes out.

Also keep a record of consent for every number. A queue can pace a message, but it cannot make an unwanted message welcome.

Bans are covered in more depth in why WhatsApp numbers get banned, and the whole campaign process in how to run a broadcast campaign.

A queue won't rescue a bad list. It simply gives a good list room to breathe. If you're designing a sending flow from scratch and want a second pair of eyes, talk to us.