← All terms

    What Is 10DLC? The Complete 2026 Guide to A2P SMS Registration

    Updated April 2026·By OptInFix Compliance Team
    TL;DR

    10DLC (10-Digit Long Code) is the US carrier-mandated framework that lets businesses send Application-to-Person SMS from a local 10-digit number. To send legally in 2026, every brand must register with The Campaign Registry (TCR), submit at least one approved campaign, and continuously demonstrate TCPA-compliant consent.

    Key takeaways

    • 10DLC is mandatory for almost all US business SMS — including transactional, 2FA, and reminders.
    • Compliance has two steps: brand registration (the company) and campaign registration (the use case).
    • Carriers (T-Mobile, AT&T, Verizon) throttle, fine, or fully block unregistered or mismatched traffic.
    • Your TCR trust score directly controls throughput and per-message fees.
    • Every campaign needs a publicly accessible opt-in URL with TCPA-grade consent proof.

    10DLC Definition

    10DLC (10-Digit Long Code) is the US wireless industry's official path for sending Application-to-Person (A2P) SMS from a standard 10-digit local phone number — for example, (415) 555-0142.

    Before 10DLC, businesses sending SMS from a local number were treated as Person-to-Person (P2P) traffic. Carriers caught this in 2020–2021 and rolled out 10DLC: a registration system that gives sanctioned A2P traffic higher throughput, deliverability, and protections — and aggressively filters everything else.

    If a US recipient's number is on T-Mobile, AT&T, or Verizon (covering >95% of US mobile users), unregistered or mismatched 10DLC traffic is heavily filtered, fined, or blocked outright.

    Why 10DLC Matters in 2026

    Three forces converged to make 10DLC unavoidable:

    • Carrier enforcement: T-Mobile and AT&T now apply per-message fees and daily caps based on registration status and trust score. Unregistered traffic is filtered before delivery.
    • TCPA litigation: TCR registration is increasingly treated as table-stakes evidence of compliance. Defendants without it look reckless.
    • FCC consent revocation rule (2024): STOP/HELP keyword handling and 10-business-day suppression are now federally codified, and enforced through 10DLC violation notices.

    The practical result: even a small business sending 50 appointment reminders a day must be registered, or messages will silently fail.

    How 10DLC Registration Works (Step by Step)

    1. Pick a Campaign Service Provider (CSP) — Twilio, Bandwidth, GoHighLevel's LeadConnector, etc. The CSP submits your data to TCR on your behalf.
    2. Brand registration: Submit legal name, EIN, address, and website. TCR matches against IRS records.
    3. Brand vetting (optional but recommended): Pay a one-time fee for "Standard" or "Vetted" status — unlocks higher throughput.
    4. Campaign registration: Declare the use case (Marketing, Customer Care, 2FA, Account Notifications, Mixed). Submit sample messages, an opt-in URL, and STOP/HELP language.
    5. TCR review (1–7 business days): TCR + the CSP review opt-in flow and may reject for missing disclosures.
    6. Carrier approval (parallel): T-Mobile manually reviews high-volume campaigns. Approval signals readiness to send.
    7. Ongoing monitoring: Carriers profile your traffic. Pattern mismatch (e.g., Marketing campaign sending OTPs) triggers suspension.

    10DLC Costs in 2026

    Costs split across three layers:

    • One-time TCR brand fees: ~$4 brand registration; $40 (Standard) or $1,500 (Enhanced) brand vetting.
    • Recurring TCR campaign fees: $1.50–$10/month per campaign depending on use case.
    • Per-message carrier surcharges: $0.0025–$0.01 per segment, on top of your CSP's send fee.

    Unvetted brands pay higher per-segment fees and get throttled to ~75 messages/sec/campaign or less. Vetted brands can hit 4,500 SMS/min on a single campaign.

    Top 5 Reasons 10DLC Campaigns Get Rejected

    • Legal name vs EIN mismatch — submitting a DBA when the EIN is held by the parent LLC. Fix: 147c letter from the IRS.
    • Opt-in URL hidden behind login or JS-only render — TCR reviewers and crawlers can't see the consent flow.
    • Missing "Msg & data rates may apply" disclosure on the consent surface.
    • Pre-checked SMS consent box — must be unchecked and separate from email consent.
    • Use-case mismatch — submitting Marketing but sending appointment reminders, or vice versa.

    10DLC Compliance Checklist

    • Register your brand and at least one campaign with TCR through your CSP.
    • Use a publicly indexable opt-in page that shows the brand name, an unchecked SMS consent checkbox, "Msg & data rates may apply," and STOP/HELP language.
    • Capture timestamped, IP-logged, hash-locked consent proof for every opt-in.
    • Process STOP within 10 business days (immediate is industry standard) and maintain a per-brand suppression list.
    • Match your campaign use case to actual sending behavior — don't blend marketing into a 2FA campaign.
    • Re-vet your brand annually; review trust score quarterly.

    Examples

    Compliant 10DLC opt-in
    [ ] Yes, send me SMS updates from Acme Co. By checking this box, I agree to receive marketing text messages at the number provided. Msg frequency varies. Msg & data rates may apply. Reply STOP to cancel, HELP for help. Consent is not a condition of purchase. View our Terms and Privacy Policy.

    Separate, unchecked checkbox; brand name; rate, frequency, STOP/HELP, and consent-not-required language all present.

    Non-compliant opt-in
    [x] By submitting this form I agree to receive emails and texts from Acme Co.

    Pre-checked, bundles email + SMS consent, no rates/STOP/HELP/frequency. Will be rejected by TCR and is risky under TCPA.

    Generate a TCR-ready opt-in URL in under 2 minutes

    Frequently asked questions

    Related reading

    Related glossary terms

    Generate a TCR-ready opt-in URL in under 2 minutes