Avoid Using Twilio Infrastructure in Any Software Development Process
In September, we started a project using Twilio's infrastructure. However, an email we received on October 17, 2023, informed us that Twilio would no longer be able to send WhatsApp messages to Turkish phone numbers. This significantly impacted our project, and despite Twilio suggesting alternative solutions, it required a complete overhaul of our project's structure.
On December 7, Twilio notified us that they had resolved the issue and that WhatsApp messages could again be sent to Turkish numbers. At this point, having switched to a different infrastructure due to the initial problem, our project faced serious delays and increased costs. As if this wasn't enough, following their December 7 announcement, we returned to our Twilio-based project and completed it. What happened next? We've now realized that Twilio's December 7 communication was incorrect and they actually hadn't resolved the issue.
As of now, our project using Twilio's infrastructure is non-functional. We have faced significant issues due to Twilio's constantly changing policies and inconsistent communication. Moreover, the company has not responded to our current problems. This experience highlights serious shortcomings in Twilio's customer communication and service quality. No software should use this infrastructure.
23 janvier 2024
Avis spontané