Every business currently using a 10-digit local number to send promotional messages, appointment reminders, or transactional alerts to U.S. subscribers is operating within the A2P 10DLC framework—whether they have acknowledged it formally or not. Since February 2025, AT&T, T-Mobile, and Verizon enforce hard blocking on unregistered long-code traffic. Campaigns that have not completed the required brand and use case registration with The Campaign Registry no longer reach subscribers at all. This 10DLC 101 guide covers the core architecture of the system: what registration actually requires, how carriers evaluate campaigns once registration is submitted, where the process breaks down for organizations that treat compliance as a one-time form submission, and what a properly built registration foundation looks like. For broader context on the regulatory ecosystem, the TCR 101 resource library covers the Campaign Registry structure alongside regulatory glossary and A2P/TCPA FAQ references.
What 10DLC Is and Why It Replaced Shared Short Codes
10DLC—10-digit long code—is the U.S. industry standard for application-to-person (A2P) messaging over local 10-digit phone numbers. It replaced the shared short code model that dominated business SMS through the mid-2010s, when a single 5- or 6-digit number served multiple unrelated businesses simultaneously. Carriers had no mechanism to distinguish a regional bank’s fraud alert from a spam campaign running on the same code. Filtering was inconsistent, deliverability was unpredictable, and complaint volumes accumulated against shared resources regardless of any individual sender’s behavior.
The A2P 10DLC framework emerged from a CTIA-led initiative formalized between 2019 and 2021. It requires every business sender to establish an individual verified identity and submit their messaging use cases for explicit carrier review before operating at scale. The Campaign Registry—TCR—serves as the central vetting authority. TCR does not approve or block individual messages. It issues trust scores and campaign approval statuses that carriers use as inputs to their own filtering algorithms. Passing TCR registration qualifies a sender for carrier evaluation; it does not guarantee deliverability on its own.
A2P messaging compliance therefore operates across two dimensions. The first is structural: establishing the legal and technical records that carriers require to classify traffic as legitimate business-to-consumer communication. The second is operational: maintaining active consent records, processing opt-outs within carrier-defined windows, and keeping deployed message content aligned with the approved use case. Both dimensions involve continuous obligations. TCR campaign status can be suspended when carrier-side monitoring detects pattern violations after initial approval. Organizations that treat 10DLC registration as a one-time submission encounter this dynamic when campaigns are suspended mid-cycle without warning.
The Registration Architecture: Brand, Campaign, and Use Case
10DLC registration operates in two sequential layers. Brand registration comes first, establishing the legal identity of the sending entity: company name, Employer Identification Number (EIN), physical mailing address, website URL, and industry vertical classification. TCR validates submitted brand data against external identity sources including IRS records and Dun & Bradstreet business verification. EIN mismatches between what is submitted and what external registries hold represent the single most common brand registration failure mode, generating rejection codes that stall the entire campaign registration pipeline by one to two weeks while the underlying data discrepancy is corrected and resubmitted.
Standard business entities—LLCs, S-Corps, C-Corps, and publicly traded companies—follow the primary registration pathway with access to the full throughput tier structure. Sole proprietors without an EIN follow a distinct pathway with lower initial documentation requirements but face default throughput constraints that cap daily sending capacity until TCR-approved enhanced vetting is completed, a process that typically requires an additional seven to ten business days.
The A2P 10DLC Brand and Campaign Registration Process in Detail
Campaign registration defines what the business intends to send and to whom. Each campaign represents a single messaging use case: customer service, appointment reminders, promotional marketing, two-factor authentication, delivery notifications, or one of several specialty categories including healthcare alerts and public safety. Every submission requires sample messages that accurately reflect what subscribers will receive, opt-in workflow documentation demonstrating how subscriber consent was obtained, and live links to a publicly accessible privacy policy and terms of service page that contains required TCPA disclosure language—including opt-out instructions, message frequency disclosures, and data rates notices.
SMS carrier compliance requirements also vary by platform. Each CSP—Twilio, Bandwidth, Telnyx, Vonage, RingCentral, and others—has a submission interface that captures fields in a different sequence and applies validation logic that differs across providers. A documentation gap that passes one provider’s form validation may trigger a campaign rejection on another. The provider-specific 10DLC registration checklists on MyTCRPlus detail exactly what each major CSP requires at submission, eliminating the most preventable submission errors before the application is filed.
How Carriers Evaluate 10DLC Campaigns: Trust Score and Filtering Logic
TCR assigns every registered brand a trust score that directly governs message throughput. Higher trust scores unlock higher daily and weekly sending limits. The score is calculated from brand identity confidence—how cleanly submitted data matches external verification records—as well as business entity type, use case classification, and historical sending behavior over time. New brands receive a baseline trust score that constrains throughput, typically around 2,000 messages per day, until sending history accumulates or enhanced vetting is approved through TCR’s identity verification pathway.
Each major carrier then applies its own filtering logic on top of TCR approval status. A campaign with confirmed TCR approval can still face content filtering when message patterns trigger carrier-side detection algorithms: repeated promotional URLs across message batches, content resembling SHAFT-prohibited categories (sex, hate, alcohol, firearms, tobacco), aggressive call-to-action language, or opt-out rate spikes above carrier complaint thresholds. The TCR Trust Score Preflight Simulator on MyTCRPlus allows compliance teams to model how their brand data and campaign parameters will likely score before filing with TCR, identifying specific data vulnerabilities that would suppress the baseline trust score and require post-registration remediation.
The carrier review layer operates independently of TCR status and is not surfaced in the TCR dashboard. A campaign displaying “Approved” status in TCR may still face message filtering at one specific carrier due to that carrier’s interpretation of its content policies. Accurately diagnosing this requires number-level deliverability monitoring—tracking delivery confirmation rates per carrier network per sending window—rather than relying solely on TCR dashboard status as confirmation of successful delivery.
Use Cases, Throughput Tiers, and Restricted Categories
TCR defines a fixed taxonomy of approved use case types. Standard categories include marketing, customer care, two-factor authentication, polling and voting, and account notification. Specialty categories—available to qualifying verticals—include healthcare alerts, emergency communications, and public safety. Each use case type carries associated throughput tiers and content governance rules. Selecting the wrong use case is not a minor administrative correction. Misclassifying messaging purpose—for example, registering transactional order updates under a marketing use case to access a higher volume throughput tier—violates TCR terms of service and can result in campaign suspension and brand trust score reduction that degrades throughput access across every campaign under that brand registration.
Certain industries are categorically excluded from 10DLC. Cannabis, CBD, retail firearms, payday lending, and third-party lead aggregation using shared opt-in lists are prohibited use cases under CTIA guidelines. Businesses in adjacent industries frequently discover their specific model falls within a restricted class only after filing and receiving a rejection. Identifying restricted category boundaries before initiating registration prevents fees from being consumed by campaigns that cannot clear TCR review.
10DLC Registration Requirements for Small Business
10dlc registration requirements for small business vary by entity type. A sole proprietor texting appointment reminders to an established client base faces different throughput constraints and documentation requirements than a mid-market e-commerce operator sending transactional notifications at volume. Business text messaging requirements are not uniform across entity classifications. They are governed by the combination of entity type selected at brand registration, the use case category assigned at campaign registration, and the specific CSP handling the submission. Sole proprietors who complete enhanced vetting through TCR can access higher throughput tiers, but that process adds seven to ten business days to the registration timeline and requires additional identity documentation beyond what standard brand registration collects.
Where 10DLC Registration Breaks Down
10dlc compliance requirements checklist 2025 enforcement reflects a fully hardened policy environment. Since February 2025, unregistered A2P long-code traffic is hard-blocked across AT&T, T-Mobile, and Verizon simultaneously. There is no throttle-then-block transition period remaining. Any business that has not completed registration faces complete message delivery failure until brand and campaign registration is finalized and approved by TCR.
The majority of 10DLC campaign registration failures trace to four consistent patterns. First, brand data inconsistency: EIN, legal name, or address submitted to TCR does not match the records that TCR’s identity verification layer checks against, generating a brand rejection that blocks all downstream campaign submissions until corrected data is resubmitted. Many compliance teams discover this only after campaign registration is filed, not during brand submission, because TCR’s vetting timeline varies and discrepancies are not always surfaced in real time.
Second, opt-in documentation gaps: the consent workflow URL submitted at registration points to a page that either lacks required TCPA disclosure language or has been redesigned since submission. Carrier spot-checks against the live opt-in URL post-registration will surface this. A campaign approved with a compliant opt-in URL that is subsequently changed can lose its approval status without advance notice.
Third, sample message misalignment: content samples submitted at campaign registration do not reflect the actual messages being deployed. This is among the most common triggers for carrier-level content filtering after TCR approval—particularly for marketing campaigns that update promotional offers or call-to-action language after initial submission without updating the registered campaign record.
Fourth, use case miscategorization: the selected use case type does not accurately reflect the messaging purpose, generating TCR rejection codes that require a corrected resubmission with the appropriate use case selected and an additional registration fee assessed. Each of these failures is preventable through pre-submission validation against current TCR and carrier standards before any application is filed.
Moving Forward with 10DLC
Understanding how to register a 10dlc campaign with TCR accurately on the first submission eliminates the rework cycles that accumulate filing fees, extend go-live timelines, and create gaps in messaging operations that cost revenue. The core discipline that 10DLC 101 establishes is recognizing this as a compliance architecture—not a registration checkbox. 10dlc carrier filtering and message deliverability outcomes are direct downstream consequences of how registration data was structured at submission and how it is maintained afterward. TCR use case registration and vetting process decisions made at the moment of initial filing affect trust score baseline, throughput tier access, and long-term deliverability for the life of every campaign operating under that brand registration.
The TCR Registration Mastery Guide provides field-by-field brand and campaign submission guidance at the depth that first-pass approvals require—including the specific data inputs that generate trust score advantages over the TCR baseline and the documentation structures that satisfy carrier spot-checks on opt-in workflows.
Run your TCR Readiness Assessment on MyTCRPlus before initiating brand or campaign registration. The assessment evaluates whether your business entity data, website compliance documentation, and opt-in workflows meet current TCR and carrier standards—surfacing the specific gaps that generate registration rejections before they consume filing fees and extend your go-live timeline.
