The daily carrier cap is an EIN-level allowance, pooled across CSPs

The requirementstatement

The T-Mobile daily brand cap is an allowance against the tax ID, pooled across every campaign and every CSP that registered it, resetting at midnight Pacific.

Severityseverity: HighHIGHRejected by at least one carrier or provider, and a common cause of failure at the rest.
When it bitesphase: Gates approvalapprovalGet this wrong and the brand or campaign is refused at registration.
What is checkedobject: daily volume against brand.ein
Where it liveslayer: BrandBRAND
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-MobileTCR
When it appliesapplicabilityText: Applies to every 10DLC registration.

Why this rule existsrationale

Because the cap attaches to the EIN rather than to the brand, splitting traffic across two providers does not double it — the two routes draw from one bucket, and the second one starts failing when the first has used the allowance. Teams add a provider specifically to increase capacity and get no more messages delivered, with the failures landing on whichever route sent last.

How to fix itremediation

Plan volume against one allowance per tax ID, not per provider or per campaign, and reconcile sends across every route before scheduling a large day. The window resets at midnight Pacific, which is the boundary to schedule around.

Check this yourselfattestation

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

Have you added up the daily traffic across every CSP and every campaign that shares this tax ID?

1List every provider holding a brand on this EIN — including accounts another team set up. The cap does not care that they are separate accounts.
2Reconcile the total against one allowance before scheduling a large day, and schedule around the midnight Pacific reset.

What wrong looks like: A second provider is added specifically to increase capacity, and no more messages are delivered. Both routes draw on one bucket, and the failures land on whichever sent last.

Notesnotes

Absorbs OPS-118, which states the same pooling behaviour. Volume is not visible at registration time. What the user has to do is add up the traffic across every CSP that holds a brand on this EIN — including ones another team set up — because the cap does not care that they are separate accounts.

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 recordHighHIGH BRD-007TCR takes only the first line of the IRS-registered nameHighHIGH BRD-010Take the legal name from the CP-575 or 147C, never a W-2 or W-9HighHIGH BRD-014An acquired business registers the details it filed taxes underHighHIGH BRD-027EIN must be old enough to have propagated to IRS recordsHighHIGH BRD-034Validate a non-US identifier against its home register before submittingHighHIGH

All brand rules

BRD-235 is one of 196 brand rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.