The TCR registration process is the sequential workflow every U.S. business sending A2P text messages through 10-digit long code numbers must complete before wireless carriers will deliver their traffic. It has two distinct stages — brand registration and campaign registration — each with its own vetting mechanism, approval timeline, and failure modes. These stages are strictly sequential: campaign registration cannot be submitted until brand registration is approved. Understanding how the TCR registration process works at each stage, what gets submitted, what gets checked, and what generates a rejection is what determines how efficiently a business moves from first submission to an approved messaging program. The TCR Registration Mastery Guide on MyTCRPlus provides the step-by-step execution framework; this article explains the underlying mechanics of what the process actually does at each stage.
How the TCR Registration Process Is Structured
The Campaign Registry is the centralized hub that validates business identity and messaging programs for U.S. A2P SMS traffic. Businesses do not register with TCR directly. The registration process flows through a three-tier infrastructure: TCR sits at the center, Campaign Service Providers (CSPs) — the messaging platforms, CRMs, and VoIP providers businesses use to send texts — submit registrations on behalf of their customers, and Downstream Aggregators (DCAs) — AT&T, T-Mobile, Verizon’s intermediary review systems — conduct independent vetting on campaigns after the CSP submission.
This structure is why different messaging platforms present different registration forms. Each CSP builds its own interface for collecting the information TCR requires. The underlying data submitted to TCR is standardized, but the interface, workflow, and level of pre-submission guidance varies by platform. Businesses that switch platforms mid-process typically need to re-register their campaigns under the new CSP, even if the brand registration carries over.
The two-stage structure — brand first, campaign second — reflects the distinction between organizational identity and messaging program content. Brand registration answers the question: is this a real, legitimate business entity? Campaign registration answers: is this a compliant messaging program being run by that entity? Both questions must be answered affirmatively for traffic to flow.
Stage One: Brand Registration — Identity Verification and Trust Score Assignment
Brand registration is the first stage of the TCR registration process. The submission collects legal entity name, Employer Identification Number (EIN), registered business address, primary contact information, website URL, business industry category, and brand entity type. Brand entity type selection — standard company, sole proprietor, government, non-profit — is consequential because it determines which vetting pathway the brand enters and affects the Trust Score assigned after registration.
Trust Score is the numerical score TCR assigns to a registered brand based on its identity verification outcome, business entity type, and publicly available data about the organization. Trust Score determines messaging throughput limits — the number of messages per minute and per day a registered campaign can send. Higher Trust Scores unlock higher throughput. A standard company with full EIN verification and a matching website typically receives a higher Trust Score than a sole proprietor registered with limited business identity documentation. The TCR Trust Score Preflight Simulator on MyTCRPlus allows businesses to estimate their Trust Score outcome before registration based on their entity type and documentation profile.
The 2025 Auth+ 2.0 update introduced mandatory enhanced identity verification for public-profit brand registrations. Brands registered before October 17, 2024, with at least one active campaign must complete Auth+ 2.0 verification by October 30, 2025. New public-profit brands registering from August 7, 2025, must complete Auth+ vetting as part of the standard registration process. This adds a two-factor verification step — independent of the standard brand form — that confirms the authorized representative completing the registration has the legal authority to bind the organization. Businesses that complete Auth+ 2.0 receive an elevated Trust Score tier with higher throughput eligibility.
Brand registration approval typically completes within minutes to two business days when the submitted information is accurate and matches IRS records. The most common brand registration failures are legal entity name mismatches against IRS records, a missing or non-public website URL, and an EIN that cannot be verified through TCR’s data sources. Sole proprietors who register with a legal name that doesn’t match their IRS SSN/EIN association are among the most common failure cases. After a brand rejection, the error code returned identifies the specific field that failed, and the correction must be submitted through the CSP before re-vetting begins.
Stage Two: Campaign Registration — Use Case, Message Flow, and Carrier Vetting
Campaign registration opens only after brand registration is approved. The submission requires a use case selection from TCR’s approved category taxonomy, a description of the messaging program, sample messages representing the actual content subscribers will receive, a description of the opt-in workflow (the Message Flow), opt-out handling documentation, a HELP message with customer care contact, and, where applicable, declarations for content attributes including the loan attribute, age-gated content, and embedded links.
The Message Flow is the campaign submission field that describes, in narrative form, how subscribers opt into receiving messages. It should describe the specific mechanism — a web form on a specific URL, a paper form at point of sale, a keyword opt-in via SMS — and confirm that the opt-in mechanism includes frequency disclosure, STOP instructions, and a link to the SMS Terms and Conditions. The website URL submitted during brand registration will be inspected against the opt-in workflow described in the Message Flow, and inconsistencies between the two generate a campaign rejection.
After the CSP submits the campaign to TCR, the submission enters the DCA vetting layer. Direct Connect Aggregators — the carrier-side review systems operated by AT&T, T-Mobile, and Verizon — conduct independent content vetting on every submitted campaign. This DCA layer runs separately from TCR’s initial review and can add 24 to 72 hours to the approval timeline, sometimes longer when campaigns require manual review. The total campaign registration timeline for standard use cases is typically three to seven business days from submission. Special use cases — charities, political messaging, sweepstakes — may take longer due to manual DCA review requirements.
The TCR Use Case Selector maps specific message programs to the correct TCR use case categories before submission, preventing the use case misalignment rejections that account for a significant share of campaign-level failures. The Provider-Specific 10DLC Registration Checklists on MyTCRPlus detail what each major CSP requires in its registration interface, since platform-specific submission requirements vary beyond the TCR standard.
The Rejection and Resubmission Cycle
Campaign rejections are common. Financial services, healthcare, and multi-category messaging programs fail at rates between 40% and 70% depending on industry. Each rejection returns an error code identifying the specific failure — website compliance, sample message non-conformance, use case mismatch, consent documentation gap — and the correction must be made before the CSP can resubmit.
The resubmission cycle carries material time and cost consequences. Each resubmission attempt incurs carrier vetting fees — charged per DCA submission — that vary by carrier and CSP. More significantly, each rejection resets the campaign vetting timeline: a resubmitted campaign goes back to the beginning of the three-to-seven-day standard review window, plus the 24-72 hour DCA layer. A business that submits an uncorrected or partially corrected campaign twice before getting it right has added four to six weeks to its registration timeline and paid fees on each failed attempt.
The error codes returned at both the brand and campaign level are documented in the TCR Error Codes & Rejections Hub, which maps each code to its root cause and the specific correction required before resubmission.
How to Move Through the TCR Registration Process Without Entering the Rejection Cycle
The businesses that complete the TCR registration process in a single cycle share four preparation practices that separate first-submission approvals from the rejection cohort.
The first is legal entity name validation before submitting brand registration. The name entered on the brand form must match the IRS record exactly — not the DBA name, not the shortened brand name used on the website, the legal entity name as it appears in IRS records. Running an IRS EIN lookup before submitting catches mismatches before they generate a brand rejection.
The second is website pre-validation. The website URL submitted with the brand form must be active, public-facing, and contain CTIA-compliant SMS disclosures: a Terms and Conditions page with SMS-specific language, a privacy policy stating mobile data is not shared with third parties for marketing, and an opt-in mechanism with adjacent disclosure language. Submitting a brand registration with a website that hasn’t been reviewed against these criteria builds the brand rejection into the submission.
The third is message flow construction from the actual opt-in mechanism rather than from a template. The Message Flow description submitted during campaign registration should describe the real opt-in workflow — the specific form URL, the checkbox language, the confirmation message — because TCR vetting compares the description against the live website. A templated Message Flow that describes a generic opt-in process while the actual website uses a different mechanism generates an inconsistency rejection.
The fourth is use case discipline: one campaign per functionally distinct message program. Consolidating appointment reminders, marketing promotions, and account alerts into a single campaign to reduce registration overhead consistently produces content-to-use-case misalignment rejections and post-approval filtering from carriers that detect message types inconsistent with the registered use case.
The TCR registration process, understood as a sequential workflow with two distinct vetting mechanisms — identity at the brand stage and content compliance at the campaign stage — is predictable and completable in a single cycle for businesses that prepare each submission to the standard that vetting systems apply. The businesses that enter the rejection cycle do so because their preparation was calibrated to what the registration form asks rather than to what the vetting system checks.
Walk through the full TCR registration process with the TCR Registration Mastery Guide on MyTCRPlus — built to take a business from brand submission through campaign approval with the preparation standards that eliminate the rejection cycle.
