How do I run a bulk send without burning my channel?
A badly run broadcast does not just cost you the campaign: it costs you the channel. A number restricted by Meta and a domain marked as spam take weeks to recover, if they recover at all.
Before you start
- Role: Owner, Admin or Editor.
- A connected channel in Messaging.
- Know how many sending credits you have before you begin.
1. Pick an audience, not the whole base
Start from a segment, not from "everyone". Sending to people with no relationship to the subject produces blocks and unsubscribes — exactly the signals that sink your reputation.
2. Check the size and the credits
Compare the audience size against your credit balance. The broadcast screen shows the recipient count and the estimated cost before you confirm. A campaign that stops halfway leaves half your base without the message and the other half without the context for what comes next.
3. Respect the channel's limit
See official WhatsApp from scratch and email nurture sequence.
4. Release it in batches
Do not send everything at once. Use batch sending — how many go out per cycle and the interval between cycles — to release a smaller slice, watch delivery and reaction, then widen. Batching turns a mistake into a small incident instead of a whole-base catastrophe.
5. Test first
Send to yourself and to someone on your team. Check the links, the personalisation fields and how it looks on a phone. A field name showing up raw in the message is the most visible and most avoidable error there is.
6. Make it easy to opt out
An easy way out protects the channel. Someone who does not want your messages and cannot leave will mark you as spam or block you — and that weighs far more than an unsubscribe.
7. Follow it afterwards
Send, then watch. If delivery drops or blocks climb, stop the rest before the campaign completes. A broadcast in progress can be cancelled; batches not yet sent are stopped.
Related
If it didn't work
- The send stopped halfway: most likely credits — check the balance in Messaging.
- WhatsApp was restricted: see the Meta sending limit (Portuguese).
- The message went out with a blank field: that contact had no value stored for it — set a default value.