Keyword opt-in requires a compliant confirmation reply
The requirementstatement
The auto-reply sent after a keyword opt-in must carry the brand, frequency, rates, STOP and HELP.
- 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.optin_message
- Where it liveslayer
- Consent flowCONSENT_FLOW
- 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
- CTIATCRBandwidthAWS
- When it appliesapplicabilityText
- Applies when consent was collected by text-to-join keyword.
Why this rule existsrationale
How to fix itremediation
Write the opt-in confirmation to include all five elements within the 320-character limit.
A compliant exampleexample
Acme Coffee: you're subscribed to offers. Msg frequency varies. Msg & data rates may apply. Reply HELP for help, STOP to cancel.
Rules you will hit next
6 other rules read 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.
CON-KEYWORD-CONFIRM is one of 101 consent flow rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.