Sole-proprietor throughput is capped, and the CSP enforces it

JSONMarkdown

The requirementstatement

Sole-proprietor traffic is capped at roughly 1,000 messages a day and 15 a minute, enforced at the CSP rather than by the carrier.

Severityseverity
HighHIGHRejected by at least one carrier or provider, and a common cause of failure at the rest.
When it bitesphase
After you are livepostFalls due once you are sending: STOP handling, quiet hours, suppression, record retention.
What is checkedobject
sole-proprietor send rate
Where it liveslayer
BrandBRAND
How Ekas settles itdetectability
Post-submissionUNDETECTABLE_PRE_SUBMISSION
The subject does not exist yet at submission time: a reply window, an expiring PIN, a queue position. Reported with its deadline.
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
TCRT-MobileAT&T
When it appliesapplicabilityText
Applies when the brand is a sole proprietor.

Why this rule existsrationale

Because the cap is applied upstream of the carrier, exceeding it does not produce message-level rejections — traffic is throttled or the account is reviewed, which looks like a delivery problem rather than a limit. A business planning a launch send on this tier will not find the ceiling in any error code, only in queue times that get steadily worse.

How to fix itremediation

Size the programme against roughly 1,000 messages a day and 15 a minute before committing to a schedule. If a single send would exceed it, spread it across days or move to a standard brand — there is no increase available on this tier.

Check this yourselfattestation

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

Does your largest planned send fit inside roughly 1,000 messages a day and 15 a minute?

  1. 1Do the arithmetic before committing to a schedule: list size against the daily cap, and burst rate against 15 a minute.
  2. 2If a single send would exceed it, spread it across days or move to a standard brand. There is no increase available on this tier.
  3. 3Watch for throttling rather than rejections — the cap is applied at the CSP, upstream of the carrier.

What wrong looks like: No error code names the ceiling. Queue times get steadily worse, the launch send arrives over two days, and it reads as a delivery problem rather than a limit.

Notesnotes

Send rate is not visible at registration time. The user has to do the arithmetic themselves — list size against the daily cap — and knowing that the CSP applies it means the symptom to watch for is throttling, not rejections.

Rules you will hit next

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

BRD-006Submit every name line above the address on a multi-line IRS recordHighHIGHBRD-007TCR takes only the first line of the IRS-registered nameHighHIGHBRD-010Take the legal name from the CP-575 or 147C, never a W-2 or W-9HighHIGHBRD-014An acquired business registers the details it filed taxes underHighHIGHBRD-027EIN must be old enough to have propagated to IRS recordsHighHIGHBRD-034Validate a non-US identifier against its home register before submittingHighHIGH

All brand rules

BRD-086 is one of 196 brand 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