Verbal opt-in requires the documented script
The requirementstatement
A campaign collecting consent by phone must supply the exact script read to the consumer.
- 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.message_flow + consent artifact
- 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
- TCRFCCAerialink
- When it appliesapplicabilityText
- Applies when consent was collected by live verbal and IVR.
Why this rule existsrationale
How to fix itremediation
Attach the verbatim script your agents read, not a summary of it. We can generate a compliant script covering all eight required elements, which you can adapt and hand to your team.
Common mistakespitfalls
- "Agents ask for permission to text" describes a policy, not a script — a reviewer cannot audit it.
Rules you will hit next
5 other rules read campaign.message_flow + consent artifact. 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-VERBAL-SCRIPT is one of 101 consent flow rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.