TCR Vetting Systems Operational
TCR Error Database

Use Case Mismatches Sample Messages

Use Case Mismatches Sample Messages. Fix TCR 602 – use case mismatches sample messages. Learn the rule, see compliant wording, and correct the message.

The Consistency Requirement

Code 602 means your declared Campaign Use Case (e.g., "Account Notifications") does not align with your Sample Messages (e.g., "Buy one get one free!"). Carriers require strict categorization; you cannot send marketing content under a transactional use case.

Common Mismatches

Scenario A: Hidden Marketing

You selected "Customer Care" or "2FA".

Your Sample Message:

Correction: Remove the "20% off" offer or switch use case to "Marketing".

Scenario B: Vague "Mixed"

You selected "Mixed" or "Low Volume Mixed".

Your Sample Messages:

Correction: If you selected Mixed, you must provide samples of BOTH marketing and transactional message types.

How to Fix

  1. Audit Your Samples

    Review every sample message submitted. Do they contain call-to-actions, coupons, discount codes, or upsells?

  2. Match the Category

    If your samples are purely transactional: Change Use Case to "Account Notifications" or "Customer Care".
    If your samples have ANY marketing: Change Use Case to "Marketing" or "Mixed".

  3. Update Description

    Ensure your "Campaign Description" explicitly states the purpose found in your samples. E.g., "This campaign sends appointment reminders and occasional seasonal discount offers."

Not sure which use case fits?

Our interactive wizard can recommend the correct category based on your message intent.

Comprehensive TCR rejection remediation powered by MyTCRPlus.com

EXPLORE NEXT

RELATED

// Stop guessing. Start messaging.

ELIMINATE TCR
REJECTION RISK TODAY

SMB & Enterprise businesses achieve up to 90% approval rates with our diagnostic tools and carrier-validated templates.