# CMP-SAMPLE-COUNT — At least two sample messages are required

> A campaign must carry at least two, and at most five, sample messages.

- **Rule ID:** CMP-SAMPLE-COUNT
- **Layer:** Campaign (`CAMPAIGN`)
- **Checks:** `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:** Deterministic (settled in code from the submitted values)
- **Fix type:** Fix the field — a better value in the form clears it
- **Required by:** Twilio, TCR, AWS, Bandwidth
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/campaign/cmp-sample-count/

## Why this rule exists

Two samples is the operative minimum across providers even where a form claims one is enough — AWS's own form says "at least one" while its reviewer rejects below two. The upper bound of five is a hard field limit.

## How to fix it

Provide at least two distinct sample messages that reflect what the campaign will actually send.

## Example of a compliant value

```text
Provide 2 to 5 distinct sample messages.
```

## Notes

AWS's own form says "at least one" while its reviewer rejects below two. Two is the operative minimum across providers.