Broadcast pacing & limits
Anti-ban controls applied to every broadcast.
– seconds
Each account waits a random time in this range between its messages. A fixed cadence looks robotic — a spread of, say, 8–25s is far safer.
messages / day (0 = unlimited)
Once an account hits this many sends in a calendar day, the rest of its recipients in a broadcast are skipped. Ramp new accounts up slowly.
These reduce ban risk but don't eliminate it. Keep messages varied, only send to people who expect them, and stop immediately if you see blocks or reports.
Behavior & safety
Human-like sending and automatic circuit breakers.Shows a “typing…” presence for a moment before sending, like a real person. Adds a little time per message.
pause an account after consecutive failures (0 = off)
If sends keep failing, the account is likely dead/banned — stop it mid-broadcast instead of burning more numbers.
start cap × (account age in days + 1)
A day-old account caps at this many sends, a 2-day-old at 2×, and so on — ramps volume up gradually. The hard daily cap above still applies as a ceiling.
– server local hour (0–23)
Sends outside these hours are skipped. Overnight ranges (e.g. 22–6) are supported.
When someone links an account, detect their public IP's country and bind an egress proxy from the pool in that same country (so the WhatsApp number sends from a matching region). Falls back to the default/direct if no tested proxy matches. Only works for real remote users — localhost has no public IP.