Handling STOP and Unsubscribe Requests on WhatsApp the Right Way

Picture a gym that sends a Saturday offer to its member list. Within minutes, eleven people reply 'stop', 'STOP', 'please stop', 'remove me', and one 'who is this?'. The front desk reads them over the weekend. On Monday another offer goes out to everybody.

That Monday message is where a manageable situation turns into reports, blocks and a damaged sender reputation. Handling opt-outs is not paperwork. It is how you keep the channel usable.

Why this matters more on WhatsApp than on email

An email recipient who is annoyed usually marks it as spam or deletes it. A WhatsApp recipient can block you or report you from inside the chat in a couple of taps. Those signals feed the way your number is judged, which we cover in spam reports and quality rating. Ignoring a clear request to stop invites exactly that.

What people actually type

Do not assume people will write the exact word you hoped for. Real replies include:

• STOP, Stop, stop
• Unsubscribe
• Don't message me again
• Remove my number
• No more offers
• Enough!

A system that only recognises one keyword catches a fraction of them. The rest need either a person reading the inbox promptly or broader matching, with a human check for borderline ones. If someone clearly wants out, treat it as out, whatever the spelling.

A workable process, step by step

1. 1Tell people how to leave in the first marketing message they receive, and in your opt-in wording. Something like 'Reply STOP to stop these messages.'
2. 2Mark the contact as opted out the moment you see the request. Not at the end of the week.
3. 3Remove them from every campaign list and automation, not just the current one.
4. 4Send one short confirmation: 'Done, you won't get promotional messages from us again. Reply START if you change your mind.'
5. 5Keep the record, with date and the words they used.
6. 6Let them back in only if they ask, using START or a fresh opt-in.

Step 4 deserves a note. A confirmation is courteous and tells you the system worked. Keep it to one message and do not use it to try to win them back with a discount. That defeats the point.

What stopping does and does not cover

Someone opting out of promotions is not necessarily opting out of everything. A customer who says STOP to offers may still need to hear that their order has shipped. Be clear in your own policy about which categories an opt-out covers, and tell people. If it is unclear, the safest default is to treat STOP as a stop to everything non-essential, and to confirm what you will still send.

What automation can do for you

Hand-processing STOP is fine at ten contacts and a liability at ten thousand. In the Meta CRM within WA Getway, STOP and START replies are handled automatically: a STOP flips the contact's opt-out and a START restores it, and campaigns go only to opted-in contacts, so a stopped contact does not get the next one. That is the behaviour we built it to guarantee.

It applies to the official Meta route. If you run a QR-based connection instead, you need your own process for opt-outs, and you need to be stricter about it, since those numbers are already exposed to ban risk. We compare the two in Meta Cloud API vs QR gateway.

Making the exit easy is good business

It is tempting to hide the unsubscribe path to keep numbers up. The list that results is padded with people who ignore you, which drags down every metric you care about. A smaller list of willing readers beats a big list of resentful ones. We'd rather you have 800 people who open than 5,000 who report.

Take a small example. A salon with 600 contacts that quietly drops the 40 who asked to leave sends to 560 willing people. The one that keeps messaging all 600 sends to 560 plus 40 who now actively dislike it, and those 40 are the ones who report.

That also changes how you think about the other end. Good consent at the start means fewer exits later. Read how to collect opt-in without killing conversions alongside this one.

If you are building your own flow

Keep the logic boring and testable. Match several phrasings, log everything, apply the change immediately and write a test with ten messy examples before going live. If your systems are tangled and you want someone to wire opt-out handling across billing, CRM and WhatsApp, we do that kind of integration work.

The simple version: when someone says stop, stop, and make it effortless for them to come back.