Worked example: deciding between a short code and 10DLC
A national pharmacy chain sends millions of refill reminders and one-time passcodes each month. It leases a dedicated short code because it needs high throughput and a single recognizable number, accepting the longer carrier approval process and higher monthly lease cost.
For store-level conversations, where customers reply to a local pharmacist, it uses 10DLC numbers registered under a separate campaign. Both programs follow the same consent, opt-out and content rules; the difference is throughput, cost, approval path and whether customers recognize a local number.
Short Code Laws and Compliance
Short answer: There is no single statute titled “Short Code Law.” US short code programs must still follow TCPA/FCC consent rules in 47 CFR § 64.1200, carrier/CSP acceptable use policies, and CTIA industry monitoring principles such as the Messaging Principles and Short Code Monitoring Handbook. Short codes are not registered through The Campaign Registry’s 10DLC Brand/Campaign model.
Short Codes vs 10DLC vs Toll-Free
| Path | Identity | Registration model |
|---|---|---|
| Short code | 5–6 digit code | Lease + program approval / monitoring (not TCR 10DLC) |
| 10DLC | Local 10-digit | Brand + Campaign via TCR through CSP |
| Toll-free | 8xx number | Toll-free verification via CSP/carriers |
Twilio notes toll-free and short codes are not part of the A2P 10DLC system (A2P overview). Choosing a short code does not remove TCPA duties.
The Legal Layer (TCPA / FCC)
Whether you send from a short code or 10DLC:
- Marketing/telemarketing texts using covered technologies generally need prior express written consent
- Consumers may revoke consent by reasonable methods including STOP-style replies recognized in § 64.1200
- State laws may add requirements
“Short code laws” questions are usually TCPA questions plus program-specific carrier rules.
The Industry / Monitoring Layer (CTIA)
CTIA documents are best practices / monitoring standards, not statutes, but they heavily influence whether programs stay approved:
- Clear, program-specific opt-in
- Confirmation messages identifying brand/program, frequency, help path, opt-out, and rates language when applicable
- Robust STOP and HELP handling
- Accurate, non-deceptive content
- Documented consent records
CSP explainers (for example Telnyx’s HELP/STOP summary) echo these norms. Read the current CTIA handbook version your provider cites—handbooks revise over time.
Commercial / Provisioning Layer
Short codes typically involve:
- Leasing a random or vanity code through aggregators/CSPs
- Provisioning timelines measured in weeks (ask your CSP for current estimates—do not rely on blog folklore)
- Ongoing lease fees higher than typical 10DLC number rents (get a quote; fees change)
- Program brief / sample flows reviewed before launch
This article intentionally omits invented fee tables and universal SLAs.
Compliance Program for Short Codes
- Classify content — marketing vs informational templates
- Design PEWC where marketing applies; keep audit trails
- Implement keywords — STOP family + HELP with correct auto-replies
- Single opt-in ≠ multi-program enrollment — CTIA materials caution against enrolling consumers into multiple programs from one opt-in without proper consent design
- Monitor complaint and opt-out rates; remediate content quickly
- Keep terms & privacy publicly reachable
If volume does not justify short code cost/complexity, evaluate 10DLC or toll-free instead—see comparison drafts and MyTCRPlus video on 10DLC vs toll-free.
Common Myths
- “Short codes are exempt from TCPA.” False.
- “Short codes skip consent because they’re approved.” Approval ≠ consent.
- “Vanity codes are legally safer.” Branding ≠ legal safe harbor.
- “Migrating to 10DLC removes CTIA expectations.” 10DLC still expects consent, STOP/HELP, and truthful samples.
When to Prefer Short Code vs 10DLC
Lean short code when brand needs a memorable code, very high volume, or CSP advises it for the use case.
Lean 10DLC when local identity matters, volumes are moderate, or you want Brand/Campaign flexibility across multiple programs.
Either path: soft-check disclosures and samples with tools such as MyTCRPlus before launch reviews—no guarantees.
Program Brief Essentials
When your CSP asks for a short-code program brief, include:
- Brand legal name and consumer-facing name
- Program description and message frequency
- Opt-in mechanisms with URLs/screenshots
- Opt-out and help flows with exact auto-replies
- Example messages (including link domains you will use)
- Customer care contact path
- Privacy policy and terms URLs
Inconsistent briefs vs live traffic are a primary monitoring failure mode. Update the brief when marketing calendars change—not only at lease renewal.
Transfer and Sunset
If you retire a short code:
- Stop outbound traffic
- Keep STOP/consent archives
- Communicate alternate channels to customers
- Follow CSP lease termination steps so the code is not reused against your brand unexpectedly
Document sunsets in your compliance calendar alongside 10DLC Campaign reviews.
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
Are there specific “short code laws”?
No single dedicated federal “Short Code Act.” Compliance is TCPA/FCC + carrier/CTIA program rules + contracts.
Do short codes use TCR?
Not for the 10DLC Brand/Campaign registry model. Different provisioning path.
Is CTIA’s handbook binding law?
No—but ignoring it risks program suspension via monitoring/carrier action.
Can I use the same consent for short code and 10DLC?
Only if disclosures clearly authorize the channels/programs you actually use. Do not assume portability without review.
Disclaimer
This article is for informational purposes only and is not legal advice. CTIA handbooks, carrier rules, TCPA interpretations, and fees change. Confirm requirements with your CSP and qualified counsel.
Related guide: CTIA guidelines for SMS explained