The A2P 10DLC registration process is the sequence that moves Application-to-Person (A2P) SMS on a United States 10-Digit Long Code (10DLC) from raw business data to approved The Campaign Registry (TCR) records. A Campaign Service Provider (CSP) submits the live file. Documentation can be assembled before that submit.
How to do A2P 10DLC registration is this same sequence. There is no separate A2P-only registry.
Step 1. Confirm A2P on US 10DLC
Confirm the from-number is a US 10-digit long code and the traffic is A2P. Short code and toll-free verification are different processes. Canadian domestic traffic is a different process.
Step 2. Select the CSP That Will Submit
Twilio, Bandwidth, RingCentral, Vonage, Sinch, Telnyx, Zoom, Amazon End User Messaging, and others expose their own consoles. mytcrplus.com does not become the CSP of record.
If you later change CSPs, reuse the evidence package. Re-key the new console.
Step 3. Assemble Brand Identity
Collect legal name, Employer Identification Number (EIN) or sole-proprietor identifier, address, contacts, and website. Align privacy and terms so they disclose SMS. EIN, name, and domain mismatches are a common first rejection.
Step 4. Submit Brand Registration
The CSP posts the brand to TCR. Clean files often return in 1–3 business days with a trust score from 0 to 100. Scores under 50 often enter 7–10 business days of manual review.
Step 5. Select One Use Case
Map production traffic to one TCR use case. Marketing, 2FA, account notifications, and customer care are different programs when copy and consent differ. Use-case misalignment is a large share of platform-reported rejections.
Step 6. Assemble Campaign Evidence
Write a description of at least 40 characters. Produce two samples with brand name and STOP. Document the opt-in. Add HELP language. Confirm privacy and terms URLs load without a login wall.
Validate consent language against Telephone Consumer Protection Act (TCPA) disclosure practice. Validate samples for SHAFT and carrier-restricted categories.
Step 7. Submit the Campaign and Freeze the Site
Standard use cases enter Direct Connect Aggregator review. Special use cases can add operator review. Campaign timing commonly spans 1–10 business days. Do not rebuild the opt-in during that window.
Step 8. Provision and Monitor
Map approved numbers to the approved campaign. Process STOP in near real time. Retain consent artifacts for four or more years. Re-file when the use case changes.
How to Get A2P 10DLC Registration
“How to get” and “how to do” queries resolve to this process. Initiate A2P 10DLC registration by opening the CSP console only after the evidence package is complete. Incomplete submits buy resubmission fees.
FAQ
Is the Twilio A2P 10DLC registration process different?
Field labels differ. The brand-then-campaign order does not.
Can the process be automated?
CSPs expose APIs that post fields. TCR and carrier review stay manual or queued. Automation does not skip identity checks.
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.