This article contains information about T-Mobile 10DLC. To review requirements set by other carriers or learn more about 10DLC as a whole, check out our 10DLC Overview.

Note: For T-Mobile 10DLC surcharges, please see carrier surcharges.

Fees for violation of practices spelled out in the T-Mobile Code of Conduct:

Fees will be assessed for every Sev-0 violation issued.

To avoid increased fees, please register your brands and campaigns as soon as possible:

Note: 527 organizations (i.e., non-profit organizations under Section 527) that have political use cases must also register with Campaign Verify to have their brand vetted and receive a token. For more information, see the Political messaging definition in 10DLC campaign use cases.

T-Mobile’s 10DLC Daily Cap is a throughput limit on the amount of messages a brand can send to T-Mobile users per day. The T-Mobile Daily Cap includes T-Mobile, and their MVNOs. It’s shared between SMS, MMS, and all campaigns under a brand (per EIN).

For Standard use cases, the daily cap depends on the tier assigned by T-Mobile (Top, High Mid, Low Mid, or Low). By default, your brand will be assigned a Low tier, meaning your brand can send T-Mobile a maximum of 2,000 messages per day on it. Once that limit is reached, all messages on that brand will be rejected with error code (4)780. The daily cap resets at midnight PT.

Note: If you have a brand with campaigns across several providers, all campaigns under the same brand/EIN will share the daily cap.

To increase your brand tier, you have to complete the third-party vetting process. If you’re registering through Bandwidth (rather than directly through TCR), please follow these instructions.

* In the T-Mobile Daily Cap column, the term “Standard” refers to T-Mobile’s standard throughput policy. The brand will start in Low and can apply for Standard vetting to try and increase their throughput.

** For Political use cases, there are other considerations that determine the throughput for T-Mobile:

*** Government entities will receive the Uncapped policy for T-Mobile if they have a verified Government Entity Status (“Government Entity: TRUE”). If they don't have a verified Government Entity Status (“Government Entity: FALSE”), they will receive the Standard throughput policy.

The requirements for a T-Mobile Special Business Review (SBR) focus on each brand you may have, and external vetting is required to be completed before applying for an SBR. If you expect your brand to send more messages than your daily throughput allows, please follow the instructions below to be considered for an SBR:

Note: While there's no set SLA or guaranteed timeline when it comes to Special Business Reviews, barring any missing application information, an SBR generally takes 2 months to be reviewed and implemented. This timeframe could be extended if more information is needed by the aggregator or carrier, the size of the review queue, and install times based on network availability.

Here are some of the terms you’ll find on the form:

T-Mobile will consider reduced pricing for the following use cases, on a case-by-case basis:

To qualify for reduced pricing, a Pricing Special Business Review must be submitted and approved by T-Mobile. Please reach out to [email protected] to request the pricing form and for further instructions.

Important: Satisfying any criteria above is not a guarantee of approval. Fee reductions are offered at T-Mobile's discretion, will be re-evaluated on an annual basis, and may be revoked or reduced at any time.

T-Mobile has implemented a limit of 49 numbers per campaign in an effort to combat snowshoeing and ensure brands and campaigns are registered as intended (see note about ISVs below). If more than 49 telephone numbers (TNs) are legitimately required on one campaign, a Number Pool must be assigned to the campaign.

Note: Independent Software Vendors (ISVs) are customers that support many brands (e.g., an ISV can support hundreds of dental offices). All of the individual brands the ISV supports are required to be registered individually on their own campaign, as opposed to creating a Number Pool.

A Number Pool allows you to apply more than 49 TNs to an approved campaign.

Note: Assigning number pools to 501(c)(3) campaigns requires a separate account in the Bandwidth App. This is because number pool ranges are linked to a single NetNumber ID (NNID) and Bandwidth can only support one NNID per service account. If you need a number pool for a 501(c)(3), please open a support ticket to discuss setting up a separate account.

If you have a use case that has a legitimate need for >49 TNs per campaign, please create a ticket under the reason "Number Pools" when asked "What do you need help with today?".

Note: Please use "CAMPAIGN ID Number Pool Request" as the subject line. An example would be: "C7GH42I Number Pool Request."

This will open a support ticket in which we will communicate a decision on the request. If approved, we will follow up on the ticket once the number pool is assigned to the campaign.

Important: Checking the box for Number Pooling in TCR or the Bandwidth App does not constitute a Number Pool approval. The application must still be submitted and approved by Bandwidth.

Providing detailed form responses will give Bandwidth a better picture of your traffic and help process your request in a timely fashion. We also advise providing detailed campaign descriptions and sample content, as this is what the carriers will be reviewing if there's ever an issue with your campaign.

This should mirror the campaign type from your campaign registration. If the campaign is Mixed Use, please identify all appropriate use case categories, not just one.

👎 Not recommended: "Mixed: “Account Notifications”."

👍 Recommended: “Mixed: Account Notifications, 2FA, Customer Care, Marketing.”

List the steps a consumer takes to agree to receive SMS messages for this campaign, and provide a screenshot of the opt-in method, copy of a flier with a keyword, or any other proof of opt-in used.

👎 Not recommended: "Consumer can opt-in via SMS."

👍 Recommended: “Consumer can opt-in to receive SMS messages by texting SUBSCRIBE. They also have the option to text HELP for help or STOP to opt-out afterward."

Please only submit a Number Pool order for campaigns that have gone through vetting and have been approved. Number Pools cannot be assigned to campaigns that are currently in pending or declined status.

Please assign and provide at least one number to the campaign in order for our aggregator to test if the Number Pool is properly provisioned when approved.

Please provide us with your best estimate of how many TNs you anticipate you will need to assign to this campaign. If you already have numbers on the campaign please provide us the total you expect to need. If you don't need more than 49 TNs you don't need a Number Pool.

We need a clear picture of why more than 49 numbers are needed for a single campaign.

👎 Not recommended: “More than 50 Agents/locations.”

👍 Recommended: “We have 50 agents working on a personal basis with the customers, who expect that number to be associated with their agent.”

Provide as much detail as possible so it can be confirmed as a valid assignment (e.g., one number per agent, one number per store location, etc.)

👎 Not recommended: "Each employee has their own phone line."

👍 Recommended: We have 25 locations in the US and each employee (~100 employees per location) has a dedicated line."

Please provide your best estimate of how much total messaging traffic you plan on sending from this campaign each day.

Please provide the percentage of traffic coming from your campaign that will be SMS.

Please provide the percentage of traffic coming from your campaign that will be MMS.

👍 Recommended: If you add together your SMS Traffic Distribution to your MMS Traffic Distribution, they should total 100%.