STOP), or by stopping marketing messages from your business in WhatsApp itself. The two work differently, and you need to respect both.
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 on each marketing send. Flowella doesn’t add those people to the Opt-outs page. See Opt-outs.Meta’s opt-in rules
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
Two ways people opt out
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
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.
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.

