Labelling the consent control "optional" pre-empts the gating rejection
The requirementstatement
The messaging consent control should be labelled optional where the form around it collects anything required.
- 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
- consent checkbox label
- Where it liveslayer
- Consent flowCONSENT_FLOW
- How Ekas settles itdetectability
- AI · crawlCRAWL
- Needs your live site or policy page fetched and read. Ekas crawls it the way a reviewer would.
- 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
- Twilio
- When it appliesapplicabilityText
- Applies when consent was collected by web form, checkout, account settings, third party and point of sale.
Why this rule existsrationale
Reviewers decide whether a control is required by looking at it, not by submitting the form, so a consent box that sits in a column of asterisked fields reads as required even when it is not. The word "optional" is what Twilio itself offers as the fix for that rejection, which makes it the cheapest way to avoid an argument you would otherwise win slowly.
How to fix itremediation
Add "(optional)" to the consent control's label, and remove any asterisk or required marker near it. Done when the label says optional in words rather than relying on the absence of an asterisk.
A compliant exampleexample
☐ Text me Acme Coffee offers and rewards updates (optional).
Provider rejection codescodes
The code you get back when this rule is what failed, and whether that provider lets you resubmit.
| Provider | Code | Resubmit |
|---|---|---|
| Twiliogen2 | 30923 | Yes |
Notesnotes
Twilio documents this as a solution to error 30923 rather than as an independent requirement, so it is graded MEDIUM and worded as a recommendation. The requirement it protects — that consent is genuinely not required — is CON-NOT-GATED.
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-090The disclosure should say which number the messages come fromMediumMEDIUMCON-101"Free" must not be used loosely in the call to actionMediumMEDIUMCON-DISC-NO-POPUPTerms must not be presented only in a pop-upMediumMEDIUMCON-RECORD-FIELDSConsent records must capture the required fieldsMediumMEDIUM
CON-063 is one of 101 consent flow rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.