Age-restricted content requires the age-gated attribute
The requirementstatement
Where sample or description content covers alcohol, firearms, or tobacco, the age-gated attribute must be set true.
- 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.age_gated + campaign content
- 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
- TCRCTIAT-MobileTwilio
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
How to fix itremediation
Set the age-gated attribute true and implement real date-of-birth verification at opt-in. Note several providers refuse these categories entirely even with a gate.
A compliant exampleexample
Content references alcohol → age gated: true, with DOB collected at opt-in.
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-123 is one of 122 message content rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.