Sample count must meet the minimum for the declared use case

The requirementstatement

The campaign must carry at least the number of sample messages its use case requires.

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
CampaignCAMPAIGN
How Ekas settles itdetectability
DeterministicDETERMINISTIC
Settled in code from the values you submitted. No model involved, no judgement call, same answer every time.
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
TCRTwilioBandwidthAWS
When it appliesapplicabilityText
Applies to every 10DLC registration.

Why this rule existsrationale

Sample minimums vary by use case, and special use cases generally require more because reviewers need to see the breadth of a programme that gets elevated treatment. A campaign that satisfies the global minimum can still fail its own use case.

How to fix itremediation

Add sample messages until the use-case minimum is met, each showing a genuinely different scenario rather than a reworded duplicate.

A compliant exampleexample

MARKETING requires at least 2 distinct samples.

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.

All campaign rules

CMP-141 is one of 94 campaign rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.

Reading the rules is the easy part.

Ekas runs every rule that gates approval, 823 of these 915, against your registration before it reaches the carrier. It reads your site, your policy pages and your opt-in the way a reviewer would, and hands you the fix, not just the verdict.