Keyword consent is bounded by what the advertisement promised
The requirementstatement
Consent given by texting a keyword extends only to the programme advertised alongside that keyword.
- 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
- keyword advertisement copy vs campaign content
- 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
- Produce a documentTERMINAL_ARTIFACT
- Needs a document that does not exist yet, such as a verbal script, a paper consent form, or QR landing copy. Ekas drafts it.
- Who requires itauthorities
- KlaviyoCTIA
- When it appliesapplicabilityText
- Applies when consent was collected by text-to-join keyword.
Why this rule existsrationale
With text-to-join, the advertisement is the whole disclosure — the consumer decided before the first message existed. So a keyword advertised for shipping alerts collects consent for shipping alerts, and the promotional programme it actually enrols people into was never disclosed to anybody who joined.
How to fix itremediation
Make the advertised copy describe everything the keyword enrols the consumer into, or split the programmes and advertise a keyword for each. Done when the samples contain nothing a reader of the advertisement would not have expected.
A compliant exampleexample
Text JOIN to 55512 for Acme Coffee offers and rewards updates. Msg frequency varies. Msg & data rates may apply. Reply STOP to cancel, HELP for help.
Common mistakespitfalls
- Running one keyword across several campaigns is the usual cause, and it fails here even when each campaign is individually compliant.
Rules you will hit next
Other consent flow rules at the same severity. A registration is judged as a whole, not rule by rule.
CON-017An offline opt-in still needs a findable business behind itHighHIGHCON-033Opt-in evidence must be the live surface, not a mockup of itHighHIGHCON-038Verbally-collected informational campaigns need the mockup and the messagesHighHIGHCON-042The phone field must be optional on a general-purpose formHighHIGHCON-044A required phone field must carry an SMS disclaimer beside itHighHIGHCON-064A kiosk or terminal must not pre-fill the consumer's numberHighHIGH
CON-163 is one of 101 consent flow rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.