Consent collected away from the handset should be confirmed on it
The requirementstatement
Where consent is collected outside the SMS channel — web, phone, point of sale or paper — the programme should send a double opt-in confirmation before recurring messages.
- 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
- OperationalOPERATIONAL
- 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
- T-MobileCTIA
- When it appliesapplicabilityText
- Applies when consent was NOT collected by text-to-join keyword.
Why this rule existsrationale
How to fix itremediation
Send one confirmation to the number as collected, asking for a reply to activate, and enrol only on that reply. Where a full double opt-in is not workable, at minimum send a single confirmation that names the brand and how to stop before any other message. Done when the flow says what the number receives first.
A compliant exampleexample
After a checkout opt-in we text: "Acme Coffee: reply YES to confirm you want offers and order updates. Msg&data rates may apply. Reply STOP to cancel." Numbers are enrolled only on YES.
Notesnotes
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.
OPS-252 is one of 139 operational rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.