SMS Unsubscribe Message Examples and Templates
The unsubscribe flow is the most legally scrutinized twenty words in your entire messaging program. Get it right and it is invisible plumbing: people leave cleanly, your list stays healthy, and regulators have nothing to look at. Get it wrong, missing STOP handling, ignored revocations, no confirmation, and you are in the highest-volume category of Telephone Consumer Protection Act (TCPA) litigation there is.
This guide is a working template library: the opt-out language to include in your messages, the confirmation texts to send when someone leaves, the edge-case handling (HELP, partial opt-outs, resubscribes), and the current federal rules that dictate all of it.
Key takeaways:
- Every recurring message program needs opt-out instructions at enrollment and periodically thereafter; "Reply STOP to opt out" is the standard formulation under CTIA guidelines.
- Under FCC rules effective April 2025, revocation must be honored however reasonably expressed, not just via the word STOP, and processed within ten business days, with most platforms doing it instantly.
- The one message you may send after an opt-out is a single confirmation of the opt-out, promptly, with no marketing content.
- A good unsubscribe experience is a retention tool: people who leave easily rejoin; people who cannot leave report you as spam.
The rules behind the templates
Three layers govern SMS opt-outs in the United States:
- The TCPA (47 U.S.C. 227) requires consent for automated texts and gives consumers the right to revoke it, with statutory damages of 500 to 1,500 dollars per violating message, which is why continuing to text after an opt-out is the most expensive mistake in messaging.
- The FCC's revocation rules (adopted 2024, effective April 2025) codified what "revocation" means in practice: consumers may revoke consent through any reasonable means, including replies like STOP, QUIT, CANCEL, UNSUBSCRIBE, END, REVOKE, OPT OUT, and plain-language refusals, and senders must honor revocation within ten business days. Senders may send one immediate confirmation message, and may use it to clarify scope only if the consumer subscribed to multiple message types.
- CTIA Messaging Principles and Best Practices, the carrier-industry standard, expects opt-out instructions in the opt-in confirmation and recurring-message programs, universal STOP support, and immediate processing. Carriers enforce this through 10DLC registration and filtering, regardless of litigation.
Translation for practitioners: automate STOP and its synonyms for instant processing, monitor replies for free-text refusals ("please stop texting me"), and never let scope-clarification become a retention tactic.
Opt-out language inside your messages
Opt-in confirmation (the compliance workhorse), sent when someone subscribes:
[Org name]: You are subscribed to [program] alerts, up to [N] msgs/month. Msg and data rates may apply. Reply HELP for help, STOP to cancel.
Recurring campaign messages, append periodically (many programs include it in every promotional message):
Reply STOP to opt out.
Short form for tight character counts:
Txt STOP to end.
Event or seasonal program, with a natural end:
[Org name]: [Message]. These updates end after [event date]. Reply STOP anytime to leave early.
The placement rule of thumb: opt-out language appears in the opt-in confirmation, in the first message of any new program, and at regular intervals in recurring sends. Transactional streams (appointment reminders, receipts) carry it less frequently but must still honor every opt-out instantly. The full consent-side picture, what you must say at signup, lives in the SMS opt-in and opt-out requirements guide.
The confirmation message: your one allowed reply
When someone texts STOP, you send exactly one message: a confirmation. It must be prompt, free of marketing, and final.
Standard confirmation:
[Org name]: You have been unsubscribed and will receive no more messages from us. Reply START to resubscribe. For help: [support contact].
Warmer variant (nonprofits, churches, community organizations):
[Org name]: You are unsubscribed, no more texts from us. Thank you for being part of this community. If you ever want back in, just reply START.
Multi-program clarification (only when the person is genuinely enrolled in multiple message types; the FCC permits one clarifying message):
[Org name]: You are unsubscribed from donation updates. You still receive event reminders. Reply STOPALL to end all messages from us.
If the recipient does not answer a clarification, treat the revocation as applying to everything. The clarification exists to serve the subscriber's intent, not to salvage the subscription.
HELP response (the companion keyword every program needs):
[Org name]: This number sends [program description], up to [N] msgs/month. Support: [phone/email/site]. Reply STOP to cancel.
Edge cases and how to handle them
| Situation | Correct handling |
|---|---|
| Free-text refusal ("stop texting me pls", "remove me") | Treat as revocation; process like STOP. Automation should flag phrases, and humans or an AI Powered Helper should catch what keyword filters miss |
| STOP sent to a transactional stream | Honor it; move critical notices to a fallback channel (email, phone) and document the choice |
| Opted-out number texts you a question later | Inbound questions may be answered; it does not restore campaign consent. Invite START if they want messages again |
| Resubscribe request | Require an affirmative START (or fresh opt-in), confirm it, and log the new consent with timestamp |
| Number recycled to a new owner | Honor "wrong person" replies as opt-outs and scrub against the FCC's Reassigned Numbers Database where appropriate |
| Opt-out arrives by email or phone instead of SMS | Reasonable-means revocation counts across channels; process it against the SMS list too |
Every path above shares one requirement: logging. Consent records and revocation records, with timestamps and message copies, are what turn a compliance dispute into a two-line email.
Writing unsubscribes that help retention
It sounds backwards, but the exit is a marketing surface, just not the way retention-hack folklore suggests:
- Make leaving instant and total. The subscriber who leaves in one reply remembers you as respectful; the one who had to fight marks you as spam, which damages deliverability for everyone else on your route.
- Offer a downshift before the door, in your messages, not after STOP. "Getting too many texts? Reply MONTHLY for just our monthly digest" is a legitimate frequency option while subscribed. After a revocation, honor it; do not counteroffer.
- Leave the light on. A warm confirmation with "reply START anytime" outperforms guilt in every audience worth keeping.
- Read your opt-out data. Spikes after particular messages are your audience annotating your content calendar; autoresponder plumbing and keyword logic are covered in the SMS autoresponder setup guide.
Frequently asked questions
What should an SMS unsubscribe confirmation say?
One short message: confirmation that the person is unsubscribed and will receive no further texts, an optional resubscribe path ("Reply START"), and support contact if needed. No marketing, no incentives, no "are you sure", and nothing further after it.
Is "Reply STOP to opt out" legally required in every text?
Opt-out instructions must appear in the opt-in confirmation and recur in ongoing programs under carrier standards; many senders include them in every promotional message for safety. Regardless of what any message says, STOP and other reasonable revocations must always work.
What words count as an opt-out besides STOP?
Under FCC rules effective April 2025, revocation made by any reasonable means counts: STOP, QUIT, END, CANCEL, UNSUBSCRIBE, REVOKE, OPT OUT, and free-text refusals like "please stop texting me." Programs should automate the keywords and monitor replies for the rest.
Can you text someone after they unsubscribe?
Only once: a prompt confirmation of the opt-out, optionally clarifying scope if they were enrolled in multiple programs. Beyond that, texting a revoked number invites TCPA statutory damages of 500 to 1,500 dollars per message. Inbound questions from the person may still be answered.
How fast must an opt-out be processed?
FCC rules allow up to ten business days, but modern platforms process STOP instantly and automatically, which is the standard to hold your vendor to. Slow manual processing is where violations, and lawsuits, actually happen.
Conclusion
The unsubscribe flow is where your program tells the truth about itself: either leaving is as easy as joining, or the whole consent story was decoration. Automate every exit word, confirm once and warmly, log everything, and treat rising opt-outs as feedback instead of failure. Lists built on easy exits are smaller on paper and stronger everywhere it counts: deliverability, engagement, and the regulator-proof records behind them.
Want opt-in, opt-out, and every keyword handled automatically? Contact the FRANSiS team to see compliant messaging flows with instant STOP processing, consent logging, and two-way conversations built in.
