The description must match the sample messages
The requirementstatement
The campaign description must describe the messages the samples actually show.
- 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.description + campaign.sample[]
- 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
- TCRTwilioBandwidthAWS
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
How to fix itremediation
Rewrite whichever is wrong so the description enumerates the message types the samples demonstrate, and the samples cover the types the description promises.
A compliant exampleexample
Description mentions promotions, order updates and event invites → one sample of each.
Rules you will hit next
One other rule reads campaign.description + campaign.sample[]. Fixing one field to satisfy a single rule is how a resubmission trades one rejection for another, so read these before you change anything.
MSG-142 is one of 122 message content rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.