A P2P exemption has conditions, all of them

The requirementstatement

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.

Severityseverity: MediumMEDIUMUsually survives review, but lowers your trust score or invites a manual look you would rather avoid.
When it bitesphase: After you are livepostFalls due once you are sending: STOP handling, quiet hours, suppression, record retention.
What is checkedobject: P2P exemption application
Where it liveslayer: OperationalOPERATIONAL
How Ekas settles itdetectability: Human checkHUMAN; Only someone holding the document or making the call can settle it. Ekas tells you exactly what to look at.
What the fix involvesfailureClass: Wait on someone elseTERMINAL_EXTERNAL; Needs an external system or a waiting period, such as IRS propagation, a vetting result, or a carrier queue.
Who requires itauthorities: Telnyx
When it appliesapplicabilityText: Applies to every 10DLC registration.

Why this rule existsrationale

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 itremediation

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 yourselfattestation

No tool can settle this one for you. Here is the check, and what wrong looks like.

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

1Measure the ratio first. It is the condition most often assumed and least often met.
2Then check every other condition honestly: no business sending, not a cloud communications suite, human-written messages, clean compliance history.
3Where 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.

Notesnotes

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.

Rules you will hit next

Other operational rules at the same severity. A registration is judged as a whole, not rule by rule.

OPS-032A help request containing a stop-word is not an opt-outMediumMEDIUM OPS-042Somebody has to own revocations that arrive in conversationMediumMEDIUM OPS-050The opt-out confirmation is worth sending inside five minutesMediumMEDIUM OPS-051Only ask which messages to stop when there is more than one kindMediumMEDIUM OPS-057Log the sends you did not makeMediumMEDIUM OPS-062An opted-out consumer must be able to come backMediumMEDIUM

All operational rules

OPS-133 is one of 139 operational rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.