Each declared sub-use case needs its own sample message
The requirementstatement
A campaign declaring sub-use cases must carry at least one sample message for each of them.
- 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.sub_use_cases[]
- 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
- BandwidthTelnyxAWSSinchBirdVonage
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
A MIXED campaign is several programmes sharing one registration, and a reviewer approves each of them on the strength of a sample. Declaring five sub-use cases and supplying two samples asks them to approve three programmes they have not seen, so they refuse — and the rejection names the sample count, which sends the submitter to add generic samples rather than to the sub-use case that had nothing behind it.
How to fix itremediation
Write one sample per declared sub-use case, each showing that sub-use case and nothing else. Done when you can point at the sample that justifies every sub-use case you ticked — and if you cannot write one, untick it.
A compliant exampleexample
Sub-use cases MARKETING + DELIVERY_NOTIFICATION → sample1 "Acme Coffee: 20% off all beans this weekend. Reply STOP to opt out." and sample2 "Acme Coffee: your order #4471 ships today. Reply STOP to opt out."
Common mistakespitfalls
- Reusing one promotional sample for two promotional sub-use cases does not satisfy this — the reviewer is counting distinct programmes, not distinct wordings.
Provider rejection codescodes
The code you get back when this rule is what failed, and whether that provider lets you resubmit.
| Provider | Code | Resubmit |
|---|---|---|
| TCR | 8102 | Yes |
Rules you will hit next
Other campaign rules at the same severity. A registration is judged as a whole, not rule by rule.
CMP-003Message flow must not begin or end with whitespaceBlockingBLOCKINGCMP-017Every mandatory campaign attribute must be explicitly setBlockingBLOCKINGCMP-024Registration fields must be written in EnglishBlockingBLOCKINGCMP-028Opt-in evidence must be a JPG, PNG or PDF under 500 KBBlockingBLOCKINGCMP-035The description must describe this programme, not messaging in generalBlockingBLOCKINGCMP-037The description must name the business that sends the messagesBlockingBLOCKING
CMP-139 is one of 94 campaign rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.