Description, message flow, and samples must not be the same text
The requirementstatement
The description, message flow, and sample messages must each contain distinct content rather than repeated boilerplate.
- 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.description + campaign.message_flow + 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
- TwilioTCR
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
How to fix itremediation
Write each field to its own purpose: the description explains the program, the message flow explains consent collection, and the samples show real messages.
A compliant exampleexample
Description: what the program sends and to whom. Message flow: "Customers opt in at acmecoffee.com/signup by ticking…". Samples: the actual texts.
Provider rejection codescodes
The code you get back when this rule is what failed, and whether that provider lets you resubmit.
| Provider | Code | Resubmit |
|---|---|---|
| Twiliogen2 | 30911 | Yes |
Rules you will hit next
2 other rules read campaign.description + campaign.message_flow + 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-FIELD-SIMILARITY is one of 122 message content rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.