Bulk messages, without the ban
Bulk messaging on WhatsApp at scale is a tightrope walk. Send too fast or too uniform and Meta throttles, hides, or bans the number. Wazzap gives you the tooling to walk that line safely: Spintax variations, smart intervals, number rotation, warming, and a CRM-native drip mode.
Overview
Wazzap supports bulk sending end-to-end. You import contacts (or pull them from your CRM), stage a campaign with the anti-ban stack enabled, and let it run. Most teams pair Wazzap with HighLevel for the orchestration, but you can also drive bulks via API or directly from Wazzap's compose screen.
Bulk messaging is powerful. It's also the single biggest cause of bans we see. Read every section below before launching anything to a large list, and start small.
The anti-ban stack
Four lines of defense work together. Skip any one of them and your number's lifespan drops. Use all four and you can sustain serious volume for months.
1. Number warming
New WhatsApp numbers are fragile. Sending 1,000 messages on day one is the fastest path to a permanent ban. Warm the number for at least 7-14 days first: hold inbound conversations, send a handful of outbounds per day, scale gradually.
The full process is in number warming process.
2. Spintax variations
When the same exact text goes to thousands of contacts, Meta's spam detection learns the pattern within hours. Spintax rewrites every send with different phrasing, so each recipient sees a slightly different message even though the intent is the same.
!/SPINTAX_A/Hi/Hello/Good morning/SPINTAX_A/! {contact.first_name}, quick question about your order. 3. Smart intervals
Bursts get flagged. A natural sender doesn't fire 50 messages in 10 seconds. Wazzap lets you configure a random delay between each message in a campaign (e.g. 30-90 seconds), so the send rate looks like a human typing.
- Set a minimum and maximum interval. Wazzap picks a random value in that range per send.
- Add per-day caps. Most numbers should never exceed 500-1,500 messages per 24 hours.
- Skip the night. Sends after midnight local time look suspicious.
4. Number rotation
Don't put all your eggs in one number. Switch numbers splits a campaign across multiple connected numbers so the daily volume per number stays low. Three warmed numbers sending 500/day each is far safer than one number sending 1,500.
CSV import and segmentation
Wazzap accepts CSV uploads with the typical columns:
phone,first_name,last_name,city,tag
+5215511223344,Diego,Salcedo,Guadalajara,vip
+5215511223345,Ana,Lopez,Mexico City,prospect
...
The header row is required. Phone numbers must include the country code (no spaces, no
dashes). Any extra column you add (e.g. order_id, plan) becomes
a merge variable you can reference in your message:
Hi {first_name}, your order {order_id} just shipped. Sending from your CRM
The cleanest path for most teams is to drive bulks from HighLevel using Wazzap as the conversation provider. You get the audience targeting, the workflow logic, and the reporting built into the CRM, with Wazzap handling the actual sends.
Drip mode
HighLevel's drip mode distributes a workflow's sends over a window of hours or days. You configure the total volume and the rate cap, and HighLevel paces it. Combined with Wazzap's intervals, you get two layers of throttling.
- Build a workflow with a "Send WhatsApp" step.
- Enable Drip mode at the workflow level.
- Set a daily cap (e.g. 500 contacts/day) and a window (e.g. 9am-6pm local).
- Trigger the workflow on the audience segment.
Traffic split
HighLevel's traffic split divides a list into N groups (e.g. 500/500) and routes each group down a different path. Pair this with Wazzap's number rotation to send the same campaign from multiple numbers at the same time, each one staying under its daily safe limit.
Audience: 3,000 contacts
Split 1 (1,000) → number A → drip 500/day
Split 2 (1,000) → number B → drip 500/day
Split 3 (1,000) → number C → drip 500/day
Total: ~2 days, ~1,000 sends/day across the fleet How many messages per day
There's no universal limit, the answer depends on the number's age, warming level, content quality, and recipient response rate. As a rough ladder:
- Days 1-7 (fresh number). 20-50 outbound, mostly to known contacts.
- Days 8-30 (warming). 100-300 outbound per day, ramp gradually.
- Months 2-3 (stable). 500-1,000 outbound per day with the anti-ban stack on.
- Mature (6+ months). Some numbers handle up to 3,000/day, but factors like reply rate matter a lot. Treat 1,500 as the upper safe ceiling.
Reply rate is the strongest signal Meta uses. If 80% of your sends get a reply, you can push volume higher. If most are ignored, drop the volume immediately, the spam classifier is already warming up.
If a number gets banned
Don't panic, the first ban is usually recoverable. We've never seen a number permanently lost on its first offense, provided you follow the reconnect-after-a-ban guide. Subsequent bans get progressively harder to lift.
Risk disclaimer
- Bulk messaging is always at your own risk.
- Run a 50-100 contact simulation before any large send.
- Scale gradually, monitor reply rates daily, adapt based on what you see.
- Respect WhatsApp's policies. Consent matters. Make sure your audience actually opted in.