What actually happens when a customer replies STOP on WhatsApp

There is no platform-wide opt-out list

WhatsApp does not maintain a global suppression list that stops all business messages to a customer who replied STOP. A STOP reply is a message like any other — your system receives it and your system decides what happens next.

This surprises people, because email and SMS have regulations that put the burden on the sender in a highly visible way, and many email tools enforce unsubscribe centrally. On WhatsApp the obligation is real but the mechanism is yours to build.

The consequence is that opt-out handling is a feature of your integration, not a property of the platform. If nobody implemented it, nothing stops the sends — and an automation is the most likely thing to keep going, because it was configured to run on a schedule rather than to check a list first.

Why automation is the usual culprit

A person sending a broadcast campaign usually sees the STOP reply arrive and stops. An automation does not read the inbox — it runs a sequence against a list of contacts, so unless the sequence checks a suppression list at every send, it will message someone who opted out.

• The sequence was built before the opt-out happened. An enrolled contact keeps receiving steps unless something removes them mid-sequence.
• The suppression list exists but is not consulted. A STOP is logged, yet the broadcast and the workflow both read the original contact list instead.
• Enrollment is a snapshot. If a workflow copies contacts in at the start, later opt-outs never reach the copy that is being messaged.
• Multiple systems hold their own copies. A contact list in a spreadsheet, a CRM and the messaging platform can disagree about who has opted out.

What an opt-out implementation actually needs

Four things: detect the opt-out, record it durably, enforce it at every send rather than at campaign creation, and let the customer back in deliberately. Miss the third and the first two do nothing.

1. 1

   Detect the intent, not just the word

   STOP, STOP ALL, unsubscribe, remove me, don’t message me again and a local-language equivalent all mean the same thing. Matching only the literal string STOP misses the rest — and a customer who is ignored will often escalate rather than rephrase.

2. 2

   Record it against the contact, durably

   The record must survive being re-imported from a spreadsheet or re-synced from a CRM, otherwise the next import silently re-subscribes them.

3. 3

   Enforce at send time, not at list-build time

   Every outbound path — broadcast, workflow step, manual send — must check suppression immediately before sending. Checking once when a campaign is created is the single most common way an opt-out is defeated.

4. 4

   Define a deliberate re-opt-in path

   People change their minds. Decide how someone is added back — normally an explicit inbound request — and never by a bulk import quietly clearing the flag.

Should you confirm an opt-out?

One confirmation message is common and usually welcome; more than one is a violation of the request. The confirmation itself has to be permitted by the rules that govern what you may send.

If the customer has just messaged you, the customer service window is open and a free-form confirmation is possible. Outside a window — which is the case for a STOP that arrives long after your last campaign — the only permitted send is a template, so a confirmation may not be deliverable at all.

That asymmetry means the safest design is to record the opt-out first and treat the confirmation as optional. If the confirmation cannot be sent, the opt-out must still be enforced.

STOP is a keyword your routing must not swallow

If your automation routes inbound messages by keyword, an opt-out word must be checked before any other rule. A routing chain that treats STOP as unmatched and routes it to a fallback menu can leave the customer inside a flow they are trying to leave.

• Check opt-out keywords first, ahead of menus, flows and intent detection.
• Do not reply to an opt-out with a menu that requires another reply — that is another message the customer did not ask for.
• Remove the contact from active sequences, not only from future sends, so a workflow in progress stops.
• Keep a record of when and how the opt-out arrived — that is the evidence if the send is ever questioned.

Why this matters beyond compliance

Ignored opt-outs produce blocks and reports, and those feed back into your messaging quality rating — which governs how many people you are allowed to reach. Opt-out handling is therefore a deliverability concern, not only a legal one.

Quality rating is influenced by how recipients respond to your messages. A customer who said STOP and kept receiving messages has limited options: block the number, or report it. Both are negative signals.

The messaging limit that governs how many unique recipients you can reach is tied to that standing, so a pattern that annoys people eventually constrains reach for everyone on the account — including the customers who do want to hear from you.

Common questions

Related reading