Consent records must capture the required fields
The requirementstatement
The flow should evidence retention of the consent record: number, timestamp, medium, the exact wording agreed to, and the consenting party.
- Severityseverity
- MediumMEDIUMUsually survives review, but lowers your trust score or invites a manual look you would rather avoid.
- 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
- 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
- CTIA
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
CTIA enumerates the fields a consent record must hold, including a capture of the language and action used to secure it. Recording only "opted in: true" leaves you unable to show WHAT was agreed to, which is the question every complaint turns on.
How to fix itremediation
State in the flow that you retain the consent record, and store the disclosure version alongside the timestamp so you can reproduce what the consumer actually saw.
A compliant exampleexample
For each opt-in we store the phone number, timestamp, collection medium, the disclosure version shown, and the session or agent identity.
Notesnotes
Registration-side twin of a runtime obligation — we verify the flow claims retention, not that retention happens.
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.
CMP-003Message flow must not begin or end with whitespaceBlockingBLOCKINGCMP-059Message flow must describe the mechanism end to endBlockingBLOCKINGCMP-060Every opt-in method in use must be listed in the message flowBlockingBLOCKINGCMP-061Each declared method needs its own complete workflow paragraphBlockingBLOCKINGCMP-072Message flow must state the message typesBlockingBLOCKINGCMP-073Message flow must state message frequencyBlockingBLOCKING
CON-RECORD-FIELDS is one of 101 consent flow rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.