IVR opt-in must capture an unambiguous confirmation step
The requirementstatement
An IVR flow must require a distinct keypress or spoken confirmation specifically for messaging consent.
- 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
- 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
- TCRFCC
- When it appliesapplicabilityText
- Applies when consent was collected by IVR.
Why this rule existsrationale
In an automated menu it is trivially easy for a caller to reach the end of a flow without having agreed to anything in particular. A dedicated confirmation step is what makes the resulting log entry mean "yes to texts" rather than "completed the call".
How to fix itremediation
Add a dedicated consent step with its own keypress, after the disclosure has been read, and log the keypress with a timestamp.
A compliant exampleexample
"To agree to receive recurring automated text messages from Acme Coffee at this number — message frequency varies, message and data rates may apply, reply STOP to cancel — press 1 now. To continue without text messages, press 2."
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-IVR-CONFIRM is one of 101 consent flow rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.