Fix TCR Code 9002:
Brand Mismatch

What TCR Error 9002 Means

TCR error code 9002 indicates campaign description inconsistency with registered brand use case category. Carriers validate alignment between stated business vertical and actual message content to prevent use case misrepresentation enabling prohibited activities.

Why This Error Occurs

Carriers implement automated and manual verification protocols detecting divergence between registered brand attributes and campaign messaging patterns. Error 9002 triggers when sample messages contain content inconsistent with approved use case category.

How to Fix TCR Error 9002

Remediation requires 4 corrective actions aligned with T-Mobile and AT&T enforcement policies. Campaign resubmission following these steps achieves 85-95% approval rates within 3-5 business days.

1. 1

   Identify Use Case Misalignment

   Review campaign description against registered brand vertical to identify content inconsistencies triggering carrier rejection. Compare sample message keywords against approved use case criteria.

   Technical Detail: T-Mobile implements Natural Language Processing scanning campaign descriptions for promotional indicators (discounts, limited-time offers, call-to-action language) conflicting with transactional use case selection. Marketing terms trigger automated mismatch flags requiring manual verification.
2. 2

   Select Correct TCR Use Case

   Align campaign category with actual business operations using TCR Use Case Selector to match brand type. Marketing campaigns require Marketing use case selection regardless of content mix.

   Technical Detail: TCR defines 19 use case categories with distinct throughput allocations and content requirements. 2FA/OTP campaigns receive 4,500 msg/min but prohibit promotional content. Marketing campaigns receive 600 msg/min standard rate with promotional content permitted. Use case reclassification requires campaign deletion and resubmission.
3. 3

   Update Campaign Content

   Revise sample messages and campaign description to reflect approved use case category. Remove promotional language from transactional campaigns or reclassify as Marketing.

   Technical Detail: AT&T validates first 3 sample messages against use case content standards. Messages containing discount percentages, urgency language, or purchase prompts trigger Marketing use case requirement. Notification campaigns must focus on account status or service updates without promotional elements.
4. 4

   Resubmit for Manual Review

   Submit corrected campaign to carrier for manual approval within 3-5 business days. Document use case justification including business model explanation and message content rationale.

   Technical Detail: Error 9002 rejections enter manual review queue requiring human validation of use case appropriateness. Carriers assess brand website consistency, sample message authenticity, and vertical alignment. Approvals typically process within 72 hours for Standard brands, 5-7 days for Special use cases requiring additional verification.

Technical Requirements

TCR error 9002 enforcement stems from Campaign Registry validation protocols requiring consistency between brand vertical registration and campaign use case selection. Carriers cross-reference multiple data sources to detect misrepresentation.

Use Case Category Criteria

TCR defines distinct content requirements for each use case category. Marketing campaigns permit promotional content with explicit TCPA consent. Transactional campaigns prohibit promotional language requiring service-specific messaging only. Special use cases demand supporting documentation verifying nonprofit status, political committee registration, or emergency service authorization.

Carrier-Specific Enforcement

T-Mobile implements strictest use case validation scanning campaign descriptions for keyword patterns indicating promotional intent. Phrases containing "sale," "discount," "offer," or urgency language trigger Marketing use case requirement regardless of registered category. AT&T validates brand website consistency requiring homepage business model alignment with selected use case. Verizon emphasizes EIN verification ensuring tax ID matches across all registration documents.

Trust Score Impact

Use case misalignment contributes to trust score penalties reducing approval probability for subsequent campaigns. Brands demonstrating consistent use case selection across multiple campaigns receive trust score bonuses improving automated approval rates. Error 9002 patterns indicating systematic misrepresentation can trigger enhanced scrutiny on all future submissions.

Prevention Strategy

Organizations avoiding TCR error 9002 implement 3 proactive controls ensuring use case alignment before campaign submission.

Frequently Asked Questions

Related Resources