Sample messages must match the declared use case

The requirementstatement

The content of the samples must be consistent with the campaign use case selected.

Severityseverity: BlockingBLOCKINGBreaking this rule gets the submission rejected. There is no partial credit.
When it bitesphase: Gates approvalapprovalGet this wrong and the brand or campaign is refused at registration.
What is checkedobject: campaign.sample[] + campaign.usecase
Where it liveslayer: Message contentMESSAGE_CONTENT
How Ekas settles itdetectability: AI · formAI_FORM; A semantic question about what you wrote: whether a description matches a use case, whether a name looks like a filed entity. Judged by a model against written criteria.
What the fix involvesfailureClass: Fix the fieldRETRY_FIELD; A better value in the form fixes it. Ekas can rewrite it and re-check.
Who requires itauthorities: TCRTwilioBandwidthAWSSinch
When it appliesapplicabilityText: Applies to every 10DLC registration.

Why this rule existsrationale

The use case determines the consent standard, the throughput a carrier grants, and the filtering applied to your traffic. A campaign registered as ACCOUNT_NOTIFICATION that sends promotions is receiving treatment it did not qualify for, so the mismatch is a registration integrity problem rather than a labelling error.

How to fix itremediation

Either change the use case to match what you actually send, or replace the off-pattern samples. If you genuinely send both promotional and transactional content, select MIXED and show both — but note that MIXED requires promotional-grade consent.

A compliant exampleexample

For ACCOUNT_NOTIFICATION: "Acme Coffee: your payment of $24.50 was received. View receipt: https://acmecoffee.com/r/4471 Reply STOP to opt out."

Common mistakespitfalls

A single promotional sample inside an otherwise transactional set is enough to trigger this — Bandwidth codes it separately as 8200.

Provider rejection codescodes

The code you get back when this rule is what failed, and whether that provider lets you resubmit.

Provider	Code	Resubmit
Twiliogen1	30893	Yes
Bandwidth	8200	Yes

Rules you will hit next

3 other rules read campaign.sample[] + campaign.usecase. Fixing one field to satisfy a single rule is how a resubmission trades one rejection for another, so read these before you change anything.

CMP-141Sample count must meet the minimum for the declared use caseBlockingBLOCKING MSG-152Transactional campaigns must contain no promotional elementBlockingBLOCKING MSG-155Sweepstakes content requires the sweepstakes use caseBlockingBLOCKING MSG-008Opt-in confirmation must be 20–255 charactersBlockingBLOCKING MSG-009HELP reply must be 20–255 charactersBlockingBLOCKING MSG-011Opt-out confirmation must be 20–255 charactersBlockingBLOCKING

All message content rules

MSG-SAMPLES-USECASE is one of 122 message content rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.