# POL-152 — The SMS terms must be findable rather than buried

> The SMS terms must be near the top of the document or reachable by their own anchor, not buried inside terms about other services.

- **Rule ID:** POL-152
- **Layer:** Policy pages (`POLICY_PAGE`)
- **Checks:** `SMS terms section position and anchor`
- **Severity:** HIGH — Rejected by at least one carrier or provider, and a common cause of failure at the rest.
- **When it bites:** Gates approval — get this wrong and registration is refused
- **How it is detected:** AI judgement over the submitted form; AI judgement over the crawled website or policy page
- **Fix type:** Fix the privacy policy or SMS terms
- **Required by:** CTIA, T-Mobile, Twilio, Bandwidth, AWS, Telnyx
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/policy-page/pol-152/

## Why this rule exists

CTIA and T-Mobile both treat consent details buried in unrelated terms as a consent defect rather than a formatting one, because a consumer who cannot find the terms has not been told what they are agreeing to. The usual shape is a fifty-clause commercial ToS with the messaging paragraph at clause 34, which is compliant on a word count and useless to a reader.

## How to fix it

Give the messaging section its own anchor and link that anchor from the opt-in, or publish the terms as their own page. Done when the registered link lands the reader on the messaging terms rather than at the top of a long document.

## Example of a compliant value

```text
terms_and_conditions_url: https://acmecoffee.com/terms#sms — the link lands on the messaging section itself.
```

## Provider rejection codes

| Provider | Code | Resubmission allowed |
| --- | --- | --- |
| Twilio (gen2) | `30909` | yes |

## Notes

Absorbs POL-153, which states the same findability requirement as a prohibition on burying opt-in details in unrelated terms. Severity divergence in the catalog: CTIA, Telnyx and Bandwidth grade the buried-consent form BLOCKING; that stricter form lives in the consent-surface layer, and this is the document-side variant, kept at HIGH.