WaSparks A customer gets your festive offer and replies “STOP.” The message arrives in the inbox, and an agent sees it. Everyone assumes someone will remove the customer from the list. Nobody does. Two weeks later the next campaign goes out, and the same customer receives it. This time they do not reply. They block the number and report it.
One report is a small thing. Many of them move your quality rating from green to yellow. The cause was not a bad offer. It was an opt-out that nobody acted on.
Why opt-outs matter so much
Customers expect to be able to leave. If they cannot stop messages easily, they will block or report instead.
Reports damage your number. Blocks and reports weigh on your quality rating, which can slow your messaging limit growth and put your number at risk.
Meta’s rules require consent and respect for opt-outs. Check Meta’s current business messaging policy for exact wording.
It is simple to get right. Unlike many compliance problems, this one has a clear fix.
Where manual processes fail
The opt-out is seen but not recorded. A reply sits in the inbox among hundreds of chats.
The list lives in a spreadsheet. Someone uploads an old file for a new campaign, and the opted-out customer is back in it.
Several people send campaigns. Each one has their own copy of the list.
Staff change. The person who knew to check has left.
The rule: opt-out applies everywhere, at once
A customer who says stop should be excluded from every future campaign on your account, not just the one they replied to. That needs to happen automatically, because relying on memory fails.
In WaSparks, a customer who replies STOP is left out of every future campaign automatically. You do not need to check lists by hand. If you import a list from another system, still review it for contacts who never opted in.
The SOP
Before sending
- Collect clear opt-in. Record where and when each customer agreed.
- Say who you are and why you are messaging. A clear first line reduces reports.
- Include an easy opt-out line where it suits the template, such as “Reply STOP to opt out.”
When someone replies STOP
- Do not argue or try to win them back. Do not send a follow-up asking why.
- Confirm only if appropriate. A short acknowledgement is fine inside the 24-hour window.
- Check that they are excluded from future campaigns. In WaSparks, that happens automatically.
- If they later opt in again, record the new consent clearly.
When you import lists
- Remove anyone who never opted in.
- Cross-check against your known opt-outs from other tools or old sheets.
- Start with recently engaged customers.
Monthly review
- Check your quality rating and messaging tier in the app.
- Look at the rate of STOP replies per campaign. A rising rate means the content or the audience needs attention.
- Review failed or blocked sends and note patterns.
See it live: Message our demo number and see how a reply lands with the team. Tap here to test on WhatsApp (replies in under 5 seconds)
What a high STOP rate tells you
STOP replies are feedback. If many customers opt out after a specific campaign, ask:
- Was the list the right audience?
- Was the message too frequent or too pushy?
- Was the offer relevant to them?
- Did customers expect to hear from you at all?
Fixing those causes does more for your number than any technical setting.
Keep customers who want to hear from you
A STOP is not always a loss. Some customers want fewer messages, not none. Offer choices at sign-up, such as order updates only, or offers only, so customers can pick what suits them, and send only what they chose.
The takeaway
Honour every opt-out, everywhere, immediately. Automate it so it does not depend on anyone’s memory, review your imported lists, and watch your STOP rate as a signal. To see how campaigns handle opt-outs, read the features page or start free.
Found this useful? Share it with your team.