Best Practices for WhatsApp Outreach
Loopwave connects through a linked-device session on a regular WhatsApp number. That gives you freedom and zero per-message fees — but WhatsApp actively detects and bans numbers that behave like spam. The single biggest factor in staying safe is your own sending discipline. This page is the playbook.
No tool can guarantee a number will never be banned. Loopwave ships strong anti-ban defaults, but reckless sending — blasting strangers, ignoring opt-outs, firing a brand-new number at hundreds of people — will get any number flagged. Treat your number as a long-term asset.
The golden rules
Message customers who contacted you first, opted in, or have a real relationship with your business. Cold-blasting purchased lists is the fastest route to a ban.
A fresh number sending bulk messages on day one looks exactly like spam. Ramp up slowly. See Warming Up New Numbers.
Humans don’t send 200 identical messages in a minute. Spread sends out with delays — Loopwave does this automatically for broadcasts and auto-replies.
Always offer a way to stop (“reply STOP to opt out”) and remove anyone who asks immediately. High block/report rates are what get numbers banned.
Consent and opt-out
WhatsApp’s signal of “spam” is largely driven by how recipients react. If people block or report you, your number’s risk score climbs fast.
- Get consent. Outreach should go to people who agreed to hear from you.
- Identify yourself in the first message so recipients recognize you.
- Offer an opt-out such as “Reply STOP to stop receiving messages,” and act on it.
- Maintain a suppression list of anyone who opted out, and never message them again.
Use labels or a contact lifecycle stage
like churned to mark opted-out contacts so your team never includes them in a
broadcast.
Pacing and daily volume
Sudden spikes look automated. Keep volume steady and modest, especially early on.
| Number age | Suggested daily ceiling | Notes |
|---|---|---|
| Brand new (week 1) | ~20–40 conversations | Mostly two-way replies, not bulk. |
| Warming (weeks 2–4) | ~50–150 / day, ramping | Increase gradually only if blocks stay near zero. |
| Established | Up to a few hundred / day | Watch block/report rates; back off if they rise. |
These are conservative guidelines, not guarantees. A trusted, aged number with a high reply rate tolerates more; a new number with low engagement tolerates far less. When in doubt, send less.
Message quality
- Personalize. Use the
{{name}}variable in templates, automations, and broadcasts so messages don’t look mass-produced. - Vary your copy. Identical text sent to hundreds of people is a spam signal.
- Encourage replies. Two-way conversations build trust signals; one-way blasts erode them.
- Avoid risky links and attachments to people who don’t expect them.
Groups vs. direct add
- Never auto-add strangers to groups. Adding people who didn’t ask is a strong spam signal and a common ban trigger.
- Prefer invite links. Share a group invite link and let people join voluntarily.
Risk table
| Behavior | Risk | Do this instead |
|---|---|---|
| Bulk-messaging a purchased list | Very high | Only message opted-in contacts |
| New number sending 200+ on day one | Very high | Warm up over weeks |
| Identical message to everyone | High | Personalize with {{name}}, vary copy |
| No opt-out offered | High | Add “reply STOP,” honor it |
| Adding strangers to groups | High | Share an invite link instead |
| Ignoring blocks/reports | High | Remove reactive contacts immediately |
| Steady, personalized, opted-in sends | Low | Keep doing this |
What Loopwave does for you
Loopwave bakes pacing into the parts of the product that send at volume, so the safe path is the default path.
Broadcasts are paced automatically
Broadcasts send one recipient per tick with a random 8–20 second gap between each send, enforce a daily cap (around 500 sends/day), and pause entirely whenever the number is disconnected. You cannot accidentally fire a thousand messages in a burst. See Broadcast anti-ban pacing.
Auto-replies are throttled
Auto-reply automations enforce a per-chat cooldown (default 5 minutes), a global rate cap (about 8 replies/minute), a random 3–9 second human-like delay before each reply, and a ready-check so nothing sends through a disconnected number. See Auto-reply anti-ban guards.
Sends pause when a number drops
If a number disconnects mid-broadcast, sending pauses until it reconnects, instead of failing every remaining recipient.
The most important habit for a brand-new number.