# POL-204 — The services in the terms must match the campaign description

> The services or products described in the terms must be consistent with what the campaign description says the business does.

- **Rule ID:** POL-204
- **Layer:** Policy pages (`POLICY_PAGE`)
- **Checks:** `ToS services section vs campaign.description`
- **Severity:** MEDIUM — Usually survives review, but lowers your trust score or invites manual review.
- **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
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/policy-page/pol-204/

## Why this rule exists

The two documents describe the same business to two different audiences, and a reviewer reads them together — terms describing a software subscription behind a campaign describing a coffee shop is the shape of a registration assembled from someone else's material. It also happens innocently when a business pivots and the terms are the last thing updated.

## How to fix it

Bring the services section into line with what the business actually sells, and check it against the campaign description before submitting. Done when both describe the same business.

## Example of a compliant value

```text
Terms: "Acme Coffee sells roasted coffee, subscriptions and brewing equipment." Campaign description names the same business.
```

## Provider rejection codes

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