T-Mobile 10DLC trust score: what caps your texting, and how to raise it
After an A2P 10DLC brand registration, The Campaign Registry assigns a trust score from 0 to 100 and T-Mobile uses that score to cap daily message volume: scores of 75 to 100 get 200,000 messages a day, 50 to 74 get 40,000, 25 to 49 get 10,000, and under 25 get 2,000. The score is driven by the accuracy of the legal name, EIN, address and website on the brand record, so most low scores are fixable without a rebuild.
Published · Last updated · By Ghulam Qadir, Automation & Infrastructure Lead, LogixLevel
What the trust score actually is
The Campaign Registry (TCR) runs vetting on every US A2P 10DLC brand and returns a numeric trust score. T-Mobile is the carrier that enforces the tier most visibly, so the score is often called the “T-Mobile score” even though it also informs other networks. The score controls two things: how many messages you can send per day across your campaigns, and how fast you can send them (MPS, messages per second).
The daily caps on T-Mobile
T-Mobile publishes a tiered daily limit for SMS and MMS outbound traffic by brand:
| Trust score | Daily cap on T-Mobile |
|---|---|
| 75 to 100 | 200,000 messages |
| 50 to 74 | 40,000 messages |
| 25 to 49 | 10,000 messages |
| 1 to 24 | 2,000 messages |
Twilio documents the same tiers and notes that starting 18 March 2026, MMS messages-per-second also scales by trust score: 40 MPS at 75+, 20 MPS at 50 to 74, and 5 MPS under 50 per major carrier.12
For a service business running two campaigns (one marketing, one notifications) across a few sub-accounts, the real risk is not hitting the daily cap. It is the per-second ceiling causing throttling and delays during a batch send, which looks to the owner like “the texts went out but the leads got them an hour late”.
What raises or lowers the score
Twilio’s registration docs call out a short, dull list of fields that account for most of the score. These are the same fields that get brand registrations rejected outright:34
- Legal company name. Must match the IRS CP 575 or 147C letter character for character. “Acme Services LLC” and “Acme Services, L.L.C.” are not the same string. If a punctuation mismatch triggers a resubmission, the second attempt usually scores lower than a clean first attempt.
- EIN or Tax ID. EIN is strongly preferred. Registering with an SSN flags the brand and lowers the score. Sole proprietors should move to an EIN before registering if texting is core to the business.
- Registered business address. Street, city, state, ZIP and country must match the address of record for the EIN. A UPS box or a mail-forwarding service for an entity that files from a different address will usually drop the score.
- Website. The website on the brand record should be reachable, HTTPS, and clearly represent the registered entity. A WordPress login page, a parked domain, or a GHL funnel on a sub-domain without a privacy policy are the three failure modes we see most.
- DUNS, stock symbol, government flags. Public companies, non-profits and government entities can submit a DUNS number or stock symbol for a direct boost. Private service businesses skip this, which is fine.
Secondary signals that nudge the score up: a privacy policy at the website address with an SMS clause, matching contact details across the brand and the website, and consistent use of the legal name on invoices and the GBP listing.
How this ties to GoHighLevel
HighLevel’s LC Phone runs on Twilio, so TCR vetting is the same process regardless of agency. HighLevel’s own A2P form fills a single Brand record for the sub-account. Two things to check on a HighLevel setup:
- The brand is registered under the client’s EIN, not the agency’s. Agencies that register everything under one brand to speed up onboarding end up with campaigns tied to the wrong entity. When T-Mobile audits, those campaigns get suspended.
- Each sub-account uses its own campaign. A single campaign shared across clients mixes message content and raises the risk of a carrier complaint, which lowers the brand score over time.
If a brand is already live with a low score, the quickest lift is a resubmission with corrected fields plus brand vetting through TCR (external vetting). TCR’s second-opinion vetting can move a brand into the next tier within a few business days when the underlying data is now clean.
A checklist before you register
- Pull the IRS CP 575 or 147C letter. Copy the legal name exactly.
- Pull the EIN confirmation. Confirm the address matches the current operating address.
- Confirm the website resolves, serves HTTPS, and shows the legal entity in the footer.
- Publish a privacy policy that names SMS and consent explicitly.
- Pick one SMS use case per campaign (marketing, notifications, 2FA). Do not mix.
- Submit, then run a test send against three real US numbers across Verizon, AT&T and T-Mobile within the first hour of approval.
Why most low scores are fixable
In the brand registrations we have reviewed, roughly nine out of ten low scores trace to one of three issues: a legal name mismatch, an SSN instead of an EIN, or a website that does not represent the entity. None of those require a new entity or a new phone number. They require updating the brand record and resubmitting.
If you want us to review your HighLevel A2P setup and send you a one-page score report with the exact fields to change, book an audit. It is free and the output is specific, not generic.
Footnotes
-
Twilio, Message throughput (MPS) and Trust Scores for A2P 10DLC in the US. https://help.twilio.com/articles/1260803225669 ↩
-
Twilio, Increased MMS rate limits for A2P 10DLC Phone Numbers in the U.S. starting March 18, 2026. https://www.twilio.com/en-us/changelog/increased-mms-rate-limits-for-a2p-10dlc-phone-numbers-in-the-u-s0 ↩
-
Twilio, A2P 10DLC Brand Approval Best Practices. https://support.twilio.com/hc/en-us/articles/4405758341659 ↩
-
Twilio, Troubleshooting A2P 10DLC Standard/LVS Brands. https://www.twilio.com/docs/messaging/compliance/a2p-10dlc/troubleshooting-a2p-brands/troubleshooting-and-rectifying-a2p-standardlvs-brands ↩
