# POL-193 — The programme described in the terms must match the registered use case

> The programme description in the SMS terms must relate to the use case the campaign is registered under.

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

## Why this rule exists

The terms are the public description of the programme and the use case is the private one, so a disagreement means one of them is wrong about what will be sent — and the reviewer resolves it by refusing the campaign. It happens most often when a terms page written for the whole business is attached to a narrower campaign.

## How to fix it

Make the terms describe the categories the campaign is registered for, or register the use case the terms describe. Done when the two describe one programme.

## Example of a compliant value

```text
Use case MARKETING · terms describe promotional offers and rewards updates — the same programme.
```

## Provider rejection codes

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