Your 10DLC Daily Limit Is Attached to the EIN, Not the Platform

September 22, 2026. If your client's texts stopped going out at two in the afternoon and started again the next morning, you did not hit a Twilio limit or a HighLevel limit. You hit T-Mobile's daily message cap, it is set by a brand trust score you cannot see from inside the sending platform, and it is attached to the client's EIN rather than to the account you are logged into. That last part is what catches agencies, because it means the cap is shared with every other platform the same business ever registered a brand on.

How the cap actually works

1. It is separate from throughput. Messages per second and the T-Mobile daily cap are two different limits. Twilio's own documentation says the daily cap is imposed by T-Mobile toward its subscribers and is separate from message sending throughput.
2. It is set per EIN, not per account. Twilio states that the limit is applied at an EIN level and shared among all A2P brands and campaign use cases registered under that EIN.
3. It counts segments, not messages. The cap is measured on total outbound SMS segments plus MMS sent toward T-Mobile, including Sprint and MetroPCS. A long message costs several segments against the ceiling.
4. It follows the brand across platforms. Twilio's error reference for code 30023 says the count runs across any messaging platform the brand is registered with, and can include brands associated with other Twilio accounts or providers. Twilio's own worked example has one company sharing a single cap between its direct account and a third-party tool.
5. It resets on Pacific time. The daily limit resets at midnight, Pacific US time, which is not midnight for the client, the agency or the recipient in most cases.
6. Only the very largest brands start high. Businesses in the Russell 3000 Index receive 200,000 SMS segments and MMS per day toward T-Mobile by default, and T-Mobile lifts that ceiling only through a process called Special Business Review.

The trust score does not improve by itself

This is the line that changes how you should advise a client. Twilio's documentation states plainly that trust scores are static and do not automatically change over time. Sending clean, consented, low-complaint traffic for six months does not raise the number. The score is assigned during standard brand registration by The Campaign Registry, and Twilio names two causes of a low one: discrepancies in the data submitted, such as an address that differs from the one on the official business registration, and a small brand footprint.

HighLevel, which is where a lot of agency traffic actually originates, lists the same inputs from its side: legal business name accuracy, EIN or tax ID match, business address consistency, website quality, whether a privacy policy and terms of service are available, brand footprint, and consistency between the submitted details and the public ones. HighLevel also says it does not assign or manually change trust scores, so escalating to your platform's support desk will not move it.

Three fixes that do not work

Buying more numbers does not help. Twilio allocates a set maximum throughput per registered campaign, shared across all the long code numbers on that campaign and all carriers, so splitting sends across ten numbers gives you the same ceiling as one. Moving platforms does not help either, because the cap is keyed to the EIN and travels with the brand. And registering a second brand under the same EIN does not buy a second allowance, since the limit is shared among all brands under that EIN.

Registering as a sole proprietor to dodge the paperwork is the worst of the three. Sole proprietor brands have no EIN and no trust score at all, and HighLevel puts their fixed throughput at 2.25 SMS messages per second in total toward the major US networks, with 0.25 toward AT&T and one per number toward T-Mobile and Verizon. That is a deliberately small lane.

What it means for operators

Fix the registration data, not the sending. An appeal is the only route that moves a trust score, and Twilio says an appeal for a US brand usually needs the IRS EIN letter, sent with the account SID to its 10DLC onboarding team. Before you appeal, make the client's public record match the submission exactly: the legal entity name, the registered address, a live privacy policy and terms of service on a real domain. Those are the inputs the scorer reads.

Then design around the ceiling rather than into it. Cap daily sends per sub-account so one client's blast cannot spend another's allowance under a shared EIN, schedule heavy campaigns against the Pacific midnight reset rather than local business hours, and keep transactional traffic away from marketing traffic so a promotion cannot starve the appointment reminders. For a home services client, that last point is the whole business: the missed call text back that recovers a booking is worth more than the promotional blast that used up the allowance, so it should never be queued behind it. That is exactly the failure mode our AI calling for home services builds are designed around, and it sits alongside the consent and disclosure work in TCPA compliant AI calling.

If the campaign never got approved in the first place, the daily cap is not your problem yet. Start with why A2P 10DLC campaigns get rejected, then come back to the ceiling.