You scheduled the flash sale text for 12:00 sharp. Limited-quantity drop, 50,000 opted-in contacts, a discount code that expires at 3 PM. You hit send at noon and watch the delivery counter climb — and by 12:15 it's only at 40%. The customer who got the text at 12:38 hits a page where the popular size is already sold out. She's annoyed, she replies STOP, and you've now got a support ticket instead of an order.
The culprit isn't your platform lagging. It's a carrier-enforced ceiling on how many messages per second (TPS — transactions per second) your registered 10DLC number is allowed to push. Nobody mentions it until you feel it, and you always feel it during a time-sensitive blast.
Full disclosure: I work for Ready, an SMS platform. We handle 10DLC registration in-app, so I spend a lot of time explaining throughput math to people who assumed "send" meant "sent."
TPS is a speed limit, not a total cap
Two different limits govern your 10DLC traffic:
- Daily message cap — how many messages your campaign can send in 24 hours (tied largely to your T-Mobile brand vetting tier).
- Throughput (TPS) — how many messages per second the carriers will accept from your number.
The daily cap is usually not what bites you on a flash sale — 50,000 messages fits comfortably inside most daily allowances. TPS is what stretches your "instant" send into a slow drip. Even if you're allowed to send 200,000 messages today, you can only hand them to the carrier so fast.
For a standard, un-vetted 10DLC brand, aggregate throughput often lands somewhere around 10–90 TPS across carriers, depending on your vetting score and which carrier you're delivering to. It's not one clean number — AT&T and T-Mobile meter differently, which is a whole separate headache I won't relitigate here (we wrote about the carrier split if you want it).
The arithmetic on a 50,000-contact blast
Let's do the math instead of hand-waving. Take a single registered number and assume a realistic blended throughput of ~30 TPS for a low-to-mid vetting score:
`` 50,000 messages ÷ 30 messages/second = 1,667 seconds ≈ 27.8 minutes ``
Nearly half an hour before the last person hears from you. Now say your message runs long — a 175-character promo with an emoji. That emoji forces the whole message into Unicode, which drops your segment size to 70 characters, so your one "text" is actually 3 segments. Carriers meter segments, not messages:
`` 50,000 contacts × 3 segments = 150,000 segments 150,000 ÷ 30 TPS = 5,000 seconds ≈ 83 minutes ``
Your noon flash sale now finishes delivering at 1:23 PM. The person at the back of the queue got a "limited drop" text an hour and 23 minutes after it opened.
Bump throughput to ~90 TPS (a stronger vetting position) and that same 150,000-segment send lands in about 28 minutes. Still not instant — but the difference between a 28-minute tail and an 83-minute tail is the difference between a sale that feels live and one that feels like leftovers.
The lesson buried in that math: kill the emoji and tighten the copy. Getting your message under 160 GSM-7 characters turns 3 segments back into 1 and cuts your send time by two-thirds before you touch anything at the carrier level. Free speed.
Throughput scales with your vetting score
Your T-Mobile brand vetting score is the single biggest lever on how fast you can send. A higher score raises both your daily cap and your throughput tier. This is why the $40 brand vetting upgrade is worth it for high-volume, time-sensitive senders and pointless for someone texting 300 appointment reminders a week.
Rough shape of the tiers (approximate — carriers adjust these and don't publish exact figures):
| Vetting posture | Typical daily cap (T-Mobile) | Practical throughput | 150k-segment blast finishes in |
|---|---|---|---|
| Standard, low score | ~2,000/day | ~10–20 TPS | 2–4 hours (and you may hit the daily cap) |
| Standard, mid score | ~10,000–40,000/day | ~20–40 TPS | ~1–1.5 hours |
| Vetted (higher score) | ~200,000/day | ~60–90+ TPS | ~28–42 minutes |
If your low-score daily cap is 2,000 messages, a 50,000-contact list doesn't just send slowly — it can't finish in a day. That's a different, worse problem than a slow tail, and it's the one that catches nonprofits off guard on Giving Tuesday and ecommerce brands on their first big drop.
We go deeper on how the score maps to the cap in this breakdown of vetting tiers.
When you actually need more than one number
Throughput is per-number, so two numbers roughly double your ceiling — with real caveats.
Adding a second registered number to spread the load makes sense when:
- You're consistently pushing tens of thousands of segments in a tight window (flash sales, Giving Tuesday, event day-of reminders).
- Your vetting score is already as high as it's going to get and you still need more speed.
- You can genuinely attribute different traffic to different numbers — a support line and a marketing line, say. Splitting the same campaign across numbers purely to game throughput is the kind of thing carriers frown on, so do it with a real use-case rationale.
Adding a number doesn't make sense when the real fix is cheaper: raising your vetting score, or shortening your message from 3 segments to 1. Solve the free problems before you pay for parallel numbers with their own ~$10/mo brand and ~$20/mo campaign carrier fees.
And whatever you do, don't try to solve throughput by sitting on a shared number with hundreds of other businesses — their spam complaints tank your delivery regardless of how clean your list is. We covered why that backfires separately.
Plan the send backward from your deadline
If your discount expires at 3 PM, work the arithmetic in reverse:
- Count your real segments. Contacts × segments-per-message. Check whether an emoji or a long URL is silently tripling your count.
- Estimate throughput from your vetting posture. Use the table above as a floor, not a promise.
- Divide. Segments ÷ TPS = seconds to fully deliver. Add a buffer — carrier load in busy midday windows can drag actual throughput below the theoretical cap.
- **Set send time so the last message lands with margin.** If the tail takes 45 minutes, don't start at 2:30 for a 3:00 expiry. Start at 1:45.
That last-message-first mindset is the one operators miss. You're not planning when the send starts — you're planning when the slowest customer in the queue gets their shot at the deal.
Timezones stack on top of this: a noon send is 9 AM for your West Coast contacts and may butt against quiet-hours rules, which pause delivery entirely for some of your list. That's not slow throughput — that's messages held until a legal send window opens. Different mechanism, same visible symptom of "why isn't everyone getting it."
Where Ready fits
Ready handles the 10DLC registration in-app — brand and campaign, with same-day approval for most senders (typical range is 1–3 days). That matters here because the whole throughput conversation is downstream of being registered correctly: unregistered traffic gets carrier-filtered before TPS is even relevant, and a mismatched use case (marketing vs. transactional) quietly throttles you no matter your score.
On pricing, Ready is $0.02/segment on the Standard tier plus the $0.0045 carrier pass-through, billed separately so you can see exactly what's carrier fee and what's platform. Segments — not messages — is the unit, which is precisely why the emoji math above hits your bill and your send time at the same time. Past 50,000 segments in a calendar month the rate automatically drops to $0.016. See the full pricing if you want to run your own numbers.
I'll be straight: a raw CPaaS API can meter throughput just as well and sometimes cheaper per segment. What you're buying with Ready is the registration done fast and the full platform around it — inbox, automations, dialer, GHL sync — without stitching it together yourself. If you're a developer who just wants an API and already has your A2P sorted, that's a legitimate reason to look elsewhere.
The practical takeaway
"Send" isn't "sent." Your flash sale delivers at the speed the carriers allow, and that speed is set by your vetting score, your segment count, and how many numbers you're sending across.
Before your next time-sensitive blast: count your segments, cut the emoji if you can, check your vetting posture against the table above, and plan the send so the last message lands before the offer dies. If the math still doesn't fit your window, that's your signal to raise your vetting score or add a second number — in that order.
If you want to pressure-test your own numbers, start a Ready account — 2,500 free credits, no card — and register a real campaign to see what throughput your brand actually gets before the big day, not during it.