Most operators approach TCR brand verification as a data-entry task: fill in the legal name, EIN, address, and website, and wait for approval. That framing is wrong in a way that costs them throughput capacity they never knew they were capped at. TCR brand verification is a live external database lookup process. The data you submit is cross-referenced against commercial identity registries including Dun & Bradstreet. The verification outcome is not a binary pass or fail — it produces a numerical trust score on a 0–100 scale that determines the message-per-second throughput ceiling on every campaign you will ever register under that brand. Operators who enter slightly mismatched data, select the wrong entity type, or use a branch address instead of their IRS-registered headquarters address receive a lower trust score than their actual business entity would merit — and they deliver fewer messages per second for the lifetime of those campaigns unless they remediate at the brand level.
What TCR Brand Verification Actually Does
A2P brand registration through The Campaign Registry does not work through direct submissions. Brands do not register with TCR directly. They submit their brand data through a registered Campaign Service Provider (CSP) — a messaging platform, aggregator, or compliance partner — which creates the brand record in TCR on their behalf. TCR then runs the submitted data through its verification pipeline.
The verification pipeline cross-references the submitted legal name and EIN against third-party commercial identity databases. If the submitted information matches a verifiable business entity, the brand is registered and assigned a trust score. If the data cannot be confirmed against any database TCR queries, the brand may be placed in a manual review queue or flagged for additional documentation. The trust score assigned at the conclusion of TCR brand vetting controls the throughput tier available to all campaigns under that brand — higher scores unlock higher messages-per-second limits. T-Mobile specifically publishes throughput tiers tied to trust score bands, and AT&T and Verizon’s DCA systems use trust score as a factor in real-time message filtering.
The TCR Registration Mastery Guide at MyTCRPlus walks through the full brand-to-campaign registration sequence, including the CSP selection process and the documentation that supports a clean first submission.
TCR Brand Verification: The Five Fields That Determine Your Score
TCR brand verification outcome is most sensitive to five data fields. Each field is cross-checked against external sources. Discrepancies — even minor formatting differences — reduce the trust score produced.
Legal Business Name. The submitted name must match the legal entity name exactly as registered with the IRS for the provided EIN. A DBA name, a shortened operating name, or an entity registered under a parent company name that differs from the submitting entity’s IRS filing will fail the legal name match. An LLC that operates as “Sunrise Hospitality” but is registered with the IRS as “Sunrise Hospitality Management Group LLC” must submit the full IRS-registered name.
Employer Identification Number. The EIN must be the number assigned by the IRS to the specific legal entity being registered. Using a parent company’s EIN for a subsidiary entity, or a subsidiary’s EIN for a campaign operated at the parent level, generates a mismatch. The 10DLC brand verification EIN legal name match requirement is strict: both values must correspond to the same IRS filing simultaneously.
Business Address. TCR’s database verification checks the submitted address against the registered business address on file with commercial identity registries. A branch office address, a mailing address, or a P.O. box submitted in place of the address on file with state registration authorities or IRS records will not match. Submitting any address different from the entity’s official registered address produces a negative impact on trust score. This is one of the most common verification failures for multi-location businesses that use a regional office address rather than their legal headquarters.
Business Website. The submitted website must be attributable to the registered brand entity. TCR vetting agents verify that the website references the registered business name, that the domain is operational, that no broken links are visible on the homepage or privacy policy page, and that the site does not trigger browser security warnings. A website under a different brand name than the registering entity, or a website without an SSL certificate, reduces trust score. The website must also include an SMS-specific privacy policy clause — a generic data collection policy without explicit SMS language is a separate campaign vetting issue but also reflects on the brand’s overall verification confidence.
Contact Email. TCR requires a domain-specific business email address for brand contact and Authentication+ delivery. Personal email accounts at gmail.com, outlook.com, yahoo.com, or any non-business domain are not accepted for A2P brand registration. Using a free email provider delays the Authentication+ two-factor verification step and may result in the brand record being placed in a manual review queue pending email domain confirmation.
Authentication Plus: The Mandatory Identity Layer
Authentication Plus launched October 17, 2024 and is mandatory for all new public for-profit brand registrations and for all existing public for-profit brands registering new campaigns. Authentication Plus verification requires the brand to complete a two-factor authentication step via the email address listed in the brand’s TCR profile — which is one reason why the contact email field must use a business domain address. If the email listed in the brand record is inaccessible or belongs to a former employee, Authentication Plus completion will block any new campaign registration under that brand.
The Authentication Plus brand verification process extends beyond email 2FA. It also requires that the submitted business information be consistent with company registration documents and tax ID records. Brands that registered before October 2024 and later attempt to register new campaigns will encounter Authentication Plus as a gate on the new campaign submission even if their brand record was approved under prior criteria. The practical implication: operators who registered early and are now expanding campaigns should verify that their brand record’s email is current and accessible before initiating Authentication Plus.
Entity Types and How They Affect the Trust Score Floor
TCR brand verification pathways differ by entity type. Public for-profit companies — entities whose existence can be verified through SEC filings, stock exchange listings, or major commercial registries — have the highest verification confidence and typically achieve trust scores in the upper tier. Private for-profit companies are verified through commercial databases like Dun & Bradstreet; the depth of a business’s commercial data history and DUNS record directly affects the trust score it receives. Nonprofit organizations follow a distinct verification pathway with documentation requirements specific to their tax-exempt status. Sole proprietors face the most constrained pathway.
TCR brand verification for sole proprietors follows a separate registration track. Sole proprietors cannot register under the standard 10DLC brand pathway. They register through the Sole Proprietor track, which requires a personal phone number for OTP verification rather than business entity data, and which carries lower throughput limits regardless of how the individual’s business is structured. A sole proprietor who registers under the standard track using a personal EIN or SSN will encounter verification failures. The TCR 101 guide at MyTCRPlus outlines the correct registration pathway for each entity type, including the documentation that supports the highest achievable trust score for each classification.
Low Trust Score vs. Verification Failure: Two Different Problems
Why TCR brand verification fails and why a brand receives a low trust score are different questions with different remediation paths. Verification failure means TCR could not match the submitted data to a verifiable entity in its reference databases. The brand record is not approved, and no campaigns can be registered until the underlying data is corrected and the brand is resubmitted. Common verification failure causes: legal name not matching EIN, non-matching address, website domain not attributable to the registered entity, or an Authentication Plus step that could not be completed due to an inaccessible email.
Low trust score is a different outcome. The brand is verified — TCR confirmed the entity exists — but the score produced by the verification process is below the optimal range because one or more fields produced a partial match rather than a confirmed match. A low-scoring brand can register campaigns and send messages, but it is capped at lower throughput tiers. T-Mobile limits messages-per-second for low-trust-score brands. AT&T and Verizon carrier filtering systems weight trust score in real-time message evaluation.
Remediation for a low trust score requires correcting the specific fields that produced partial matches — which requires identifying which fields diverged from external database records, not just resubmitting the same data. The TCR Error Codes & Rejections Hub documents the error codes associated with specific brand-level field failures, which helps operators identify which data element caused the score reduction.
Maximizing TCR Brand Verification Outcome Before Submission
TCR brand trust score improvement is most achievable before the initial submission, not after a low score is assigned. Post-submission trust score remediation involves brand record updates, re-vetting fees, and extended timelines. Pre-submission consistency checks across all five critical fields eliminate the discrepancies before they produce a below-optimal score.
The specific actions that maximize trust score on first submission: confirm the exact legal name on file with the IRS before entering it into the brand record; verify the EIN corresponds specifically to the registering entity (not a parent, subsidiary, or affiliated entity); submit the address from the entity’s official IRS or state registration records, not an operational address; confirm the website is live, SSL-secured, navigation-functional, and contains an SMS-specific privacy clause; and configure a business-domain email on the brand record before initiating Authentication Plus. The TCR Trust Score Preflight Simulator models the expected score for a brand before any submission is filed, surfacing the specific fields most likely to produce a partial match against TCR’s verification databases.
Understanding What TCR Brand Verification Controls
TCR brand verification is the foundation of every campaign registered under a brand. The trust score it produces determines throughput capacity for every message sent across every campaign for the duration of that brand’s registration. A low score from a mismatched address or an inconsistent legal name does not just affect the initial campaign — it caps every subsequent campaign until the brand record is remediated and re-vetted. Treating tcr brand verification as a data-entry formality produces a throughput ceiling that is invisible until operations scale to the point where the cap becomes visible in delivery metrics.
Getting the five critical fields right before submission — and completing Authentication+ with a current, accessible business-domain email — is the highest-leverage step in the entire 10DLC registration process. Every campaign built on that brand inherits the result.
Run the TCR Brand Consistency Checker at MyTCRPlus to validate your legal name, EIN, address, website, and email against TCR’s verification criteria before your brand record is submitted — identifying partial-match risks that would reduce your trust score before they become a throughput ceiling. Run the TCR Brand Consistency Checker.
