A registered domain can substitute for the brand name in a sample
The requirementstatement
Where a sample does not carry the brand name, the brand's registered domain appearing in the message can satisfy sender identification.
- Severityseverity
- MediumMEDIUMUsually survives review, but lowers your trust score or invites a manual look you would rather avoid.
- When it bitesphase
- Gates approvalapprovalGet this wrong and the brand or campaign is refused at registration.
- What is checkedobject
- campaign.sample[] + brand.website
- 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
- TCR
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
How to fix itremediation
Prefer the brand name at the start of the message. Where space is genuinely tight, a link to the registered domain identifies the sender acceptably.
A compliant exampleexample
Order ready for pickup: https://acmecoffee.com/o/4471 Reply STOP to opt out.
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-038 is one of 122 message content rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.