Registration gets your campaign approved. Throughput determines whether your messages actually arrive when they’re supposed to — and it’s where messaging programs quietly break at scale. A campaign can be perfectly compliant and still fail its users because it hit a limit no one planned for.

Throughput is governed by two separate constraints, and confusing them is a common mistake. TPS — messages per second, also called your velocity limit — is a rate limit that caps how fast you can send to a given carrier. Daily brand caps, most visibly T-Mobile’s, limit how many messages a brand can send in a day regardless of speed — and here’s the part that catches people: T-Mobile enforces that cap at the brand level, across every provider carrying your traffic. What you send through Tychron and what you send through any other messaging partner both count against one shared daily number, so splitting volume between providers doesn’t create two allowances — it draws down the same one. You can sit under your per-second rate all day and still hit the brand’s daily ceiling.

Cross a carrier’s throughput limit and messages don’t simply wait politely. Depending on the network you see rate-limit errors, queuing, delivery delays, and — for traffic that keeps pushing — filtering. The damage lands hardest exactly where it hurts most: login-time two-factor codes, real-time alerts, and other bursty, time-sensitive traffic that can’t absorb a delay.

Per-carrier throughput comes from your brand’s trust score and your 

, established at registration. A higher trust score and a well-matched use case raise the ceiling; a mismatched or under-declared use case caps it early. If you need more headroom, that’s where the work starts.

Here’s where the provider you choose actually matters. Tychron has run 

 since 2021: our platform automatically sends your messages to each US carrier and known Canadian carrier based on the throughput approved for your campaign, so you never exceed your velocity limits. You hand us the burst, and we pace it to exactly what each network will accept — you get delivery instead of a wall of rejection errors, and it’s included, not a premium add-on. We announced this publicly in October 2021 — on 

, well before the approach became fashionable. Plenty of providers still do the opposite: they pass carrier throttling straight back to you as errors and leave you to build the pacing logic yourself.

Spread predictable bursts where you can, instead of firing everything at the top of the hour.

Prioritize time-sensitive traffic like one-time passcodes over bulk sends.

Right-size your use case so your ceiling matches your real volume.

Watch delivery per carrier, not just in aggregate — limits are network-specific.

Improve your brand trust score, make sure your 

, and build a clean sending history. For a real step up, go through external third-party brand vetting and then apply the new limits to your campaign, so the higher throughput actually takes effect. Throughput rises as carriers see consistent, compliant volume — and a stronger vetting score lifts the ceiling directly.

Does throughput pacing delay urgent messages?

Pacing applies when you’re sending faster than a carrier will accept — and time-sensitive traffic can be prioritized within it, so one-time passcodes aren’t stuck behind a bulk campaign. The alternative, sending over the limit, is what actually delays them, as rejections and retries.

Is dynamic carrier throughput an extra charge?

No — it’s included. Pacing your traffic to each carrier’s real limits is part of how delivery is supposed to work, not a feature to upsell.

Throughput itself isn’t a line item, but the 

 do vary by carrier and message type — so how and where your volume lands still shows up on the invoice.

Disclaimer: This article is general information, not legal or compliance advice. Carrier rules, CTIA guidelines, and 10DLC and toll-free requirements change often and are enforced at the discretion of the carriers and their vetting partners. Tychron makes no warranty as to its accuracy or completeness and accepts no liability for actions taken in reliance on it — confirm current requirements with the relevant authorities and your own counsel before acting.

Tell us your burst patterns and volumes, and we’ll show you how dynamic carrier throughput paces them to full delivery across every carrier.

Velocity Limits and Dynamic Carrier Throughput

Trace almost any 10DLC or toll-free rejection back to its root and you tend to land in the same place: the reviewer couldn’t confirm how consumers agreed to be texted. The opt-in is the load-bearing part of a messaging program. Get it right and most of the review takes care of itself; get it wrong and nothing downstream saves you.

Consent, in the A2P sense, is explicit, documented, and specific to messaging. A consumer has to take a clear affirmative action to receive texts from your program — not agree to a general terms-of-service that happens to mention SMS somewhere. If the agreement to be messaged isn’t distinct and demonstrable, it doesn’t count.

, a compliant flow makes all of the following visible:

The program or brand name, so it’s clear who will be texting.

The type of messages and their frequency — “recurring,” “varies,” or a specific cadence.

Links to your Terms and your Privacy Policy, near the opt-in itself.

Placement matters as much as presence. The disclosures belong at the moment of consent — beside the form field or submit button, not buried a click away or surfaced only after signup. Whatever the channel — web form, keyword, point of sale, or verbal — the consumer should see what they’re agreeing to at the moment they agree.

A surprising number of campaigns are undone by their own privacy policy. If your policy says you share or sell consumer data and doesn’t explicitly carve out messaging opt-in and consent information, a reviewer reads that as a contradiction and 

. The fix is a clear line stating that mobile information collected for messaging isn’t shared with third parties for their marketing — and that opt-in data stays with the program.

Reviewers check your live opt-in against what you submitted. Screenshot the flow, keep the URL working, and make sure the page still says what your registration says it does. A description that no longer matches the live page is a rejection waiting to happen — and the same discipline carries straight over to 

Not universally, but a confirmed opt-in is the strongest evidence of consent and is expected for some use cases. When in doubt, confirm.

Only with prior express consent you can actually demonstrate for messaging specifically. A list gathered for email or general marketing doesn’t automatically carry SMS consent.

The consent standard is the same; the submission path differs. The disclosures and documentation you build for 10DLC carry over directly to 

Share your opt-in flow and privacy policy — we’ll check them against current carrier standards so the submitted version is the one that passes.

Designing an Opt-In That Passes Review

Toll-free numbers look like the easy path into A2P messaging. They’re already business-owned, they don’t require 10DLC brand-and-campaign registration, and they carry a trusted reputation with consumers. But there’s a step most senders discover the hard way: an unverified toll-free number can’t send at all. Since November 2023 the industry blocks every message from an unverified toll-free number, so verification is what turns it from blocked into a real messaging channel.

Application-to-person traffic on toll-free numbers runs through the toll-free messaging ecosystem, and every number sits in one of three states. Unverified numbers — never submitted for verification, or previously verified and since revoked — are blocked outright (since November 8, 2023), and as of January 31, 2024 numbers still pending review are blocked too; traffic from either is rejected with carrier error 64. Verified numbers are the only ones that originate traffic — they get full throughput and protection from the spam blocking that hits unvetted traffic. Verification is the vetting process that moves a number from blocked to sending — you attest to who is sending, what you’re sending, and how consumers agreed to receive it.

Verification looks at the same fundamentals carriers care about everywhere in A2P messaging:

Business identity — a real, resolvable company that matches the numbers you’re sending on.

Use case and sample messages — what the program does, and examples that read like the declared purpose.

Opt-in and consent — how consumers agreed to be messaged, 

Working links — a live website and a privacy policy that supports messaging consent.

None of it is exotic. It’s the same checklist that 

 — which is why the same preparation clears both.

 the reviewer can’t actually find or reproduce. Sample messages that read like marketing on a campaign declared for notifications. A privacy policy that says you share consumer data without carving out messaging consent. Identity details that don’t line up with registration records. Each one is fixable before submission — and far cheaper to fix then than after a rejection.

Don’t plan a launch — or even a test — on a number that isn’t verified yet; nothing originates until verification is approved. Verification review typically takes a few business days, though clean submissions move faster than ones that trigger follow-up questions. Once verified, the number sends at full toll-free throughput and gains the spam-filtering protection that unverified traffic never gets — which, for anything time-sensitive like one-time passcodes, is the difference between a channel you can rely on and one you can’t.

We prepare and submit toll-free verification the same way we handle 

: reviewed in-house against current standards before it goes downstream, so the version that gets submitted is the version that passes. It’s billed at cost, with no markup on the verification itself — and if you’re weighing toll-free against 10DLC for a given program, we’ll tell you 

Can I send toll-free A2P before verification?

No. Unverified toll-free numbers have been blocked since November 8, 2023, and numbers still pending review since January 31, 2024 — both rejected with carrier error 64. A number has to reach verified status to originate any traffic, so submit for verification well before you plan to launch.

Toll-free or 10DLC — which should I use?

Both are legitimate A2P paths. Toll-free suits many notification and alert programs and avoids 10DLC’s brand-and-campaign registration; 10DLC suits local-presence and high-throughput programs. The right answer depends on your traffic, and 

Does verification need to be updated later?

If your use case, opt-in flow, or volume changes materially, the verification should reflect it. Keeping the live opt-in page matching what you submitted is the simplest way to stay in good standing.

Tell us your numbers and use case — we’ll prep the verification, review it against current standards, and submit the version that passes.

Simple solutions for complex problems

Understand and take control of your network with powerful APIs

Location Routing Number (LRN) & eLRN Lookup

Caller ID Name (CNAM) Lookup w/ Robocall Status

Message Carrier Lookup (MCL)

Dig Deeper

Velocity Limits and Dynamic Carrier Throughput

Designing an Opt-In That Passes Review

Toll-Free Verification, Explained

Got Questions?