All Collections
10DLC Compliance
Carrier Compliance
Message throughput (MPS) and Trust Scores for 10DLC in the US
Message throughput (MPS) and Trust Scores for 10DLC in the US

We'll go over what SMS throughput means and how it's calculated based on your Trust Score and Campaign Type.

Updated over a week ago

Under the new 10DLC service for sending messages via 10-digit long code numbers in the United States, there are changes to how message sending throughput is allocated. 10DLC message throughput in the US will now be determined based on your Trust Score and your Use Case (“Campaign”) type. This guide gives an overview of these changes, and how throughput is allocated.

T-Mobile will also impose daily message limits toward their subscribers. This is separate from message sending throughput. See T-Mobile daily message limits for long code messaging with 10DLC for details.

Throughput overview

Message sending throughput for SMS is measured in message segments per second (MPS). Each message segment consists of up to 160 GSM-7 encoded characters, so an SMS with more characters and/or different character encoding can be comprised of multiple segments. For full details, see What is a segment?

In the past, SuperPhone’s MPS for US long code numbers was set at a standard 1 MPS per phone number, shared across all mobile carriers. This rate is changing under the new 10DLC service. Going forward, MPS throughput will be determined based on the sender's Trust Score, and the messaging Campaign type (use case).

What is a Trust Score?

A Trust Score is a score assigned during Brand registration with The Campaign Registry (TCR - the 3rd party that administers the US wireless carriers' new registration system). When a registration for US 10DLC messaging is submitted to SuperPhone, we send this information to TCR for review. SuperPhone also submits the Brand for "secondary vetting," which assigns a score from 0 to 100 and gives access to higher default throughput and message limits toward US mobile carriers.

The Brand registration process uses a reputation algorithm to review specific criteria relating to your company, and then assigns a “Trust Score”. In short, the higher your Trust Score, the higher your messaging throughput (MPS).

T-Mobile will also impose daily message limits toward their subscribers. See T-Mobile daily message limits for long code messaging with 10DLC for complete details.

What if I am not satisfied with my Trust Score? Can I appeal?

In many cases, a low Trust Score is the result of data discrepancies in the information you submitted in your registration; for example, a different address than the one associated with your official business registration number (e.g. EIN).

If you receive a low Trust Score, SuperPhone will do our best to offer guidance on possible causes or resolution for a low score. If this applies to you, please send us a message using the chat bubble in the bottom right corner, or the on the mobile app via Settings → Support.
.

How is throughput (MPS) allocated for 10DLC?

A set maximum MPS is granted for each of your registered campaigns (use cases) with SuperPhone. This MPS is shared across all US/Canada long code numbers allocated to your account, and all wireless carriers. Whether you choose to send messages over a single number to a specific carrier, or split up messages over a collection of local numbers to multiple carriers, the same MPS limit applies.

Specific Use Cases (what carriers call “Declared” Campaigns) may receive higher MPS for the same Trust Score than a “Mixed” or Marketing type Use Case.

For a full list of Use Case and Campaign types as defined by carriers, and their respective per-message fees and other considerations, see List of Campaign Types and Use Case Types for 10DLC registration.

Is MMS throughput also affected?

No. As of September 2021, MMS throughput via long code numbers on SuperPhone remains unchanged, at a total of 25 MMS per second to all US and Canadian networks.

We expect MMS throughput to also be affected by 10DLC changes in the future, but do not yet have specifics. SuperPhone is continuing to work with carriers to get full details of MMS changes, and will update this article with any changes to MMS throughput when information is available.

Is Toll-Free SMS throughput affected?

No. Toll-Free SMS is not affected by the throughput changes described in this article, nor is it subject to the new campaign registration requirements. A US Toll-Free number has a total of 3 MPS toward all US and Canada carriers by default. You can request higher message throughput for a US Toll-Free number by sending us a message using the chat bubble in the bottom right corner, or the on the mobile app via Settings → Support.

Is messaging to Canada affected?

Messaging to Canada from a Messaging Service registered with a US 10DLC use case will be sent at 9 MPS per Canada mobile carrier.

This limit is set to prevent exceeding throughput constraints put in place by Canada carriers.

Is messaging to countries other than the United States affected?

No.

Declared Use Cases: Message Throughput

A Declared use case means you have chosen one specific non-marketing use case (examples: 2FA, Account Notifications, etc.). For a full list, see List of Campaign Types and Use Cases.

Mixed / Marketing Use Cases: Message Throughput

Mixed / Marketing use cases can be registered for customers who want to send messages for multiple use cases from the same set of numbers, or for marketing. Different throughput levels are allocated for Mixed / Marketing use cases than for Declared use cases.

Trust Score

Total SMS MPS toward major US networks*

AT&T SMS MPS

T-Mobile SMS MPS

Verizon SMS MPS

85 - 100

225

75

75

75

65 - 84

120

40

40

40

25 - 64

12

4

4

4

15 - 24 (or Low Volume Mixed Campaign)

3

1

1

1

Special Use Cases

Special use cases are a distinct category that encompass specific campaign types. In some cases, these will require special review by carriers. For details, see Special Use Cases for 10DLC.

Please note that Trust Score will not impact messages per second (MPS) throughput for Special use cases.

Did this answer your question?