# CON-BOX-PRESENT — An explicit affirmative opt-in control must exist

> Consent must be captured by a deliberate affirmative action — a checkbox, toggle, or signature — never inferred from form submission.

- **Rule ID:** CON-BOX-PRESENT
- **Layer:** Consent flow (`CONSENT_FLOW`)
- **Checks:** `consent surface`
- **Severity:** BLOCKING — Breaking this rule gets the submission rejected outright.
- **When it bites:** Gates approval — get this wrong and registration is refused
- **How it is detected:** AI judgement over the crawled website or policy page; AI vision over a consent artifact (screenshot, scan, MMS media)
- **Fix type:** Fix the website — no form edit clears it
- **Required by:** CTIA, TCR, FCC, Twilio
- **Applies:** Applies when consent was collected by web form, checkout, account settings, third party and point of sale.
- **Canonical URL:** https://ekas.io/rules/10dlc/consent-flow/con-box-present/

## Why this rule exists

Express written consent requires an act that means "yes to messages" and nothing else. When consent is bundled into pressing Submit, there is no way to distinguish someone who wanted texts from someone who wanted an account, and no way to evidence the difference later.

## How to fix it

Add a dedicated checkbox the customer must tick, unchecked by default, with the consent disclosure printed beside it. Replace any "by submitting this form you agree to receive texts" wording with a real control.

## Example of a compliant value

```text
☐ By checking this box, you agree to receive recurring automated marketing text messages from Acme Coffee at the number provided. Consent is not a condition of any purchase. Message frequency varies. Message and data rates may apply. Reply STOP to unsubscribe or HELP for help. See our Terms of Service and Privacy Policy.
```