The opt-in confirmation must be the first message sent
The requirementstatement
The confirmation must precede any other messaging to a newly opted-in consumer.
- 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.message_flow + campaign.optin_message
- 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
- CTIATCR
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
How to fix itremediation
Sequence the confirmation ahead of any campaign content in your automation, and describe that ordering in the message flow.
A compliant exampleexample
On opt-in we immediately send the confirmation; campaign content begins with the next scheduled send.
Rules you will hit next
One other rule reads campaign.message_flow + campaign.optin_message. 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-060 is one of 122 message content rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.