A low-volume campaign has a ceiling, not a warning

JSONMarkdown

The requirementstatement

Low-volume campaigns must stay under their published ceiling, or be upgraded to a standard registration.

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
campaign volume against the use-case ceiling
Where it liveslayer
OperationalOPERATIONAL
How Ekas settles itdetectability
External recordEXTERNAL_DATA
The fact that settles it lives in a register we cannot query, such as the IRS file, a postal database, or another provider’s tenant. Reported as a warning with the evidence to check, not as a pass.
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
T-MobileTCRTelnyxBird
When it appliesapplicabilityText
Applies to every 10DLC registration.

Why this rule existsrationale

The tier is priced for genuinely small programmes, and exceeding it does not throttle politely — the traffic above the ceiling is unregistered for the purposes of the carriers who applied it. Programmes grow into this without noticing, because the registration that was right at launch says nothing when the list doubles.

How to fix itremediation

Track monthly volume against the tier ceiling and upgrade before crossing it rather than after. Done when the registration matches the traffic the programme is actually sending this quarter.

Check this yourselfattestation

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

Does your low-volume registration still match the traffic the programme is sending this quarter?

  1. 1Track monthly volume against the tier ceiling and own the review — nothing prompts an upgrade.
  2. 2Upgrade before crossing it rather than after.

What wrong looks like: The registration that was right at launch says nothing when the list doubles. Traffic above the ceiling is unregistered for the purposes of the carriers who applied it, rather than politely throttled.

Notesnotes

Volume against a published ceiling. What the user has to own is the review — nothing prompts an upgrade, and the registration keeps looking correct while the traffic outgrows it. OPS-VOLUME-PLAUSIBLE checks the declaration at registration time.

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-outMediumMEDIUMOPS-042Somebody has to own revocations that arrive in conversationMediumMEDIUMOPS-050The opt-out confirmation is worth sending inside five minutesMediumMEDIUMOPS-051Only ask which messages to stop when there is more than one kindMediumMEDIUMOPS-057Log the sends you did not makeMediumMEDIUMOPS-062An opted-out consumer must be able to come backMediumMEDIUM

All operational rules

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

Reading the rules is the easy part.

Ekas runs every rule that gates approval, 823 of these 915, against your registration before it reaches the carrier. It reads your site, your policy pages and your opt-in the way a reviewer would, and hands you the fix, not just the verdict.

Talk to UsHow 10DLC works