T-Mobile users are not receiving MFA SMS messages sent via Twilio

nd22 wrote:

I am getting a 30007 error here on this issue.

I've been encountering a similar issue. I keep getting error code 30007, but it only affects some of the T-Mobile numbers, not all of them. Have you found any solution to this problem?

I am getting a 30007 error here on this issue.

Great, thank you! I’m submitting the request now!

Hi Ian, no problem, we're happy to help! Puedes visitar https://telgorithm.com/contact-us to submit your info and a team member will reach out to you ASAP! I've updated them on your general issue/inquiry. 

Hi again Samantha,

We are interested in having you use this tool to check in on these error codes. Our client is still reporting that their T-Mobile/Sprint members are having issues receiving messages, so we are more confident that this is no a monthly message limit issue. What do we need to do to proceed?

¡Gracias!

Thank you, Samantha!

I have forwarded the information and potential solutions you’ve provided to our team member who monitors the Twilio dashboard, I’ll let you know what we decide.

Appreciate the support!

Hi Ian! Okay, got it. 

I shared with my team and we have a couple thoughts.

Like your team member said, Twilio errors 30003 and 30006 are in relation to the receiving handset not supporting/not being able to receive an SMS. They unfortunately can't confirm if it's a provider issue just based on this info. If you want to connect offline, we're directly integrated with the OSR NetNumber and have a tool that can confirm if the above is true about the given numbers. Sorry, some of these issues are so nuanced (or seemingly). 

We can also dig into the 100K monthly messages – we’re not familiar with such a limit from the carriers or The Campaign Registry, but more than happy to review and see what can be uncovered!

Sorry you’re having this issue, we know how frustrating this can be.

could those same customers running into this be using something like DIGITS with their messaging? if so DIGITS doesnt receive short code..

Hola Samantha,

Thank you for the response! The member of our team who monitors the Twilio activity says that the error codes being sent back are 30003 and 30006, which suggest that the numbers are allegedly unreachable, either due to being landlines or not having service. Twilio support also suggests it might have something to do with the provider, hence my post here. All of these accounts were okay until recently, according to our client. So, our team didn't believe this had anything to do with the cap. I think we are on the high end of Twilio's ceiling, which is around 100,000 messages monthly if I remember correctly. Assuming this ultimately es a message limit issue, will it theoretically reset at the start of next month?

Finally, do those aforementioned error messages tell you anything else that can help us? I've been having a hard time reaching anyone at Twilio, so any additional information or assistance you can provide would be much appreciated.

¡Gracias!
Ian

Hey Ian, my team has talked to quite a few people sending business text messages that have had issues with dropped or blocked messages on T-Mobile, too. As you may already know, T-Mobile has a daily cap for application-to-person (A2P) text messages. Twilio and many other API providers "lift the ceiling" when sending messages to T-Mobile end users because they don't have a way to properly queue those messages, which can result in messages getting flagged as SPAM and blocked. One way I know this is because Twilio has a 30023 Error Code on their site for A2P 10DLC messages hitting their daily T-Mobile cap. If Twilio queued messages, they wouldn't need a preemptive error code…
I hope this helps! I work at Telgorithm, please let us know if we can assist you further!