10DLC registration requirements are the identity, program, consent, and content inputs The Campaign Registry (TCR) and US carriers expect before they approve Application-to-Person (A2P) traffic on a 10-Digit Long Code (10DLC). Missing one layer is enough to reject the campaign.
This list is documentation practice. It is not legal advice. TCR and carriers keep discretion.
Brand Identity Requirements
- Legal name that matches IRS or state records
- Employer Identification Number (EIN) for standard brands
- Accepted sole-proprietor identifier when that path applies
- Website that loads and shows real contact details
- Privacy policy that covers SMS and data sharing
- Terms of service that disclose messaging
- Physical address, email, and phone for an authorized contact
- Industry vertical that matches the operating business
EIN, legal name, and domain mismatches are a frequent brand-rejection pattern. Fix the public site before the Campaign Service Provider (CSP) submits.
Optional trust-score supports include a D-U-N-S number filed before registration, domain age of six months or more, and consistent public reviews. None of those items replace exact legal identity.
Campaign Program Requirements
- One TCR use case that matches live traffic
- Campaign description of at least 40 characters
- Two sample messages
- Opt-in method and a description of how consent is captured
- STOP language in samples
- HELP language as a documented best practice
- Privacy policy URL
- Terms URL
- Frequency and cost disclosures where the program is promotional
Use-case misalignment is a large share of platform-reported rejections. Do not file marketing copy under 2FA. Do not file mixed programs on one campaign when the use cases are distinct.
Consent and TCPA Requirements
Telephone Consumer Protection Act (TCPA) consent sits beside the registry file.
Marketing programs need express written consent. Consent should be affirmative, purpose-specific, and not conditioned on a purchase for promotional programs. Pre-checked boxes fail that standard.
Retain timestamp and timezone, source IP or device ID, exact consent language, and the user response. Keep those records four or more years.
Nine disclosure checks used in consent validation:
- Business identification
- Message types
- Frequency
- Cost disclaimer
- Opt-out method
- HELP keyword
- Privacy policy link
- Terms of service
- Purchase independence for promotional programs
Content and Carrier Limits
Sex, Hate, Alcohol, Firearms, Tobacco (SHAFT) content is restricted. Extended carrier rules commonly prohibit cannabis and CBD, payday lending, debt relief, get-rich-quick schemes, and many crypto or NFT promotions.
T-Mobile, AT&T, and Verizon apply additional vertical scrutiny. Healthcare, insurance, financial services, and political traffic carry extra documentation load. Never promise a carrier outcome.
Website Requirements During Review
Do not rebuild the opt-in form or swap privacy URLs while Direct Connect Aggregator (DCA) review is open. Reviewers compare the live page to the filed campaign. A mid-review edit looks like a different program.
The site should resolve on desktop and mobile. Contact channels should work. Policy pages should not be login-gated.
Sole Proprietor Versus Standard Brand
Standard brands use EIN-backed identity. Sole-proprietor paths accept the identifier the CSP documents. Both paths still need a website story, consent language, and a campaign that matches traffic.
A sole-proprietor brand cannot carry an enterprise multi-EIN program. File the entity that actually sends.
Submission Package Checklist
- Brand worksheet with exact legal strings
- Screenshot or URL of the live opt-in
- Sample messages that include brand name and STOP
- Use-case selection memo
- Privacy and terms URLs
- Authorized contact who can answer vetting questions
- CSP account ready to submit
Run brand-consistency, use-case, consent, and message validation checks before the CSP posts the file. mytcrplus.com provides those diagnostics. It does not file as the CSP of record.
FAQ
What documents are required for 10DLC registration?
Legal identity, website and policy URLs, campaign description, samples, and opt-in evidence. The CSP may request more during vetting.
Are 10DLC registration requirements the same at every CSP?
Core TCR fields are shared. Console labels, upload rules, and invoices differ by CSP.
Do requirements change after approval?
Yes when the use case, legal entity, or public site changes. Update or re-file rather than drift.
Disclaimer
Mytcrplus.com provides tools and templates to support compliance efforts but does not provide legal advice. Compliance requirements vary by industry, jurisdiction, and use case. You are responsible for ensuring your messaging practices comply with applicable laws, obtaining appropriate consent from recipients, and monitoring ongoing compliance as regulations evolve. Consult legal counsel if you are unclear about your specific compliance situation.
MYTCRPLUS.com is not affiliated with The Campaign Registry. TCR and The Campaign Registry are trademarks owned by The Campaign Registry. The use of TCR is nominative use only.