Terms in this channel
SMS
A2P 10DLC
T-Mobile-scoped 10DLC registration guidance.
Read the answerSMSCTIA messaging principles
Voluntary CTIA messaging guidance and opt-out expectations.
Read the answerSMSExpress written consent
Consent scope and recordkeeping boundaries.
Read the answerSMSSMS opt-in
SMS permission scope and records.
Read the answerSMSSMS opt-out
SMS opt-out handling and reasonable revocation methods.
Read the answerSMSSMS quiet hours
Recipient-local-time boundaries in the cited US provision.
Read the answerSMSTCPA
TCPA scope and consent boundaries for covered messaging.
Read the answerSMSToll-free verification
Twilio US and Canada toll-free verification scope.
Read the answerWho this applies to#
- The cited US rules cover specified calls and texts, while CTIA guidance addresses non-consumer messaging programs and route providers apply their own approval scopes
What SMS compliance requires#
- Covered advertising or telemarketing messages require the applicable consent, quiet hours, and revocation handling described by current FCC rules
- CTIA guidance calls for consent and opt-out handling, while sanctioned 10DLC traffic to T-Mobile requires registration before campaign delivery approval
Audit structure
Separate federal legal rules, voluntary industry guidance, and route approval before assigning an operational control
What this does not require#
- CTIA guidance is voluntary industry guidance rather than a federal statute, and 10DLC registration is specific to that messaging route
Common mistakes#
- Presenting CTIA guidance as federal law
- Treating a route approval as a substitute for recipient consent
SMS compliance checklist#
- Identify the message purpose and the recipient's local jurisdiction
- Preserve consent and revocation evidence
- Confirm the approval status of the number and route used to send
OnVoard's take#
Check each gate. Start with legal permission, then review industry practice and carrier approval separately. Passing one does not prove the others passed.