# POL-228 — The terms, the use case and the samples must promise the same messages

> The message types described in the SMS terms, the registered use case and the sample messages must all agree.

- **Rule ID:** POL-228
- **Layer:** Policy pages (`POLICY_PAGE`)
- **Checks:** `SMS terms message types + campaign.usecase + samples`
- **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, AWS
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/policy-page/pol-228/

## Why this rule exists

Three artifacts describe the same programme and a reviewer compares all three, so the weakest one sets the verdict — samples showing promotions under a transactional use case with terms describing order updates is three different answers to one question. Each is written at a different time by a different person, which is exactly why they drift.

## How to fix it

Pick the true description of the programme and make all three match it, widening the use case if the samples need it. Done when the categories in the terms, the use case and the samples are the same set.

## Example of a compliant value

```text
Use case MIXED · terms describe offers and order updates · samples show one of each.
```

## Provider rejection codes

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

## Notes

POL-193 compares the terms against the use case alone. This rule adds the samples, which is the surface most likely to reveal a category nobody declared.