Who This Is For / Who It Is Not For
Who this is for: US businesses, compliance owners, marketing ops, and product teams that send or enable A2P SMS and need practical registration, consent, or troubleshooting guidance tied to 10DLC/TCR and TCPA concepts.
Who this is not for: Readers seeking invented fine amounts, guaranteed approval rates, or universal throughput figures; purely P2P consumer texting with no application layer; teams outside US A2P rules who need only foreign-regulator advice.
Short answer: Under FCC rules implementing the TCPA—chiefly 47 CFR § 64.1200—businesses generally need documented consumer consent before sending covered autodialed/robotext traffic, with prior express written consent typically required for marketing/telemarketing texts. Opt-in is a legal consent concept. A2P 10DLC registration is a carrier identity concept. You usually need both for US commercial SMS programs.
Searches for “FCC SMS opt in regulations” point here: there is no single one-page “SMS-only code,” but Subpart L’s call/text delivery restrictions and consent definitions apply to text messaging as the FCC has interpreted the TCPA.
Worked example: three opt-in paths, one standard
A fitness studio collects consent three ways: a web form with an unchecked box, a keyword on front-desk signage and a verbal script used by sales staff. Each path carries the same disclosures: the studio's name, the message types, frequency, "Msg & data rates may apply", HELP and STOP, and where to find the terms and privacy policy.
Each path records evidence differently: form submissions with timestamps, keyword messages with the inbound text, and verbal consent with a CRM flag and a confirmation text. The confirmation text is the common record across all three.
Two Consent Levels You Will Hear About
| Standard | Typical use (high level) | Proof theme |
|---|---|---|
| Prior express consent | Certain non-marketing informational messages | Clear agreement to receive that type of message |
| Prior express written consent (PEWC) | Marketing/telemarketing using ATDS or artificial/prerecorded voice | Written agreement + signature + required disclosures |
Exact applicability turns on message content, technology, and exceptions in § 64.1200 (including limited nonprofit and health-care references). Classify templates with counsel—do not self-exempt because a message “feels helpful.”
Deep dive on PEWC: draft companion article on express written consent (same site cluster) and Cornell’s § 64.1200.
What a Compliant Opt-In Flow Usually Includes
While statutes do not read like a UX checklist, regulators, courts, and CSP reviewers converge on practical elements:
- Clear offer — what texts, from which brand, how often (or that frequency varies)
- Affirmative action — unchecked checkbox, keyword JOIN, signed form—not pre-checked
- Not required for purchase disclosure when PEWC applies
- Phone number captured and confirmed
- Link to privacy / terms where web opt-in is used
- STOP / HELP instructions in confirmations and ongoing messages
- Records retained for disputes and Campaign audits
CTIA’s Messaging Principles & Best Practices reinforce consent documentation and opt-out handling as industry expectations—not a substitute for the CFR.
FCC Opt-In vs CSP Campaign Opt-In
| Audience | What they care about |
|---|---|
| FCC / TCPA plaintiffs | Whether consent meets statutory/regulatory elements for the messages sent |
| CSP / TCR Campaign reviewers | Whether message_flow, samples, and public pages show a verifiable opt-in story |
Twilio’s Campaign requirements ask for a detailed message_flow (40–2049 characters), and when website opt-in is used, privacy language covering mobile number non-sharing, frequency, and “message and data rates may apply.” Passing Campaign review does not prove PEWC in court; failing review can still block traffic.
Helpful internals: msg & data rates disclosure, single vs double opt-in, consent evidence trail.
Common Opt-In Methods
- Web form with dedicated SMS disclosure and unchecked box
- Paper form at point of sale / intake
- Keyword text-in (START/JOIN) with confirmation reply
- QR code to a mobile-friendly consent page
- Verbal scripts for eligible informational programs—with recordings/CRM logs; generally not used for Marketing PEWC
Double opt-in (confirm YES after initial subscribe) strengthens proof for marketing lists even when not universally mandated.
Opt-Out Is Part of Opt-In Design
§ 64.1200 recognizes reasonable revocation methods, including STOP-style reply words listed in the rule. Design your platform to:
- Process opt-outs quickly
- Suppress future marketing sends
- Send a single confirmation of opt-out when appropriate
- Avoid “confirm you want to leave” loops that keep messaging after STOP
Lead Gen and Shared Consent Pitfalls
High-risk patterns:
- Bundling dozens of sellers in one consent under older lead-gen designs (see one-seller PEWC updates with counsel)
- Buying SMS lists without underlying consent records
- Converting email subscribers to SMS without a new authorization
- Using forgotten website footer language as the only “consent”
Soft Operational CTA
Before you lock copy, validate that Campaign packaging and public disclosures match—MyTCRPlus tools can help catch inconsistencies early. Still run final PEWC language past qualified counsel.
Building an Opt-In Proof Packet for Audits
When counsel, a CSP reviewer, or a carrier partner asks “how do people opt in?”, assemble:
- Screenshots of each capture UI (desktop + mobile)
- Hosted public URLs for privacy/terms/SMS program page
- Exact disclosure text with version dates
- Sample confirmation SMS (opt-in reply)
- Sample HELP and STOP automations
- Data dictionary for CRM consent fields
- Retention schedule for consent records
Store this packet beside your TCR Campaign IDs. When marketing copy changes, update both the consumer disclosure and the Campaign samples so they stay aligned.
Metrics That Signal Opt-In Problems
Watch:
- Sudden STOP rate spikes after a blast
- Spam complaint notifications from your CSP
- “Who is this?” inbound replies
- Mismatch between list source and Campaign description
These are operational signals—not legal conclusions—but they often appear before formal disputes. Pause, remediate consent, then resume.
How MyTCRPlus Can Help
Prepare Brand packets, public SMS disclosures, and pre-submission diagnostics with MyTCRPlus tools at https://mytcrplus.com/tools/ and related microsite options. They help you organize evidence for your CSP—they do not guarantee approval, throughput, or legal compliance. Pair preparation with the step-by-step TCR registration guide at https://mytcrplus.com/how-to-register-for-tcr/ and troubleshooting pages for unregistered traffic blocks when deliverability collapses.
FAQ
What are FCC SMS opt-in regulations?
Primarily the TCPA framework as implemented in 47 CFR § 64.1200 and related FCC orders—not a separate “SMS Act.” Texts are treated within that telemarketing/consent regime as interpreted by the FCC.
Do I need double opt-in?
Not universally required by the CFR for every use case, but it is a strong industry practice for marketing programs and helps Campaign credibility.
Is keyword STOP enough forever?
You must honor revocation. Keeping clean suppression lists matters as much as the keyword itself.
Does TCR registration satisfy opt-in requirements?
No. Registration and consent are separate.
Disclaimer
This article is for informational purposes only and is not legal advice. FCC rules, TCPA case law, carrier policies, and fees change. Confirm opt-in design with qualified counsel and your CSP before launching.
Related guide: SMS opt-in language templates