> For the complete documentation index, see [llms.txt](https://docs.sprinthub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinthub.com/en/strategies/whatsapp/problems-with-whatsapp/blocks-and-bans-on-whatsapp-i-received-a-policy-violation-notice-now-what.md).

# Blocks and Bans on WhatsApp: I received a policy violation notice, now what?

Receiving an email from Meta informing you that your WhatsApp Business account has been identified as sending spam is a critical red flag. This notice indicates that your number is on the platform's automated security systems' "radar" and that the next step could be a permanent ban.

In this guide, we explain what to do to protect your operation and how to adjust your automations to avoid losing your support number.

***

### 🛑 What should you do immediately?

If you received this notice, the first rule is: slow down. Meta's system detected unusual behavior or a high volume of user complaints.

* Pause the broadcasts: Immediately stop any mass sending flow to customers who haven't interacted with you in the last 24 hours.
* "Let the dust settle": Keep the number only for organic support for a few days. This helps normalize your account's health score with WhatsApp's servers.

***

### ✅ Good Practices and Safe Automations

To prevent new notices from occurring, you need to change the logic of how your company starts conversations.

#### 1. Always use Opt-in

Never send messages to anyone who has not explicitly authorized contact. Opt-in is the customer's confirmation that they want to receive your communications. Sending to cold lists is the fastest path to a ban.

#### 2. Prefer Reactive Automations

Instead of being proactive and "intruding" into the customer's chat, set up automations that depend on an initial action from the lead.

* Entry Triggers: Configure your chatbot to start only when the "lead opens a new support request" or when the "lead sends a message".
* Focus on Customer Service: Automations aimed at support and questions (where the customer seeks out the company) have virtually zero risk of being flagged as spam.

***

### ⚠️ The Risk of Unofficial Integrations

Regarding the use of WhatsApp Web (integrations such as Uazapi, Z-API, and others). It is important to understand that:

**Integrations that emulate WhatsApp Web are not approved by Meta. Using these tools carries the risk of a ban, as the system detects browser "emulation" behavior for automation.**

If you use the options available in our WhatsApp Web tab, your account is susceptible to Meta's scans, especially if there is a high volume of messages.

***

### 🏆 The Ultimate Solution: WhatsApp API

The only alternative to eliminate the risk of a ban for "using unauthorized software" is migrating to the [WhatsApp API](/en/topics/system-settings/account-settings/whatsapp-api.md).

* Approval: It is Meta's official integration for businesses.
* Scalability: Allows sending at scale with official support.
* Security: Your number is verified and follows the platform's rules, ensuring full stability for your sales and support operation.