# CMP-141 — Sample count must meet the minimum for the declared use case

> The campaign must carry at least the number of sample messages its use case requires.

- **Rule ID:** CMP-141
- **Layer:** Campaign (`CAMPAIGN`)
- **Checks:** `campaign.sample[] + 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:** Deterministic (settled in code from the submitted values)
- **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/campaign/cmp-141/

## Why this rule exists

Sample minimums vary by use case, and special use cases generally require more because reviewers need to see the breadth of a programme that gets elevated treatment. A campaign that satisfies the global minimum can still fail its own use case.

## How to fix it

Add sample messages until the use-case minimum is met, each showing a genuinely different scenario rather than a reworded duplicate.

## Example of a compliant value

```text
MARKETING requires at least 2 distinct samples.
```