> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wadial.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Reduce the risk of account restrictions

> Design consent-based WhatsApp messaging that avoids spam patterns and responds safely to delivery problems.

WhatsApp may limit, suspend, or ban a number based on its policies, recipient feedback, and platform signals. WADial cannot predict, prevent, or reverse those decisions. The practices below reduce risk, but they do not guarantee that an account will remain unrestricted.

## Start with clear consent

Send messages only to people who have asked to receive them.

* Explain who will message them, why, and how often.
* Keep a record of when, where, and what the recipient agreed to.
* Use consent for the stated purpose. An order update opt-in is not permission for unrelated promotions.
* Never use purchased, scraped, or shared contact lists without valid recipient consent.
* For a new conversation, prefer a website button, QR code, or `wa.me` link that lets the recipient start the chat.

Consent requirements vary by country and message type. You are responsible for meeting applicable privacy, marketing, telecommunications, and consumer-protection laws.

## Send messages people expect

The safest automation behaves like a useful continuation of a customer relationship.

* Prioritize replies and updates triggered by a recipient's action.
* Identify your organization and make the purpose of the message clear.
* Keep the first message short and send one complete update instead of several fragments.
* Do not send unrelated content, repeated reminders, or unnecessary attachments.
* Use recognizable HTTPS links. Avoid misleading redirects or links with a poor reputation.
* Do not run outreach continuously throughout the day and night.

Personalization should make a message more useful, not disguise duplicated bulk content or evade platform controls.

## Honor opt-outs immediately

Give recipients a clear way to stop messages and process that request before sending another automation.

Your application should maintain a suppression list and recognize the opt-out words appropriate for the languages and regions you support. A recipient who withdraws consent should stay suppressed unless they complete a new, explicit opt-in.

## Control sending rate

There is no universal "safe" number of messages per minute. Account history, recipient behavior, message content, and WhatsApp policy can all affect enforcement.

* Queue outbound work instead of sending large bursts.
* Apply limits per recipient and per connected token.
* Increase volume gradually only when recipients are expecting and engaging with the messages.
* Pause a campaign when blocks, complaints, delivery failures, or protocol errors increase.
* Do not repeatedly retry a rejected message.

For transient API failures, retry with backoff and reuse the same `Idempotency-Key`. This prevents one business event from becoming multiple sends. See [Idempotency](/api/idempotency).

## Recommended delivery workflow

Before each send:

1. Confirm that the recipient has valid consent for this message.
2. Check that the recipient is not on your suppression list.
3. Verify that the content matches the promised purpose and timing.
4. Use a stable `Idempotency-Key` for the business event.
5. Send through the intended connected token.
6. Record the result and monitor request logs, token events, and receipts.
7. Stop or escalate the workflow when errors repeat instead of continuing blindly.

Use [usage and logs](/api/observability) to review API results and token activity. Webhooks or the event stream can feed delivery outcomes into your own queue and suppression logic.

## When sending starts failing

If a connected token suddenly fails to send, treat it as a signal to pause—not a reason to send faster or rotate numbers.

1. Stop automated sends, especially outreach to new contacts.
2. Check the token status, request logs, timeline, and WhatsApp app for errors or account notices.
3. Do not log out, delete the token, or repeatedly re-pair it as your first response.
4. If the token is merely disconnected but still paired, [reconnect it once](/guides/reconnect-token).
5. Do not retry rejected messages until you understand the failure.
6. After the issue is cleared, resume cautiously with a recipient who is expecting the message.

If WhatsApp has restricted the account, follow the review or appeal instructions shown by WhatsApp. WADial cannot remove a platform restriction.

## Practices to avoid

* Unsolicited bulk messaging or cold outreach to large contact lists.
* Rotating numbers or tokens to bypass a restriction.
* Randomizing text, timing, or formatting to imitate human activity or evade detection.
* Repeatedly messaging recipients who do not respond.
* Continuing after an opt-out, block, complaint, or persistent delivery error.
* Fraud, impersonation, harassment, prohibited content, or misleading claims.

## Launch checklist

* Recipient consent is recorded and purpose-specific.
* Opt-outs are processed before the next send.
* Per-recipient and per-token rate limits are configured.
* Retries use backoff and stable idempotency keys.
* Delivery failures and complaints trigger an automatic pause.
* Operators can stop outbound automation quickly.
* Message content and workflows comply with applicable law and the [WhatsApp Messaging Guidelines](https://www.whatsapp.com/legal/messaging-guidelines).

WADial is independent from WhatsApp and Meta and is not an official WhatsApp Business Platform provider. Review the [service disclaimer](https://wadial.com/disclaimer) before connecting a number.