SMS Program Compliance Guide
A practical compliance guide for running an SMS program: how to collect clear opt-in, include the right disclosures (frequency, rates, STOP/HELP), store consent proof, send a proper welcome message for recurring programs, and handle opt-out/help correctly.
SMS Program Compliance Guide (Opt-In, Disclosures, and Subscriber Rights)
Note: This article is for general informational purposes and is not legal advice.
What this guide is for
This guide explains how to set up an SMS program in a way that is audit-ready: clear consent, clear disclosures, and respectful subscriber controls (opt-out/help). U.S. rules and carrier expectations treat text messages as regulated communications, so it’s important to document consent and honor revocation properly.
1) Define your “program” before you send
Think of every SMS program as a bundle of:
-
Sender identity (brand name the user recognizes)
-
Purpose (appointments, account alerts, promotions, etc.)
-
Message type (marketing vs informational vs transactional)
-
Expected frequency
-
Support path (how a user gets help)
-
Opt-out method
A subscriber’s consent should apply only to the specific sender/program they agreed to—consent is not transferable to other programs or senders.
2) What your opt-in must clearly show
Your opt-in language should be clear and conspicuous and should not be hidden inside long-term text.
Include these items at the point of sign-up:
-
Program/brand name
-
What messages are about (purpose)
-
Message frequency disclosure (example: “Up to 4 msgs/month”)
-
Fees disclosure (example: “Msg & data rates may apply”)
-
How to opt out (STOP)
-
How to get help (HELP + support contact)
-
Links to Privacy Policy (easy to find)
Web form example
“By providing your number, you agree to receive SMS from [Brand/Program] about [purpose]. Msg frequency: [up to X/month]. Msg & data rates may apply. Reply STOP to opt out, HELP for help. See our Privacy Policy: [link].”
3) Acceptable opt-in methods (and what counts as proof)
Common opt-in methods include: web forms, texting a keyword, point-of-sale/on-site sign-up, or IVR/phone sign-up.
What to store as opt-in proof (recommended)
Keep records that show who opted in, when, how, and to what program:
-
Timestamp of consent
-
Consent method (web form, keyword, paper, IVR)
-
The exact language/action used to capture consent
-
Which program/campaign was the consent for
-
IP address (for web opt-ins), when applicable
-
Phone number that opted in
-
Identity marker (name, user/session ID), when applicable
4) Send a proper “welcome/confirmation” for recurring programs
If your program is recurring (not just a one-time response), send a confirmation message before you begin regular messaging.
A strong confirmation message includes:
-
Program name/description
-
Customer care contact (phone/email and/or HELP instructions)
-
How to opt out
-
Those messages are recurring + frequency
-
Any fees/charges disclosure
Copy/paste confirmation template
“[Brand/Program]: You’re subscribed to receive [purpose] texts. Msg freq [X/month]. Msg&data rates may apply. Reply STOP to opt out, HELP for help. Support: [phone/email].”
5) Opt-out and revocation rules you must follow
Subscribers must be able to revoke consent in any reasonable manner (not only one specific keyword), and requests must be honored within required timeframes.
Recommended implementation:
-
Accept standard opt-out keywords like STOP, and also common variants (end, unsubscribe, cancel, quit, etc.).
-
Send one final confirmation that the user has opted out, then stop messaging that program.
-
Ensure suppressions apply quickly and reliably (don’t keep sending after a revocation).
Copy/paste opt-out confirmation
“[Brand/Program]: You’ve opted out and will no longer receive messages from this program.”
6) “HELP” handling (customer care expectations)
When a user asks for help (HELP or a similar request), reply with:
-
Brand/program name
-
How to reach support (phone/email)
-
Where to find key info (optional: link to your SMS terms page)
-
Reminder that STOP opts out
Copy/paste HELP response
“[Brand/Program]: For help, contact [support phone/email]. Reply STOP to opt out.”
7) Privacy and security basics for SMS programs
Your privacy policy should be easy to access and clearly describe how you collect, use, and share consumer information, and it should be accessible from the initial opt-in experience.
Also, implement reasonable administrative/technical controls to protect subscriber data and review your practices periodically.
8) Register the traffic where required (10DLC / Toll-Free)
For business messaging in the U.S., registration is required independent of the route/use case (for example, 10DLC campaigns). Campaign registration typically requires describing your use case and providing representative message templates.
Quick “go-live” checklist
-
Opt-in language is clear and includes frequency, fees, STOP/HELP, and privacy link
-
You store opt-in proof fields (timestamp, method, language, program, phone, IP, where applicable)
-
Recurring programs send a proper confirmation before ongoing messaging
-
Opt-out is honored reliably, and revocation requests are accepted via reasonable methods
-
Registration completed where applicable
If you paste your current opt-in text (web form or keyword flow) and your welcome / HELP / STOP messages, I’ll rewrite them to match this structure and keep them consistent across your FAQ, Terms, and message flows.