Missing Sample for Use Case

Why This Rejection Happens

You selected a "Mixed" use case but only provided samples for ONE type of traffic. If you claim to send Marketing AND Alerts, you must show a sample of BOTH.

Root Cause Analysis

The Fix

Diversify your sample messages to cover all declared use cases.

✓ Correct Mix (for Mixed Campaign)

• Sample 1 (2FA): "[Brand]: Your verification code is 8842. Do not share this code."
• Sample 2 (Marketing): "[Brand]: Summer sale starts now! 20% off everything. Reply STOP to cancel."
• Sample 3 (Support): "[Brand]: Your ticket #992 has been updated. Reply HELP for info."

Create Balanced Campaigns

Ensure your "Mixed" use case is properly justified.

Comprehensive TCR rejection remediation powered by MyTCRPlus.com

What reviewers check for code 8102

Code 8102 is reported as "Missing Sample for Use Case". Every type of content the program sends must be declared. Reviewers reject campaigns whose samples or website show message types not covered by the use case or attributes, for example marketing content in a notification campaign, cart reminders without marketing declared, or charity content without the charity attribute.

Where code 8102 comes from

Code 8102 is a campaign review reason code used to report a specific deficiency found during manual campaign vetting. CSPs surface it in the rejection notice alongside any other codes found in the same review, so check for companion codes before resubmitting. It is marked High severity: it blocks approval, but it is fully fixable by correcting the submission and resubmitting.

Fix and verify before resubmitting

1. List every message type the program sends today and plans to send.
2. Choose a use case that covers all of them (Mixed or Marketing when promotions are included).
3. Select the matching content attributes.
4. Provide a sample for each declared type.
5. Update the opt-in language so consent covers every declared type.
6. Resubmit with a note that references code 8102 (Missing Sample for Use Case) and lists each change made.

Sample resubmission note

Many CSPs let you add a note for the reviewer when you resubmit. A short, specific note shows what changed and speeds up the second review. Example for Studio Juniper Salon:

Studio Juniper Salon corrected the deficiency reported as code 8102 (Missing Sample for Use Case). Changes made: list every message type the program sends today and plans to send; choose a use case that covers all of them (Mixed or Marketing when promotions are included); select the matching content attributes. All URLs, keywords and auto-replies were re-tested from an external network before this resubmission, and the campaign text now matches the live opt-in exactly.

Common mistakes that keep code 8102 coming back

• Treating abandoned-cart messages as transactional (they are marketing).
• Adding promotions to an existing notification campaign later.
• Forgetting to declare embedded links or phone numbers.

Related rejection codes

• Code 8200: Marketing Sample Without Attribute
• Code 8004: Undeclared Mixed Use Cases
• Code 8003: Cart Reminder Without Marketing
• Code 2200: Marketing Flow Without Attribute
• Code 2005: Undeclared Use Case Detected
• Code 2131: Verbal Script Missing STOP Instructions

Frequently asked questions about code 8102

Are abandoned-cart reminders marketing?

Yes. Carriers treat them as promotional because no transaction was completed. Declare marketing and collect marketing consent.

What happens if I start sending a new type after approval?

Undeclared content can cause filtering or suspension. Update the campaign before sending new types.