How to avoid a WhatsApp ban

Regular WhatsApp connects to AISAR as a linked device, so it plays by the same rules as WhatsApp Web — including the risk of WhatsApp itself banning the number for suspicious bulk sending. Here's what actually raises that risk, which safeguards AISAR already builds in, and what to do if a channel gets banned anyway.

What you need to know

The ban comes from WhatsApp itself, not AISAR: the channel is an ordinary linked device (like WhatsApp Web), and every one of WhatsApp's own anti-spam mechanisms applies to it exactly as it would to any other client.
The official WhatsApp Business API (WABA) doesn't carry this risk — it's a separate, Meta-managed channel with no QR scanning and no bans for broadcast volume in the same sense. For regular, high-volume broadcasts, see Connecting WhatsApp Business (WABA).
AISAR cannot lift a WhatsApp-side ban and has no say in WhatsApp's decision — it can only reduce the odds of triggering one, and it reports the channel's status honestly either way.

What actually raises ban risk

WhatsApp doesn't publish an exact ban formula, but its main input is recipient complaints and blocks, plus behavior typical of spam campaigns. In practice, risk goes up with:

Mass first-contact messages to people who never wrote to you first or agreed to be messaged.
Near-identical text sent to a large number of contacts in a short window.
A brand-new number, connected minutes ago, immediately used for a bulk send instead of a period of ordinary use first.
A high rate of recipient complaints and blocks — that is what WhatsApp actually reacts to, not the mere fact of using a third-party client.
Using that same number in the official WhatsApp phone app for similar bulk sending at the same time.

AISAR's built-in safeguards

For regular WhatsApp (unlike WABA), broadcasts in AISAR don't fire all at once by default — they run under Sending rate control, on the broadcast schedule step:

Mechanism	What it does
Messages per minute	Defaults to 15 messages per minute for personal WhatsApp. Going above the recommended value gets flagged with "Exceeds the recommended value… the channel can get blocked."
Random delay between messages (jitter)	Defaults to 3-8 seconds — imitates a human sending by hand instead of a perfectly even bot cadence. Dropping below the recommended value also triggers a warning.
Daily limit	Defaults to 1500 messages per day per channel — a broadcast that hits the cap resumes the next day instead of stopping outright.
Skip recently contacted	Optional filter (1-720 hours): a contact already messaged within that window gets skipped in the current broadcast — cuts the odds of the same person getting several similar messages back to back.
Send window	Restricts sending to specific hours (a fixed window, or a "smart" window based on each recipient's own activity) instead of sending at any time of day.
Automatic broadcast opt-out	Replying "stop", "/stop", "unsubscribe" or its Russian equivalent to any AISAR message opts the contact out of broadcasts across every channel at once — future broadcasts skip them until they write in again.

These limits don't apply to the WhatsApp Business API: the official channel has its own Meta-managed throughput, and AISAR doesn't layer its own rate limit on top of it — see How much the WhatsApp Business API costs and its limits.

How to prepare a broadcast the safe way

Build a narrow recipient segment instead of "send to everyone" — the more targeted the audience, the fewer stray complaints.
Don't push messages-per-minute up, or the delay down, past the values AISAR flags as recommended for this channel.
Turn on "Skip recently contacted" and "Send window" if the broadcast goes out in waves, or a contact may have received another message recently for an unrelated reason.
Add opt-out text (Include opt-out in the broadcast content settings) — replying "stop" is an easier first move for someone than tapping "Report" in WhatsApp.
Warm up a brand-new number with ordinary use first — a few days of real one-on-one conversation and replies before loading it with its first large broadcast.
For regular, high-volume broadcasting, move to the WhatsApp Business API — it's built for exactly this, not stretched to fit.

If the channel gets banned anyway

The channel in the list (Settings → Channels) switches to Banned status — that is WhatsApp's call, AISAR just reflects it. Reconnecting the channel in AISAR only works once the ban is actually lifted on WhatsApp's own side: request an account review in the official WhatsApp app on the phone. If the account is still banned, the channel goes right back to "Banned" as soon as it re-pairs.

Common issues