T-Mobile Surcharge Passthrough Fees

The below fees will apply to both registered and unregistered traffic toward users on T-Mobile (including Sprint). Starting October 1, 2021, T-Mobile will increase carrier fees for unregistered traffic to $0.004 per SMS segment (rather than $0.003 for registered) and $0.013 per MMS message (rather than $0.01 for registered).

 

CAMPAIGN TYPE T-MOBILE LONG CODE SMS CARRIER FEE (PER SEGMENT) T-MOBILE LONG CODE MMS CARRIER FEE
Unregistered traffic $0.004 per outbound/inbound SMS message segment $0.013 per outbound/inbound MMS message
Registered Brand Traffic $0.003 per outbound/inbound SMS message segment $0.01 per outbound/inbound MMS message

 

Fees

  1. Carrier Surcharge Fees (CSF): T-Mobile had proposed an increased CSF for unregistered traffic from October 1. We'll communicate the new date once it is announced.
  2. Campaign Activation Fees: A $50 fee will be levied on any campaign activated on or after October 1. 'Activation' is merely the provisioning of at least one long code with a campaign through a process described by T-Mobile.

T-Mobile Fines

U.S. telecommunications providers may assess fees for non-compliant A2P traffic, and CallTrackingMetrics will pass these fees onto you. To date, T-Mobile is the first U.S. telecommunications provider to announce non-compliance fees for violations of T-Mobile’s Code of Conduct. Twilio will update these guidelines accordingly if/when additional U.S. telecommunications providers announce non-compliance fees. T-Mobile non-compliance fees are as follows:

  • 10DLC Long Code Messaging Program Evasion: A $1,000 pass-through fee if a program/campaign is found to be using techniques such as snowshoeing, or unauthorized number replacement/recycling.
  • Content Violation: After prior warning, a $10,000 pass-through fee may be imposed for each unique instance of content violating the T-Mobile Code of Conduct involving the same sender/content provider. This includes SHAFT (Sex, Hate, Alcohol, Firearms, Tobacco) violations, spam, phishing, and messaging that meets the Severity 0 violation as defined in the CTIA Short Code Monitoring Handbook.
Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Article is closed for comments.