# OPS-135 — Do not spread one message across many numbers

> Similar or identical content must not be distributed across many sending numbers to dilute per-number reputation or evade filtering.

- **Rule ID:** OPS-135
- **Layer:** Operational (`OPERATIONAL`)
- **Checks:** `outbound traffic distribution across numbers`
- **Severity:** BLOCKING — Breaking this rule gets the submission rejected outright.
- **When it bites:** Falls due after approval, once you are live and sending
- **How it is detected:** Not knowable before submission — reported with its deadline
- **Fix type:** Hard stop — not remediable, resubmission will not help
- **Required by:** T-Mobile, AT&T, CTIA, Twilio, Telnyx, AWS, Vonage, Sinch, Plivo
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/operational/ops-135/

## Why this rule exists

Filtering is scored per originator, so splitting a send across ten numbers gives each one a tenth of the complaint rate and a tenth of the volume — which is the entire mechanism, and the carriers named it before anybody built a product around it. The innocent version is indistinguishable from the outside: a brand whose sends were slow buys more numbers to go faster, and is now doing exactly what the rule prohibits. It carries a four-figure pass-through fee rather than a rejection, so the first signal is an invoice.

## How to fix it

Route similar content through one registered originator, or request an approved number pool for the campaign so the distribution is declared rather than discovered. Where throughput is the real constraint, raise it through vetting rather than through number count.

## Common mistakes

- Needing more throughput is a legitimate problem with a legitimate answer — a registered number pool, or a higher-tier brand vet — and neither of them is more numbers quietly added to a campaign.

## Check this yourself

**How many numbers does this campaign actually send from, and was a pool ever approved for it?**

1. Count the originators on the campaign, then ask your provider whether an approved number pool is on record.
2. Where throughput is the real constraint, raise it through vetting rather than through number count.
3. Route similar content through one registered originator otherwise.

*What wrong looks like:* A brand whose sends were slow buys more numbers to go faster and is now doing exactly what the rule prohibits. It carries a four-figure pass-through fee rather than a rejection, so the first signal is an invoice.

## Notes

Absorbs MSG-138, the same prohibition from the message-content side. A traffic shape we cannot observe. What the user has to check is how many numbers their campaign actually sends from and whether a pool was ever approved for it — OPS-POOL-DECLARED covers the registration-side declaration, and OPS-136 catches the duplicate-campaign version of the same pattern before submission.