# CON-049 — Secondary collection pages owe the full disclosure, not a token line

> The consent language on a secondary phone-collecting page must carry the opt-out instruction and the policy links, not merely mention texting.

- **Rule ID:** CON-049
- **Layer:** Consent flow (`CONSENT_FLOW`)
- **Checks:** `secondary phone-collecting pages`
- **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
- **Fix type:** Fix the website — no form edit clears it
- **Required by:** Telnyx
- **Applies:** Applies to every 10DLC registration.
- **Depends on:** CON-048
- **Canonical URL:** https://ekas.io/rules/10dlc/consent-flow/con-049/

## Why this rule exists

Having added a line to the contact form, brands stop there — so the secondary pages end up with "we may text you" and none of the elements that make an opt-in valid. A consumer who consents on that page has been given materially less than one who consented on the signup page, and their consent is correspondingly weaker.

## How to fix it

Reuse the same consent block on every form rather than writing a shorter one per page — one snippet, included everywhere, is both less work and the only way the pages stay in step when the wording changes. Done when the contact form shows the same disclosure as the signup page.

## Example of a compliant value

```text
Include the same block used at checkout: consent sentence, "Msg frequency varies. Msg & data rates may apply. Reply STOP to unsubscribe, HELP for help.", and links to the Acme Coffee Terms of Service and Privacy Policy.
```

## Provider rejection codes

| Provider | Code | Resubmission allowed |
| --- | --- | --- |
| Telnyx | `803` | yes |
| Telnyx | `861` | yes |

## Notes

Depends on CON-048: until we know which secondary pages exist, there is nothing to judge the wording of. Subject to the same whole-site crawl limitation.