TCR registration is no longer a procedural formality. Effective February 1, 2025, AT&T, T-Mobile, and Verizon block outbound A2P traffic from unregistered 10-digit long-code numbers at the infrastructure level — not as a soft filter but as a hard routing rule. For compliance officers and SMS program managers, the operational question has shifted from whether to register to how to do it correctly on the first submission. Every rejection-resubmission cycle costs a vetting fee and extends your messaging blackout window by 7 to 15 business days. The following guide covers the complete registration structure, trust score mechanics, common failure points, and the documentation practices that distinguish clean approvals from repeated rejections.
What the Campaign Registry Actually Does
Most messaging platform documentation describes The Campaign Registry as a “central database.” That framing understates what it does operationally. TCR is a third-party vetting intermediary, contracted by the major U.S. carriers, that authenticates business sender identity and evaluates the legitimacy of individual messaging programs before granting carrier-level access to A2P 10DLC infrastructure.
When a carrier receives a message from a 10-digit long-code number, its routing systems query TCR to verify that the number is linked to an approved brand and campaign. No match means no delivery. CTIA’s A2P messaging framework — adopted across the carrier ecosystem — designates TCR as that verification layer, and carriers enforce it without exception.
The October 2024 addition of Authentication+ extended TCR’s verification scope. Public, for-profit brands must now complete a one-time identity check for the brand representative submitting registration data. A $12.50 per-brand fee for this verification takes effect August 1, 2025. Businesses registering before that date avoid the fee; businesses that defer until mid-2025 or later will pay it as part of every new brand registration.
The Two-Stage Structure: Brand Registration vs. Campaign Registration
TCR registration operates as a sequential two-layer process. Treating these layers as a single submission, or starting campaign registration before brand vetting completes, is the source of a substantial share of operator delays.
The first layer is brand registration. This step establishes your legal business identity within TCR: entity name exactly matching IRS records, Employer Identification Number, business address, industry vertical, and an active website URL. The EIN-to-name match is strictly enforced — a single-character discrepancy between the name on your IRS EIN certificate and the name submitted to TCR generates a brand vetting failure. This is not a soft warning; it requires a corrected resubmission and restarts the vetting clock.
TCR Brand Registration Requirements for Businesses
Brand registration requires seven fields, all of which must be consistent across your IRS records, your public business registrations, and your company website: legal business name, EIN or Tax ID, physical street address (P.O. boxes are rejected), business entity type, industry vertical, a live SSL-certified website URL, and a brand administrator email using a business domain. Gmail, Yahoo, and other consumer email domains fail the domain-matching check.
A social media business page substitutes for a website only for sole proprietors, and only if the page includes a visible privacy policy and terms of service. For all other entity types, a functional website with those documents publicly accessible is a non-negotiable requirement.
Once brand registration resolves — typically within minutes to 48 hours for clean submissions — your Campaign Service Provider submits campaign registration. The two registrations are distinct records in TCR’s system and are reviewed separately.
How to Complete TCR Campaign Registration Without Getting Rejected
Campaign vetting applies carrier review criteria derived from CTIA Messaging Principles and Best Practices. Reviewers evaluate five elements: the use case description, the sample messages, the opt-in call-to-action, the opt-out workflow, and the coherence between all five components.
The use case description must precisely match the sample message content. A campaign registered under “customer care” that submits samples containing promotional offers, product discounts, or urgency language will receive a mismatch rejection — typically code 2003 or 2004 — because the content pattern signals a marketing use case. Carrier vetting systems apply content classification to sample messages automatically. The description and samples must narrate the same messaging program.
Opt-in documentation is the single highest-rejection-rate component. Your submission must identify the specific mechanism through which subscribers gave written consent: a web form URL with visible opt-in language, a paper form, a keyword opt-in flow, or a recorded verbal agreement. The opt-in URL must be live and SSL-valid at submission time. Redirect chains that obscure the originating form, broken links, and pages that load in more than three seconds all trigger review failures.
How to Complete TCR Campaign Registration for Common Use Cases
Use the MyTCRPlus TCR use case selector to identify the correct use case category before writing your campaign description. TCR recognizes 14 standard use cases — marketing, customer care, delivery notifications, two-factor authentication, and others — plus a set of special use cases for non-profit and political organizations. Registering under a use case that does not match your actual message content is one of the fastest paths to a campaign-level rejection.
Sample messages must contain three elements: brand name, opt-out language (STOP to unsubscribe), and HELP instructions (HELP for help, or a contact method). Absence of any one element triggers rejection codes in the 5100, 6000, or 8100 series depending on which element is missing and at which stage of the message flow it was expected. Validate your samples against the provider-specific 10DLC registration checklists before submission — each major CSP adds formatting requirements on top of TCR’s baseline, and meeting only the baseline while missing the CSP layer produces a rejection that looks unexplained without the provider context.
TCR Trust Score Impact on Message Throughput
The Trust Score assigned during brand registration governs your campaigns’ message throughput — the number of messages per second each registered campaign can deliver. Scores above 75 qualify for standard throughput, typically 75 messages per second on AT&T and T-Mobile’s networks. Scores at or below 49 are restricted to 3.75 messages per second. For any operation running appointment reminders, order confirmations, or promotional sends against a list of more than a few hundred subscribers, a restricted throughput score makes the messaging program functionally unusable at volume.
The Trust Score algorithm draws on EIN verification against IRS records, business age, third-party business credit data, and the depth of your public web presence. Sole proprietors, businesses under three years old, and entities with limited online footprint consistently receive lower initial scores. The score is not permanently fixed. Enhanced vetting — available through TCR’s vetting partners at an additional fee — can increase throughput above the standard tier for brands that qualify.
A2P 10DLC Registration Steps and Timeline After Submission
From initial submission to first approved message delivery, clean registrations typically resolve in 15 to 25 business days. Brand registration itself takes minutes to 48 hours. Carrier vetting of the campaign layer takes 5 to 20 business days depending on current queue volume and use case complexity.
Any correction required after initial review restarts the carrier review window from zero. Running your registration data through the TCR trust score preflight simulator before filing surfaces data inconsistencies and trust score risk factors that would otherwise appear as rejection codes mid-review — specifically the brand-level errors that are most time-consuming to correct after submission has already begun.
Building a TCR Registration Process That Survives Carrier Review
The businesses that complete TCR registration without extended rejection cycles treat it as a documentation assembly project before it becomes a form-filling exercise. Every brand field corresponds to a verifiable public record. Every campaign field corresponds to a live URL or a documented internal process. The review fails when fields are filled accurately but inconsistently, or when the submitted documentation doesn’t reflect how the actual messaging program operates.
10DLC Registration Checklist for Small Business
Before starting brand registration, confirm four conditions: your legal entity name matches your IRS EIN certificate exactly including punctuation and abbreviations; your website is live with a valid SSL certificate; your privacy policy explicitly discloses SMS marketing and any third-party data sharing; and your brand administrator email uses your business domain.
Before starting campaign registration, document in writing how each subscriber provided consent, at which URL or through which mechanism that consent was captured, and what opt-out and HELP language appears in your message flows. The TCR registration checklist provides field-by-field validation against current vetting criteria, including the Authentication+ identity verification step now required for public for-profit brands.
For businesses managing multiple phone numbers, locations, or messaging programs, the SMB TCR Registration Starter Bundle delivers pre-vetted campaign templates, a compliance microsite for opt-in documentation, and integrated registration diagnostics — consolidating the documentation assembly phase from several days of manual preparation into a structured workflow.
TCR registration succeeds when the documentation precedes the submission. Carriers verify that the business is legitimate, that its messaging programs operate under written consent, and that message content matches the declared use case. Organizations that assemble and verify those three components before filing clear the registration process without the correction cycles that cost time, fees, and messaging downtime. The review window does not reward effort applied after submission; it rewards accuracy applied before it.
Access the TCR Registration Mastery Guide on MyTCRPlus to work through brand and campaign submission requirements with field-level guidance, current Authentication+ steps, and built-in preflight validation tools aligned to 2025 carrier vetting standards.
Access the TCR Registration Mastery Guide before your next submission. MyTCRPlus provides field-by-field documentation requirements, preflight trust score analysis, and carrier-specific checklists that validate your brand and campaign data against current vetting criteria — before the review window opens.
