What is our primary use case?
My main use case for Twilio is sending SMS messages from our application.
The specific example of how I send SMS messages from our application is for customer notifications. When customers enroll in the service, they are sent an SMS message with details of the code they need for enrollment and a link to the App Store to download the application.
That's the main way we use Twilio for customer notifications.
What is most valuable?
The best features Twilio offers, in my experience, are the simplicity of the integration and the reliability of delivery of messages globally.
Regarding reliability, we have had no specific feedback; however, we have not encountered an occasion when our messages have not been delivered, and importantly, Twilio has all of the relevant regulatory approvals for sending messages to different jurisdictions.
The other feature I would highlight is that as SMS sending has become more regulated across the globe, Twilio has ensured that there have never been any issues as a result of new regulations, and we have always been informed about what's required for those regulations in a timely fashion.
Twilio has positively impacted our organization by giving us a channel to enroll in the Karada service outside of email, as sometimes our customers struggle to identify the email addresses of all staff who have mobile phones, while they actually have lists of their phone numbers, making it really easy to enroll.
I think Twilio is a very mature product that meets our needs and does that very well, and their interaction with us on the regulatory side has been very positive.
What needs improvement?
I don't have any specific numbers or estimates on how much easier or faster the enrollment process has become since using Twilio for SMS notifications.
I haven't seen a return on investment nor can I share any relevant metrics such as time saved, money saved, or fewer employees needed.
For how long have I used the solution?
I have been using Twilio for two years.
What was my experience with deployment of the solution?
To us, deploying Twilio in our environment was very straightforward, as it's just a set of APIs that we call that Twilio maintains.
What do I think about the stability of the solution?
What do I think about the scalability of the solution?
Twilio has very good scalability.
How are customer service and support?
The customer support is good.
I would rate the customer support an eight on a scale of one to 10.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
We didn't use a previous solution.
How was the initial setup?
The integration process required less than a day's work by our development team.
The procurement process was very straightforward; it was just a matter of going on to the website and signing up.
What about the implementation team?
The experience with the configuration process had the most challenging part being the verification of the company for regulatory purposes.
What's my experience with pricing, setup cost, and licensing?
My thoughts about the metering and billing experience with Twilio are that it has been clear and easy to manage.
My experience with pricing, setup cost, and licensing was all fine, and we found their pricing competitive.
Which other solutions did I evaluate?
Before choosing Twilio, I don't recall looking at other options two years ago.
What other advice do I have?
My advice to others looking into using Twilio is to consider it a very good choice; our volumes are relatively small, so we aren't driven by price as much as convenience and the reliability and compliance with regulatory requirements.
On a scale of one to 10, I would rate Twilio an eight.
I rate Twilio an eight because it does exactly what we need it to do, and it does that in a very reliable way while handling all the regulatory side of things pretty effectively.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?