Handling STOP, HELP and Opt-Out Management the Right Way
How US businesses handle opt-out and help keywords across channels, keep suppression lists clean, and avoid texting someone who already asked you to stop.
In this article
Handling STOP, HELP and Opt-Out Management the Right Way
The worst message a US business can send is one to a customer who already asked it to stop. It is a compliance problem, it is an instant complaint, and it is almost always an accident — the contact opted out through the campaign tool, and three weeks later somebody sent them a reminder from the CRM, which never got the memo. Opt-out management is not a single setting. It is a discipline that has to hold across every system capable of sending a message.
In US business texting, STOP and HELP keyword handling is baseline expected behavior: carriers and messaging providers treat automatic keyword processing as standard, honoring an opt-out is a legal expectation for marketing traffic, and customers judge you on how cleanly it works. Get it right and it is invisible. Get it wrong and it surfaces at the worst possible moment.
This guide covers what each keyword should do, how to keep a suppression list clean across tools, the difference between opting out of marketing and opting out of service updates, re-subscribe flows, and the cross-system leaks that cause accidental sends.
The keywords and what your system must do
| Keyword typed by the customer | Correct system behavior | Confirmation sent |
|---|---|---|
| STOP | Immediately suppress all marketing to that number; flag the contact | One confirmation, then nothing further |
| STOPALL | Suppress everything from that sender, including service traffic | One confirmation |
| UNSUBSCRIBE, CANCEL, END, QUIT, OPTOUT | Treat exactly like STOP | One confirmation |
| HELP, INFO | Send business identity, contact info and how to opt out | Immediate help reply |
| START, UNSTOP, YES (in an opt-in context) | Re-subscribe, log new consent with timestamp | Confirmation of resubscription |
| Free-text requests: "stop texting me", "take me off this list", "no more messages" | Detect and treat as an opt-out | Confirmation, plus flag for review |
| Spanish or other-language equivalents ("PARAR", "BAJA") | Accept as opt-out triggers | Confirmation in the customer's language |
| Anything else | Route to the inbox as a normal conversation | Normal reply |
Two rows deserve emphasis. Free-text opt-outs are the ones platforms miss: a customer who writes "please stop texting me, I've asked twice" has opted out just as clearly as one who typed STOP, and if your system only matches exact keywords, the request goes into the inbox and gets forgotten. Configure detection for natural-language opt-out phrasing and flag those conversations for a human to confirm.
And case and whitespace do not matter. "stop", "STOP", " Stop " and "Stop." must all work. So should a STOP that arrives on a channel other than SMS — if someone asks you to stop on Instagram or WhatsApp, that is a request, not a channel-specific keyword.
Real message examples
Opt-out confirmation (correct): "You've been unsubscribed from Ridgeline Plumbing marketing texts and won't receive any more. Appointment and service updates will still come through. Reply START to resubscribe."
Full stop confirmation: "You've been unsubscribed from all Ridgeline Plumbing texts. If you need us, call (555) 018-2200 or email [email protected]. Reply START to resume texts."
HELP reply: "Ridgeline Plumbing — service and scheduling texts. Call (555) 018-2200 or visit ridgelineplumbing.example. Msg & data rates may apply. Reply STOP to unsubscribe."
Re-subscribe confirmation: "Welcome back — you're resubscribed to Ridgeline texts. Msg frequency varies. Reply HELP for help, STOP to unsubscribe."
Human follow-up after a free-text opt-out (optional, only if you have another legitimate channel): Do not text this. Note it in the CRM instead, and if a call is warranted, call.
Rules for the confirmation itself:
- Send exactly one. Multiple confirmations after an opt-out is the classic own goal.
- Confirm and stop. Do not use it to ask why, offer a discount, or attempt a save. That message is what turns an unsubscribe into a complaint.
- Be specific about scope. Tell them what stopped and what continues.
- Include the path back, briefly.
Marketing opt-out vs service opt-out
This is the distinction most senders handle badly. A customer who no longer wants promotions usually still wants to know when the technician is arriving or that their prescription is ready.
Model consent as separate scopes on the contact record:
- Marketing consent — promotions, campaigns, seasonal offers, re-engagement.
- Service/transactional consent — appointment reminders, order and dispatch updates, account notices tied to something the customer initiated.
- Global stop — the customer wants nothing at all by text.
When someone replies STOP to a marketing message, the safe and conventional interpretation is that marketing stops. When someone replies STOPALL, or says "stop all texts", everything stops and you should note an alternative contact method on the record.
Two implementation requirements: your confirmation message must say which scope stopped, and your service messaging must genuinely be service messaging. If your "appointment reminder" carries a promotional line at the end, you have collapsed the distinction yourself — see promotional vs transactional messages: what actually changes.
One suppression list, enforced everywhere
The suppression list is the single most important data structure in your messaging program, and it must be checked by every path capable of sending.
- Inventory every sender. Campaign tool, shared inbox, CRM workflows, reminder system, ecommerce notifications, review tool, AI agents, any n8n or Zapier automation, and every rep texting from a personal phone.
- Designate one system of record for consent status. Everything else reads or syncs from it.
- Check at send time, not at list build time. A list exported Monday and sent Thursday includes anyone who opted out in between.
- Match on normalized numbers. Normalize to E.164 everywhere, or formatting differences will bypass suppression.
- Suppress by person, not by record. Deduplicate before you send.
- Apply across channels where the request was clearly global. If someone asks you to stop on WhatsApp, do not keep texting them.
- Never allow a manual override. No "but this one's important" exception. Ever.
The cross-system leaks that cause accidental sends
These are the specific failure modes worth auditing for:
| Leak | How it happens | Fix |
|---|---|---|
| CRM workflow ignores suppression | Automation built by a different team, sends directly via API | Route every send through the platform that owns consent |
| Stale exported list | CSV pulled before the opt-out, sent after | Re-check suppression at send time |
| Duplicate contact records | Same person, two records, one flagged | Deduplicate on normalized phone number |
| Number formatting mismatch | Suppression stored one way, list another | Normalize to E.164 across all systems |
| New platform, un-imported list | Migration didn't carry suppression records | Import suppression before the first send |
| Rep texting from a personal phone | Nothing checks anything | Move all customer texting into the shared inbox |
| Third-party tool (reviews, surveys) | Separate vendor with its own list | Sync suppression to it, or send through your main platform |
| Re-import overwrites status | Bulk contact upload resets consent fields | Never let imports overwrite consent status |
The single structural fix that eliminates most of these: send everything through one platform that owns consent state. That is the strongest operational argument for consolidating messaging into a shared inbox rather than running four tools that each maintain their own idea of who unsubscribed. In Omnifox, opt-out status lives on the contact and is enforced across campaigns, automations, AI agents and manual replies alike.
Re-subscribe flows
People do come back. Make it possible without being pushy.
- Keep START working permanently. Never expire it.
- Log new consent with timestamp, source and the exact wording shown — the old consent record does not carry forward after an opt-out.
- Never solicit a re-subscribe by text to someone who opted out of texts. Use a channel they still accept: an email they subscribe to, the checkout flow, a form on your site, a conversation in person.
- Offer re-subscription at natural moments — a new purchase, a new service appointment, an account update — through the same opt-in collection methods you use for new contacts.
Audit trails: keep the receipts
If a customer disputes whether they consented or whether you honored an opt-out, the only useful answer is a record. Store, per contact:
- Consent status per scope (marketing, service, global)
- Consent timestamp, source and the exact disclosure wording they saw
- Opt-out timestamp, the keyword or phrasing used, and the channel
- Confirmation message sent, with timestamp
- Any re-subscribe events with the same detail
- Full message history for the number
Retain these for as long as your counsel advises, keep them exportable, and confirm before signing with any vendor that you can take these records with you — this is exactly the data that gets lost in a platform migration.
A monthly opt-out audit
Thirty minutes, once a month:
- Send a test STOP, HELP and START to each sending number and confirm the behavior and copy.
- Cross-check every message sent in the last 30 days against the suppression list for post-opt-out sends.
- Search inbound messages for free-text opt-out phrasing and confirm each was actioned.
- Check for duplicate contacts sharing a phone number.
- Confirm every sending tool in your inventory still reads from the system of record.
Honoring opt-out requests promptly is a legal expectation for marketing messages in the US, and business SMS is additionally subject to carrier rules — see text messaging compliance for US businesses and TCPA basics in plain English. This is general information, not legal advice; confirm your obligations with your own counsel.
Frequently asked questions
What keywords must a business text program respond to?
At minimum STOP and its variants, HELP or INFO, and START to resubscribe. Handle them case-insensitively, ignore punctuation and whitespace, and also detect plain-language requests like "stop texting me."
How fast do I have to honor an opt-out?
Immediately, in practice. Automated keyword handling should suppress the contact the moment the message arrives, and the confirmation should be the last message they receive. Manual processing is how accidental sends happen.
If someone opts out of marketing texts, can I still send appointment reminders?
Generally yes, when the reminder relates to something the customer initiated and carries no promotional content. Model marketing and service consent as separate scopes, say clearly in your opt-out confirmation what stopped and what continues, and confirm your approach with counsel.
How do I stop accidental messages after someone opts out?
Maintain one suppression list as the system of record, have every sending tool check it at send time rather than list-build time, normalize phone numbers, deduplicate contacts, and stop reps texting customers from personal phones.
Can a customer resubscribe after opting out?
Yes. Keep START working permanently, log the new consent with its own timestamp and source, and never solicit resubscription by texting someone who asked you to stop texting them.
Make it boring, then keep it boring
Good opt-out management in the US is unglamorous: automatic keyword handling, one confirmation, one suppression list every tool respects, separate marketing and service scopes, a working way back, and an audit trail that answers a dispute. Run the monthly audit and it stays that way.
Omnifox enforces opt-out status on the contact across campaigns, automations, AI agents and manual replies on every connected channel. Start a free trial.
Details verified on 14-09-2026 from each provider's public pages; they may change without notice. "Not native", "plan-dependent" or "via integrations" means that, as of that date, we did not find the feature in its public documentation or it depends on the plan. Sources: Zapier. Third-party names are trademarks of their respective owners and are cited for comparison purposes only.
Ready to try it in your business?
Bring WhatsApp, Instagram, Messenger, email and calls into one inbox, and let AI handle the first reply. Set it up today.
7 days free. No credit card required.
Read more
-

Best of Both Worlds: Your WhatsApp App + a Platform With the API
-

The Best Sales CRM in 2026
-

What Is Conversion Rate and How to Actually Improve It
-

Automated Customer Notifications on Telegram: A Practical Guide
-

How to Measure the ROI of Your Customer Service Team
-

AI + Human: The Hybrid Model That Delivers the Best CSAT in 2026
-

Inactivity follow-up: remind the customer and escalate to a human
-

WhatsApp messaging limits and how to increase them
Comments (0)
No comments yet. Be the first to share your thoughts.
Leave a comment
Your email is never published. Comments are moderated before appearing.