You registered your 10DLC brand, got the campaign approved, started sending, and then one day a chunk of your list stopped getting messages. No error you'd notice. The sends just queued and dribbled out over the next day, or got dropped entirely. The culprit usually isn't your content. It's a per-brand daily message limit that T-Mobile attaches to your brand based on your trust score, and a standard, unvetted brand sits at the bottom of that ladder.
Full disclosure: I work for Ready, an SMS platform with self-serve 10DLC built in. So I have a horse in this race. But the throughput tiers I'm about to walk through are set by the carriers and The Campaign Registry, not by us, they apply no matter whose platform you send on. The only thing I'll argue is when paying the one-time vetting fee actually earns its keep.
The cap nobody mentions until you hit it
T-Mobile enforces a brand-level daily message cap, a ceiling on how many messages your entire brand can deliver to T-Mobile subscribers in a 24-hour window, regardless of how many campaigns or numbers you run. That cap is tied to your brand's trust score.
The score comes out of registration. A standard (unvetted) brand lands somewhere in the low range, and that pins your daily T-Mobile throughput to roughly 2,000 to 3,000 messages per day. Not per second, per day. For a lot of senders that's plenty. For a mid-volume brand or an agency running multiple clients, it's a wall you hit without warning.
Here's the rough ladder (these are carrier-side tiers, approximate, and T-Mobile adjusts them over time):
| Brand trust score | Approx. daily T-Mobile cap |
|---|---|
| Unvetted / low (standard reg) | ~2,000 to 3,000/day |
| Mid (score ~50 to 74) | ~40,000/day |
| High (score ~75+) | ~200,000/day |
| Top tier (vetted, strong profile) | ~2,000,000+/day |
Enhanced vetting is what moves you up this ladder. It doesn't guarantee a specific number, the score is assigned by a third-party evaluator based on your business profile, but it's the mechanism that turns a 3,000/day brand into a 200,000/day brand. If you want the deeper breakdown of exactly what 25 vs 75 unlocks, we wrote that up in what a 25 vs 75 vetting score actually unlocks.
What vetting costs vs. what you're already paying
Standard 10DLC on Ready runs the normal carrier fees: roughly ~$10/mo per brand and ~$20/mo per campaign, approval typically 1 to 3 days, often same-day. That's the baseline every registered sender pays, vetting or not.
Brand vetting is a separate, one-time fee on top:
- Standard vetting, $79, one-time
- Enhanced vetting, $179, one-time
One time. Not monthly. You pay it once, the evaluator scores your brand, and the higher daily cap sticks as long as the brand stays registered. So the real question isn't "can I afford $179", it's "does my send volume justify needing the headroom."
The worked example: a mid-volume sender hitting the wall
Say you run a brand with 45,000 opted-in contacts. T-Mobile is the largest US carrier, so assume roughly a third of your list (15,000 contacts) are on T-Mobile. (Rough approximation; your actual split varies by region and audience.)
You send a weekly promo. Each message is a tidy 155 characters, GSM-7, so one segment each.
On a standard unvetted brand (~3,000/day T-Mobile cap):
- You need to deliver 15,000 messages to T-Mobile numbers.
- At ~3,000/day, that's 5 full days to clear a single weekly blast to just the T-Mobile portion of your list.
- Your "Tuesday 10am flash sale" finishes landing the following Sunday. The offer is dead before half your T-Mobile contacts see it.
That's not a cost problem. It's a the-message-arrives-too-late-to-matter problem, which is worse, because you paid to send it and got no window.
On an enhanced-vetted brand (~200,000/day):
- 15,000 T-Mobile messages clear well inside the first hour (now your real constraint becomes per-second throughput, TPS, which is a separate ceiling, more on that in a second).
- The whole 45,000-contact blast lands as a blast instead of a slow leak.
The vetting fee that fixed this: $179, once. Against a list you're presumably monetizing every single week, that math isn't close.
What you spend on the messages either way
The send cost is the same whether you're vetted or not, vetting changes speed, not per-message price. On Ready Standard that 45,000-contact single-segment blast is:
45,000 × ($0.02 + $0.0045 carrier fee) ≈ $900 + carrier pass-through per blast.
Spending ~$900 a week on sends while a $179 one-time fee is the only thing standing between "lands in an hour" and "dribbles out over five days" is exactly the kind of trade where the fee is a rounding error. Run your own numbers on the pricing page.
Vetting fixes the daily cap, not the per-second one
Worth being honest here: raising your daily cap is only half the throughput story. There's also TPS, messages per second, which controls how fast your approved volume actually streams out. A brand can have a 200,000/day cap and still have its noon flash sale trickle out over 40 minutes because TPS is the binding constraint in that hour.
So vetting solves "I can't send enough per day." It does not by itself solve "my instant blast isn't instant." For that, see why your 10DLC number can only push ~90 texts a second and the broader TPS ceiling explainer. If you're a time-sensitive sender, you want both the daily headroom and enough TPS.
When vetting is NOT worth it
I'll say the unglamorous part. Most senders don't need vetting.
Skip it if:
- You send under ~2,000 messages/day to T-Mobile. A standard registration covers you. Spending $179 to unlock headroom you'll never touch is waste.
- You're transactional-only (appointment reminders, order updates, 2FA) at modest volume. Your daily counts are low and steady.
- You're a local business texting a few hundred contacts. The standard tier is built for exactly you.
Get Standard ($79) vetting if:
- You're climbing toward 3,000 to 10,000/day on T-Mobile and starting to see sends queue.
Get Enhanced ($179) vetting if:
- You run genuine flash sales, drops, or time-boxed campaigns to tens of thousands of contacts.
- You're an agency consolidating multiple clients' volume, or a single brand pushing serious daily numbers.
- The cost of a message landing a day late is higher than $179.
We laid out the shorter version of this decision in is 10DLC brand vetting worth $79.
Agencies: the math compounds per client
If you run an agency, every client brand carries its own daily cap. Onboard 30 clients and leave them all unvetted, and you've got 30 brands each walled at ~3,000/day to T-Mobile, which is fine right up until one of them runs a promotion and floods a support ticket into your inbox asking why their sale "didn't send."
The move is to vet selectively: the clients with real volume get Enhanced at $179 one-time, the reminder-only locals stay standard. You're not blanket-spending, you're matching the fee to the send profile. And because Ready's 10DLC is self-serve with same-day approvals in most cases, you can register and vet a client the same week they sign, instead of the quarter-long slog manual A2P onboarding usually is. We walked through the batch flow in onboarding 30 agency clients the fast way.
The practical takeaway
The daily T-Mobile cap is real, it's tied to your trust score, and a standard brand sits near the floor at ~2,000 to 3,000/day. Enhanced vetting, $179, one-time, is the lever that moves you up toward ~200,000/day. The decision is simple:
- Low, steady volume → standard registration, skip vetting.
- Climbing into the thousands/day on T-Mobile → Standard vetting ($79).
- Real blasts to tens of thousands → Enhanced vetting ($179), and check your TPS too.
If you're not sure which bucket you're in, estimate your T-Mobile portion (roughly a third of your list), divide your biggest single-day send by 3,000, and see how many days it'd take to clear. If the answer is "more than one," you've already found your reason.
You can register a brand, pick a vetting tier, and start sending on Ready with your first 20 texts free, at app.tryready.com/signup. If you want the full picture on how a same-day approval even happens, here's the onboarding timeline.