# OPS-127 — UCaaS low-volume carries restrictions beyond the volume

> A UCaaS low-volume registration is limited to a low daily ceiling, a restricted throughput class, one number per human user, and no API or automated traffic.

- **Rule ID:** OPS-127
- **Layer:** Operational (`OPERATIONAL`)
- **Checks:** `UCaaS traffic pattern against the tier conditions`
- **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:** External record we cannot query — reported as a warning to verify
- **Fix type:** Wait on an external system or a required interval
- **Required by:** T-Mobile, AT&T, TCR
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/operational/ops-127/

## Why this rule exists

The tier exists for individual humans typing messages, and the conditions enforce that rather than merely the volume — so a business that stays under the daily cap but sends through an API has still breached it. It is chosen for the low cost and the conditions are discovered afterwards.

## How to fix it

Use this tier only for human-sent, one-number-per-person messaging. Register a standard campaign for anything automated, however low the volume. Done when no API traffic runs on a UCaaS registration.

## Check this yourself

**Does anything automated touch the numbers on your UCaaS low-volume registration?**

1. Look for API traffic, integrations and scheduled sends on those numbers — an integration somebody added later is the usual breach, and it is invisible in the volume figures.
2. The tier requires human-sent messages, one number per person, no automation — staying under the daily cap is not sufficient.
3. Register a standard campaign for anything automated, however low the volume.

*What wrong looks like:* A business well under the daily ceiling has still breached the tier because it sends through an API. The tier was chosen for the price and the conditions were read afterwards.

## Notes

Tier conditions applied by the carriers. What the user has to confirm is that nothing automated touches the numbers on this tier — an integration somebody added later is the usual breach, and it is invisible in the volume figures.