# OPS-VOLUME-PLAUSIBLE — Declared volume must be plausible for the business

> The message volume the campaign implies should be consistent with the size of the business described.

- **Rule ID:** OPS-VOLUME-PLAUSIBLE
- **Layer:** Operational (`OPERATIONAL`)
- **Checks:** `campaign.description + brand website`
- **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 field — a better value in the form clears it
- **Required by:** TCR, T-Mobile, AT&T
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/operational/ops-volume-plausible/

## Why this rule exists

A two-location coffee shop declaring a million messages a month is either mis-declaring or fronting for someone else's traffic, and volume mismatch is a signal reviewers use to detect resold registrations. Under-declaring is also a problem, since throughput is granted against the declaration.

## How to fix it

Declare volume consistent with your actual subscriber base. If you expect rapid growth, register at current scale and request an increase later rather than over-declaring now.

## Example of a compliant value

```text
A single-location retailer with ~5,000 subscribers should not declare enterprise-tier volume.
```