One Carrier's Limit No Longer Slows the Whole Send
A text send is not one stream. It is three, one per major carrier, and each carrier sets its own limits.
Until now, a send moved at the pace of its slowest carrier. As of this month, it does not.
The Problem
Carriers limit registered 10DLC traffic per brand. The limits differ by carrier and by how the brand is vetted, and they bind hardest when election traffic peaks.
Run a send as a single queue and the tightest limit sets the pace for everyone. Recipients on a carrier with room to spare wait behind recipients on a carrier without it.
Lanes, Not a Queue
Political Comms now paces every carrier on its own lane.
A carrier at its limit slows only its own recipients. Every other carrier keeps sending at full speed. A send that used to wait on one carrier now finishes everywhere else on schedule.
Daily Caps, Decided Up Front
T-Mobile caps daily volume per brand. The cap is visible before launch, not discovered halfway through.
The launch dialog previews T-Mobile volume against the cap before you send.
At the cap, the project pauses cleanly. It waits until T-Mobile recipients are all that remain and nothing already queued is still in flight, then pauses and notifies you. Resume in the next day's window.
Or send straight through. Choose at launch to continue past the cap, with an acknowledgment that messages over the cap may fail.
Visible While It Runs
The send page shows which carrier is holding recipients. A slow lane reads as a carrier limit, not a mystery.
Pausing a project stops sending within seconds, on every lane.
Why It Matters Now
The weeks before an election carry the most volume of the cycle and the least tolerance for delay. A deadline ask that lands after the deadline raises nothing.
Per-carrier pacing means the carriers with room deliver now, and the carrier without it is visible, planned for, and contained.
Frequently Asked Questions
Why do carrier limits slow down a text send?
Each wireless carrier sets its own throughput limits for registered 10DLC traffic, based on the brand's vetting. When a send runs as one queue, the slowest carrier sets the pace for every recipient. Per-carrier pacing removes that coupling.
What happens when a brand reaches its T-Mobile daily cap?
The project pauses once T-Mobile recipients are all that remain and nothing already queued is still in flight, and you are notified. Resume in the next day's window, or choose at launch to send straight through, with an acknowledgment that messages over the cap may fail.
Can I see which carrier is holding a send?
Yes. The send page and launch dialog show which carrier is holding recipients, and the launch dialog previews T-Mobile volume before you send.