# OPS-132 — The consumer-traffic thresholds are where P2P stops

> Traffic above the published consumer-operation reference thresholds is classified as non-consumer, whatever the sender intends.

- **Rule ID:** OPS-132
- **Layer:** Operational (`OPERATIONAL`)
- **Checks:** `per-number traffic shape`
- **Severity:** MEDIUM — Usually survives review, but lowers your trust score or invites manual review.
- **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:** Wait on an external system or a required interval
- **Required by:** CTIA
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/operational/ops-132/

## Why this rule exists

The thresholds — a rough messages-per-minute band, around a thousand a day, one number per person, a hundred recipients per message, roughly balanced two-way traffic, and a limit on repeated identical messages — define the boundary in practice. A sender operating just above them without an A2P registration is not in a grey area; they are unregistered A2P traffic, and it is blocked outright rather than throttled.

## How to fix it

Measure your own traffic against the thresholds and register A2P if you are near any of them. The two-way ratio is the one people miss — traffic that is overwhelmingly outbound is non-consumer whatever the volume.

## Check this yourself

**What is the outgoing-to-incoming ratio on your numbers?**

1. Measure it. Traffic that is overwhelmingly outbound is non-consumer whatever the volume, and it is the threshold people miss.
2. Check the others too: messages per minute, roughly a thousand a day, one number per person, a hundred recipients per message, repeated identical messages.
3. Register A2P if you are near any of them.

*What wrong looks like:* A sender just above the thresholds without an A2P registration is not in a grey area — they are unregistered A2P traffic, and it is blocked outright rather than throttled.

## Notes

Traffic shape we cannot see. What the user has to check is the outgoing-to-incoming ratio on their numbers, since it reclassifies traffic that is well under every volume threshold.