The consent experience itself must be versioned and retained
The requirementstatement
A capture of the exact language and action used to secure consent must be retained and versioned per 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
- 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
- CTIA
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
How to fix itremediation
Version the disclosure text and store the version identifier on each consent record, so any past consent can be replayed exactly as the consumer saw it.
A compliant exampleexample
Each opt-in stores disclosure_version=2026-03-a alongside the timestamp; we retain the full text of every version.
Rules you will hit next
6 other rules read campaign.message_flow. 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-201 is one of 139 operational rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.