Samples must match the declared opt-in method
The requirementstatement
Sample content must be consistent with how consent was collected, not only with the use case.
- Severityseverity
- HighHIGHRejected by at least one carrier or provider, and a common cause of failure at the rest.
- When it bitesphase
- Gates approvalapprovalGet this wrong and the brand or campaign is refused at registration.
- What is checkedobject
- campaign.sample[] + consent method
- 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
- CTIATCRFCC
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
How to fix itremediation
Align the samples with what the opt-in surface promised. Where you send more than the opt-in described, widen the disclosure rather than narrowing the samples.
A compliant exampleexample
Keyword opt-in advertised as "text JOIN for offers" → samples are offers, not appointment reminders.
Rules you will hit next
Other message content rules at the same severity. A registration is judged as a whole, not rule by rule.
MSG-149 is one of 122 message content rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.