Sweepstakes content requires the sweepstakes use case
The requirementstatement
Where samples contain sweepstakes or contest content, the sweepstakes use case must be declared.
- 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
- TCRSinchBandwidth
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
Sweepstakes carry their own eligibility and official-rules requirements, and several providers subject them to special business review. Running one under a general marketing use case bypasses that review, so reviewers force the correction rather than accepting the label.
How to fix itremediation
Declare the sweepstakes use case and publish official rules linked from the message, or remove contest content from the campaign.
A compliant exampleexample
Use case: SWEEPSTAKE, with official rules at acmecoffee.com/rules linked in the message.
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 caseBlockingBLOCKINGMSG-152Transactional campaigns must contain no promotional elementBlockingBLOCKINGMSG-SAMPLES-USECASESample messages must match the declared use caseBlockingBLOCKINGMSG-008Opt-in confirmation must be 20–255 charactersBlockingBLOCKINGMSG-009HELP reply must be 20–255 charactersBlockingBLOCKINGMSG-011Opt-out confirmation must be 20–255 charactersBlockingBLOCKING
MSG-155 is one of 122 message content rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.