# MSG-142 — The description must match the sample messages

> The campaign description must describe the messages the samples actually show.

- **Rule ID:** MSG-142
- **Layer:** Message content (`MESSAGE_CONTENT`)
- **Checks:** `campaign.description + campaign.sample[]`
- **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 field — a better value in the form clears it
- **Required by:** TCR, Twilio, Bandwidth, AWS
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/message-content/msg-142/

## Why this rule exists

The description is the claim and the samples are the evidence, so reviewers read them against each other first. A description promising appointment reminders beside samples full of promotions is the clearest possible signal that one of the two is untrue.

## How to fix it

Rewrite whichever is wrong so the description enumerates the message types the samples demonstrate, and the samples cover the types the description promises.

## Example of a compliant value

```text
Description mentions promotions, order updates and event invites → one sample of each.
```