# OPS-133 — A P2P exemption has conditions, all of them

> A P2P exemption may only be registered where every published condition holds — no business sending, not a cloud communications suite, human-written messages, traffic symmetry no worse than one to three, and a clean compliance history.

- **Rule ID:** OPS-133
- **Layer:** Operational (`OPERATIONAL`)
- **Checks:** `P2P exemption application`
- **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:** Human check — only someone holding the document can settle it
- **Fix type:** Wait on an external system or a required interval
- **Required by:** Telnyx
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/operational/ops-133/

## Why this rule exists

The exemption is attractive because it removes registration entirely, so it attracts applications from senders who meet most of the conditions. Meeting most of them is meeting none: the exemption is withdrawn on any one, and the traffic that ran under it retrospectively becomes unregistered A2P.

## How to fix it

Check every condition honestly before applying, particularly the traffic-symmetry and human-written ones. Where any fails, register instead — the cost of the registration is far below the cost of a withdrawn exemption.

## Check this yourself

**Have you measured your traffic symmetry against the one-to-three condition before applying for a P2P exemption?**

1. Measure the ratio first. It is the condition most often assumed and least often met.
2. Then check every other condition honestly: no business sending, not a cloud communications suite, human-written messages, clean compliance history.
3. Where any fails, register instead.

*What wrong looks like:* Meeting most of the conditions is meeting none. The exemption is withdrawn on any one of them, and the traffic that ran under it retrospectively becomes unregistered A2P.

## Notes

An application to the provider. What the user has to do is measure their own traffic symmetry first, because it is the condition most often assumed and least often met.