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

# WhatsApp opt-in and opt-out rules for businesses

> What Meta requires before you message someone on WhatsApp, how people stop marketing messages in WhatsApp, and how Flowella's STOP keyword opt-outs differ.

Meta requires you to have a person's **opt-in** before you message them on WhatsApp. Since Meta's November 2024 policy update, that opt-in doesn't have to mention WhatsApp, as long as it names your business, makes clear the person is agreeing to hear from you, and meets the law where you and they are. People can opt out in two separate ways: by telling **you** (for example by replying `STOP`), or by stopping **marketing** messages from your business in WhatsApp itself. The two work differently, and you need to respect both.

> [!NOTE]
>
> **In Flowella.** Partly supported. Flowella records opt-outs, not opt-ins, so keep your own record of how and when each person opted in. Flowella opts people out automatically when they send `STOP` and similar keywords, and blocks every message to them from that number. WhatsApp's own marketing stop shows as [error 131050](https://knowledge.flowella.io/whatsapp/errors/error-131050.md) on each marketing send. Flowella doesn't add those people to the **Opt-outs** page. See [Opt-outs](https://knowledge.flowella.io/app/opt-outs.md).

## Meta's opt-in rules

| Requirement | What it means |
| - | - |
| Say what they're opting in to | The person must understand they're agreeing to receive messages from you. |
| Name your business | The opt-in must name the business that will message them. |
| Follow the law | You must meet the consent and notice rules that apply to you and to the person, such as data protection and direct marketing law. |

Meta accepts any opt-in method that meets those rules, for example:

* A website form or checkout tick box
* An SMS conversation
* A phone call, including an automated phone menu
* A signed form, in person or on paper

Meta also recommends making clear which kinds of message people will get (order updates, offers, reminders), and offering a separate opt-in for each kind. People who get messages they didn't expect block and report, which lowers your [quality rating](https://knowledge.flowella.io/whatsapp/limits/quality-score.md).

> [!WARNING]
>
> Meta's rules set a minimum. They don't replace your own legal obligations. Check what applies to your business with your legal adviser.

## Two ways people opt out

| | Opt out with your business | Stop marketing in WhatsApp |
| - | - | - |
| How it starts | The person replies with a keyword, asks you, or you add them to your suppression list | The person chooses to stop marketing messages from your business in WhatsApp |
| What it blocks | Whatever your business decides. In Flowella, every message from that number | Marketing templates only. Utility templates, authentication templates and replies still arrive |
| Who enforces it | You, through Flowella | WhatsApp. Marketing sends fail with **131050** |
| How it's reversed | The person sends `START` or `UNSTOP`, or your team selects **Re-opt in** | Only the person, by resuming marketing messages in WhatsApp |
| How you're told | The **Opt-outs** page and the HubSpot **Opted out of WhatsApp** property | A `user_preferences` webhook with `value` `stop` or `resume`, and 131050 on each marketing send |

WhatsApp also lets people mark offers as **Interested** or **Not interested** under **Offers and announcements**. That feedback doesn't trigger the `user_preferences` webhook.

## What Flowella does

| Situation | What Flowella does |
| - | - |
| A customer sends exactly `STOP`, `UNSUBSCRIBE`, `CANCEL`, `END` or `QUIT` | Records an opt-out for that WhatsApp number. See [How keyword opt-outs work](https://knowledge.flowella.io/app/opt-outs.md#how-keyword-opt-outs-work). |
| A customer sends `START` or `UNSTOP` | Re-opts them in on that number. |
| You send to an opted-out number | Blocks it in the Inbox, skips it in bulk sends and fails HubSpot actions with `CONTACT_OPTED_OUT`. See [What an opt-out blocks](https://knowledge.flowella.io/app/opt-outs.md#what-an-opt-out-blocks). |
| A marketing send fails with 131050 | Shows "This contact has opted out of marketing messages from your business. Do not retry marketing templates to them." HubSpot shows `FLOWELLA_META:marketing_opt_out`. The contact isn't added to **Opt-outs**. |
| Meta sends a `user_preferences` webhook | Flowella records it, but doesn't change the contact's opt-out status or notify you. |

Keyword opt-outs apply to each WhatsApp number separately. Someone who opts out on one of your numbers can still get messages from another, unless they opt out there too.

## What to do

**1. Record opt-in where you collect it**

Store how and when each person opted in, in HubSpot or your own system. Flowella doesn't store opt-in.

**2. Tell people how to opt out**

Include a line such as "Reply STOP to stop these messages" in marketing templates, and honour it.

**3. Suppress 131050 contacts from marketing**

After a marketing send fails with 131050, stop sending marketing templates to that person. In HubSpot, branch on the action's **Error code** output and add the contact to a suppression list. See [Error 131050](https://knowledge.flowella.io/whatsapp/errors/error-131050.md).

**4. Exclude opted-out contacts before you send**

In HubSpot, exclude contacts where **Opted out of WhatsApp** is **Yes**. See [Session window, opt-out and send status properties](https://knowledge.flowella.io/hubspot/contact-activity.md#session-window-opt-out-and-send-status-properties).

## Related

* [Opt-outs](https://knowledge.flowella.io/app/opt-outs.md)
* [Error 131050](https://knowledge.flowella.io/whatsapp/errors/error-131050.md)
* [Policy and enforcement](https://knowledge.flowella.io/whatsapp/messaging/policy-and-enforcement.md)
* [Quality rating](https://knowledge.flowella.io/whatsapp/limits/quality-score.md)

Checked against Meta's [Get opt-in for WhatsApp](https://developers.facebook.com/documentation/business-messaging/whatsapp/getting-opt-in) and [user\_preferences webhook](https://developers.facebook.com/documentation/business-messaging/whatsapp/webhooks/reference/user_preferences) pages on 18 November 2026.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.