Blog
10DLC Throughput Limit Low Volume Campaign (2026)
- SMS
- 10DLC
- A2P
- Compliance
- Engineering
The 10DLC throughput limit on a low volume campaign: T-Mobile’s daily cap, AT&T’s per-minute cap, and why vetting does not raise it.

A low volume 10DLC campaign is the cheap, slow lane. It fits a few hundred messages a day. It does not fit an OTP burst or a digest that has to clear in a minute. The throughput limit is the campaign class. Secondary vetting does not lift it.
Alternatively, Pingram files the campaign for the volume you send. You do not pick Low Volume Mixed because the fee is lower and then discover the cap in production.
Two different “low volume” objects
Low Volume Mixed is the campaign. It covers a brand with several use cases, up to five of them: a demo account, a single shop, a test send. It is the class for under about 15,000 messages a month across carriers, when the traffic is not time-sensitive. The monthly campaign fee is lower. The throughput is the lowest tier, and it stays there.
Low-Volume Standard is the brand. That brand is capped at 2,000 SMS segments and MMS per day to T-Mobile, about 6,000 SMS segments and MMS per day across US carriers. It can hold up to five campaigns. The campaign on it still has to be a low volume campaign if you want the lower fee, and that campaign keeps the low cap.
Sole proprietor is a third bucket: 1,000 messages a day to T-Mobile, and one campaign. Do not apply the low volume campaign numbers to it.
Pingram treats these as a registration choice, not a default. A side project that texts a handful of users can sit on the low volume campaign. A product notification that will grow is registered as a standard campaign from the start.
The limit that actually binds
T-Mobile’s daily cap is a quota, not a messages-per-second setting.
The cap covers T-Mobile and its MVNOs. It is shared across SMS, MMS, and every campaign under the brand’s EIN, including the same brand registered at another provider. For a low volume campaign the number is 2,000 per day. There is no vetting score that raises it. Past the cap, messages to that brand fail with error (4)780 until midnight Pacific Time.
AT&T limits the same campaign to 75 SMS segments a minute.
Count segments. A UCS-2 message, or a GSM-7 message past 160 characters, costs more than one segment. A day of 2,000 segments is fewer than 2,000 notifications.
Verizon rate-limits 10DLC too. Size workers to the T-Mobile daily cap and the AT&T per-minute cap first. Those are the walls on this campaign class.
What to do when you outgrow it
Vetting does not promote a low volume campaign. These tiers apply to a standard campaign:
| T-Mobile tier | Vetting score | Daily cap |
|---|---|---|
| Low | 1–24 | 2,000 |
| Low Mid | 25–49 | 10,000 |
| High Mid | 50–74 | 40,000 |
| Top | 75–100 | 200,000 |
Low Volume Mixed stays at 2,000. The fix is a new campaign in a standard use case, on a Standard brand if you are on Low-Volume Standard. Vetting then applies to that campaign. A Special Business Review is the path past the top vetted tier. It generally takes about two months. It is not a way around a low volume campaign you already filed.
On your own, you wait for that new campaign to be approved, treat (4)780 as a quota error, and retry after midnight PT. Retrying immediately looks like a carrier filter.
With Pingram, we file the campaign appropriate to your volume, and request higher trust score vetting when appropriate before your application is throttled, not after. A low volume campaign still cannot be vetted into a higher tier. We do not leave you on that class and refile after (4)780.
Where this sits next to registration
Brand, campaign, and number attachment are covered in A2P 10DLC Registration: The Ultimate Developer’s Guide (2026). The throughput limit is the part you lock in when you choose the class. Switching later is a new campaign review. Wrong-class traffic is what carriers block.
Pingram handles that registration, including multi-tenant brands, so each customer has their own EIN-level cap. The guide is the do-it-yourself path. Pingram is the path where the campaign class is chosen for the traffic, and kept current.
TLDR
A 10DLC low volume campaign is capped at 2,000 a day to T-Mobile per brand, shared across campaigns for that EIN, and 75 SMS segments a minute on AT&T. The T-Mobile number counts segments and MMS. Secondary vetting does not lift it. A standard campaign is what trust score can move, up to 200,000 a day at the top tier. Pingram files the class that matches the volume, instead of leaving the product on the low volume cap.
Common questions
01What is the 10DLC throughput limit on a low volume campaign?
As of October 5, 2026, a low volume campaign is capped at 2,000 messages a day per brand to T-Mobile and 75 SMS segments a minute on AT&T. The T-Mobile ceiling counts SMS segments and MMS. Vetting does not raise it. Pingram registers the campaign class for the volume you actually send, so a product that will outgrow 2,000 a day is not filed as low volume.
02Does a higher trust score increase a low volume campaign?
No. A low volume campaign stays at 2,000 a day to T-Mobile. Trust score moves a standard campaign between tiers, from 2,000 up to 200,000 a day. With Pingram, we file the campaign appropriate to your volume, and request higher trust score vetting when appropriate before your application is throttled, not after. A higher score on a low volume campaign does not change the cap.
03What happens when the T-Mobile daily cap is hit?
Further messages to that brand are rejected with error (4)780 until the cap resets at midnight Pacific Time. The cap is shared across SMS, MMS, and every campaign under the same EIN. Pingram registers each customer as their own brand, so one tenant’s volume does not consume the platform’s cap.