When an A2P messaging campaign fails carrier vetting, the underlying cause almost always traces back to a gap in understanding what the TCR vetting process actually measures. The Campaign Registry doesn’t evaluate intent — it evaluates documentation. Brands that submit without understanding how each vetting layer works, what data is checked against external sources, and how vetting results propagate through trust score assignment and campaign review frequently encounter denials that could have been anticipated and corrected before the first submission fee was paid. This guide maps the complete TCR vetting process from brand identity verification through campaign-level DCA review, including what each checkpoint examines and how vetting outcomes determine your 10DLC messaging throughput.
The Sequential Structure of the TCR Vetting Process
The TCR vetting process operates in two sequential layers — brand vetting and campaign vetting — and the outcome of each layer determines access to the next. A brand entity must pass identity verification and receive a trust score before any campaign associated with that brand can be submitted for use-case review. Campaign vetting will not advance until the parent brand carries a TCR-verified status.
Brand vetting is executed by TCR and its external vetting partners: identity validation occurs against EIN records through IRS-linked third-party data sources, and the resulting trust score is computed using TCR’s proprietary algorithm. Campaign vetting is then executed by the Direct Connect Aggregators — Syniverse for AT&T, KORE Wireless for T-Mobile, and iconectiv for Verizon — each applying carrier-specific criteria against the campaign’s opt-in documentation, privacy policy, sample messages, and content-attribute declarations.
This sequential dependency has a practical consequence that operators frequently miss: if a brand’s vetting score falls below the threshold required for a specific campaign type, correcting the campaign submission data will not produce approval. The brand-level issue must be resolved first — either by correcting the EIN record parity, improving online presence signals, or pursuing enhanced vetting through TCR’s authorized external partners.
Brand Identity Verification — The First Gate of the TCR Vetting Process
Brand identity verification is the initial stage of the TCR vetting process, and its outcome seeds every downstream throughput and access determination. Every brand submitted to TCR undergoes automated validation against three external data sources: the EIN registry for U.S. entities, Dun & Bradstreet DUNS records (optional but strongly recommended for improved scoring), and open-source web presence signals. The outcome of this TCR brand identity verification process produces one of two statuses: Verified or Unverified.
A Verified brand status confirms that TCR’s validation confirmed exact parity between the submitted entity name, EIN, and address against IRS-linked third-party records. An Unverified status results from name mismatches — abbreviations, DBA substitutions, or punctuation variations — incorrect EIN, addresses diverging from IRS filing records, or the absence of an active public-facing website. Sole proprietor registrations add a mobile OTP confirmation step: a one-time password must be received and confirmed on the registered mobile number before identity verification can complete, regardless of all other field accuracy.
The brand’s website is a separately validated signal within brand vetting TCR reviewers examine. The site must be live and fully operational — not under construction, not parked — contain accessible contact information, match the stated business category, and host a privacy policy compliant with CTIA Messaging Principles. A site containing SHAFT-C content (Sex, Hate, Alcohol, Firearms, Tobacco, Cannabis) anywhere on its pages will generate a brand denial regardless of EIN parity, because carrier policy prohibits those content categories from the 10DLC ecosystem entirely.
The TCR Brand Consistency Checker validates parity across EIN data, website presence signals, and privacy policy language before submission — surfacing the discrepancies most frequently cited in TCR brand identity verification failures before the submission fee is committed.
How the TCR Brand Trust Score Is Assigned
Following brand identity verification, TCR assigns every registered brand a trust score on a 0–100 scale. The 10DLC trust score is not a static credential — it is the operational mechanism that determines eligible campaign types, message throughput limits, and T-Mobile daily message caps. How trust score affects 10DLC message throughput is the most consequential output of the entire vetting process, yet it is the element operators most frequently encounter without prior preparation.
The trust score algorithm incorporates several weighted inputs: brand identity verification result (Verified vs. Unverified carries a significant weight differential), years in business, business type classification, and the presence of an active DUNS number or LEI identifier. Non-profit, political campaign, and government entities are assigned to fixed-trust tiers that bypass standard algorithmic scoring. For-profit entities receive a score based on TCR’s assessment of the submitted brand profile against these inputs.
Throughput implications by trust score band: scores in the 0–49 range place brands in a low-tier throughput tier — T-Mobile daily message limits apply, and manual DCA review may be triggered, extending how long does TCR vetting take from the standard 24–48 hours to 7–10 business days. Scores in the 50–74 range reach standard throughput with automated DCA review for standard use-case campaigns. Scores in the 75–100 range unlock elevated throughput with premium message-per-second allocation and the fastest path through automated vetting queues.
Secondary vetting TCR brand registration steps — available through TCR’s authorized external vetting partners at a fee ranging from $40 to $110 depending on vetting depth — can elevate a brand’s effective trust tier by importing a third-party compliance and reputation assessment into the TCR brand record. This pathway is typically pursued by brands with new EINs, limited business history, or use cases requiring elevated throughput to operate at commercial volume.
The TCR Trust Score Preflight Simulator estimates your brand’s likely score band before submission, identifying which profile inputs are suppressing the TCR brand trust score and modeling the throughput impact of each correction — before any fee is paid.
Standard Versus Enhanced Vetting in TCR Campaign Registration
Not all campaign registrations move through the same vetting pathway. TCR campaign registration divides campaigns into Standard use cases and Special use cases, and each track has different requirements, approval bodies, and timelines.
Standard use cases — including Marketing, Customer Care, Two-Factor Authentication, Account Notifications, Delivery Notifications, and a defined set of others in the TCR CSP User Guide — do not require pre-registration approval from the mobile network operators. A brand with a Verified status and sufficient trust score can submit Standard campaigns and receive DCA vetting results within 24–72 hours, depending on carrier queue volume and submission completeness. Standard campaigns are the majority of what operators register.
Special use cases — Charity, Emergency, Higher Education, and others defined in the TCR framework — require MNO approval before the campaign can transmit. Vetting timelines for Special campaigns extend significantly beyond standard review periods, and incomplete submissions in this category restart the review clock with a new submission fee assessed.
Standard vs enhanced vetting TCR campaigns also diverge at the brand level. Standard brand vetting uses TCR’s automated scoring algorithm. Enhanced vetting subjects the brand to a reputation and compliance review incorporating messaging history, complaint records, and carrier feedback signals. Enhanced vetting outcomes are imported into the TCR brand record and can unlock campaign types or throughput tiers that automated scoring alone cannot produce. For businesses operating at commercial messaging volume, enhanced vetting replaces automated score uncertainty with independently verified compliance standing — a meaningful operational advantage at scale.
Campaign-Level Vetting: What the DCAs Examine
Once a brand clears identity verification and receives its trust score, each submitted campaign enters DCA vetting. The DCA vetting process at each carrier — Syniverse, KORE Wireless, and iconectiv — independently reviews the submission against CTIA-aligned criteria. Review stringency and specific requirements can differ between carriers, but the core examination elements are consistent across all three.
The DCA vetting process reviews opt-in mechanism and documentation first: the submission must describe the consent collection method, and reviewers verify the described mechanism at the provided URL. Web forms collecting phone numbers must carry visible opt-in disclosure language. The opt-in confirmation message must include the brand name, message frequency disclosure, HELP keyword instruction, STOP keyword instruction, and the “message and data rates may apply” disclosure. Missing any single element generates a standalone rejection code.
Sample messages are reviewed for use-case alignment, content compliance, and structural requirements. Each sample must accurately represent the campaign’s actual content, include the STOP keyword for marketing use cases, avoid SHAFT-C content, and use branded or full destination URLs — public shorteners such as bit.ly are prohibited across all three carriers.
Privacy policy review confirms that a dedicated, publicly accessible policy exists, contains an SMS-specific section, and explicitly states that subscriber data is not shared with third parties for marketing purposes. Linking a generic terms-of-service page as a substitute generates a denial.
Content-attribute accuracy — declarations covering embedded links, embedded phone numbers, number pooling, and age-gating — must reflect the campaign’s actual message content. Incorrect declarations are a common source of post-approval carrier filtering issues and cannot be corrected without deleting and reregistering the campaign.
The TCR Registration Mastery Guide provides compliance documentation templates for each DCA review element, organized by use-case type and formatted to the standards each carrier expects.
After Vetting Clears: Active Status and Ongoing Compliance Obligations
A successfully vetted campaign receives an Active status in the TCR system. Active status means the campaign has been cleared by TCR and the participating DCAs, and that the associated 10DLC numbers are eligible to transmit A2P messages at the throughput tier corresponding to the brand’s trust score band.
What happens after TCR brand registration and campaign approval is not a static compliance state — it is an ongoing monitoring relationship. Carrier systems continue evaluating message content and subscriber complaint rates against the declared use case and sample messages. Campaigns that deviate significantly from the registered content or accumulate elevated complaint rates can be throttled, flagged for re-review, or suspended without a formal denial notice. TCR campaign registration is the entry point, not the endpoint, of carrier compliance.
Brands operating at elevated send volumes benefit from running a pre-submission compliance audit before attaching large number pools or launching new use cases under an existing brand entity. The TCR Readiness Assessment maps current registration posture — brand verification status, trust score band, active campaign coverage, and potential compliance gaps — against TCR’s current vetting standards.
The TCR vetting process is a sequenced compliance review, not a single submission event. Brand identity verification establishes the trust foundation; trust score assignment determines throughput capacity; DCA campaign review confirms that opt-in flows, sample messages, and content attributes meet carrier standards. Operators who understand this sequence — and who build their registration submissions against the actual criteria each layer evaluates — reach Active status faster, with fewer resubmissions, and with throughput allocations that support their operational volume. The brands that encounter repeated vetting failures are those that submitted without a pre-flight check against each review layer’s specific requirements. Treating the TCR vetting process as a structured audit, not a form submission, is what separates first-attempt approvals from extended denial cycles.
Run the TCR Trust Score Preflight Simulator on MyTCRPlus before submitting your brand registration. Enter your company profile and receive an estimated trust score band with specific input corrections that increase your throughput tier — before your first TCR submission fee is paid.
