The consent control label must name the programme, not just contact
The requirementstatement
The label on the consent control must say what the consumer is subscribing to — a bare "Text me" or "Contact me" is not specific enough.
- 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
- consent checkbox label text
- 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 websiteTERMINAL_WEBSITE
- The fix lives on your site. No amount of rewording the form clears it.
- Who requires itauthorities
- TelnyxBandwidthTwilio
- When it appliesapplicabilityText
- Applies when consent was collected by web form, checkout, account settings, third party and point of sale.
Why this rule existsrationale
The label is the only sentence many consumers read before ticking, so it is the whole of what they agreed to. "We may contact you" agrees to nothing in particular, which means the brand cannot later show that recurring marketing was within it — and Bandwidth reads the same defect as a failure to name the specific message programme.
How to fix itremediation
Rewrite the label to name the brand and what the messages are about. Done when the label alone, with the rest of the page covered up, tells a stranger who will text them and why.
A compliant exampleexample
☐ Text me Acme Coffee offers and rewards updates.
Common mistakespitfalls
- "I agree to receive SMS messages" names the channel but not the programme, and Bandwidth rejects it for the same reason as "Contact me".
Provider rejection codescodes
The code you get back when this rule is what failed, and whether that provider lets you resubmit.
| Provider | Code | Resubmit |
|---|---|---|
| Telnyx | 611 | Yes |
| Twiliogen2 | 30513 | Yes |
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-008The live CTA and the declared message flow must say the same thingBlockingBLOCKINGCON-010The three subscriber-management attributes must be declared trueBlockingBLOCKINGCON-013Subscriber attributes must agree with the message bodies suppliedBlockingBLOCKINGCON-023Evidence URLs must resolve without a loginBlockingBLOCKINGCON-024The opt-in URL must serve a certificate that verifiesBlockingBLOCKINGCON-027The opt-in URL must land on a page that carries the opt-inBlockingBLOCKING
CON-059 is one of 101 consent flow rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.