# POL-151 — The SMS terms must be about the messaging programme

> The SMS terms must cover the messaging programme specifically rather than restating general website terms.

- **Rule ID:** POL-151
- **Layer:** Policy pages (`POLICY_PAGE`)
- **Checks:** `SMS terms body`
- **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
- **Fix type:** Fix the privacy policy or SMS terms
- **Required by:** Twilio, TCR, Infobip, AWS, Sinch
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/policy-page/pol-151/

## Why this rule exists

A page titled "SMS Terms" that turns out to be the standard site terms with a heading changed tells a reviewer that nobody wrote terms for this programme — and the consumer still has no idea what they will receive. It happens when the terms page is produced to satisfy the registration field rather than to document anything.

## How to fix it

Write the terms around this programme: what it sends, how often, who it is for, what it costs, how to stop and how to get help. Done when nothing in the document would be true of a different business.

## Example of a compliant value

```text
Acme Coffee Rewards sends weekly promotional offers and rewards balance updates to customers who joined at checkout. Message frequency varies. Message and data rates may apply.
```

## Provider rejection codes

| Provider | Code | Resubmission allowed |
| --- | --- | --- |
| Twilio (gen1) | `30882` | yes |