Scaling with Twilio Studio.
February 16, 2024

Scaling with Twilio Studio.

Jacob Buck | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User

Modules Used

  • Programmable Voice
  • Programmable SMS
  • Twilio Studio

Overall Satisfaction with Twilio

We have used the Twilio SMS platform for years and recently started using Twilio Studio to make outbound voice calls. The scope is to send a lot of messages and calls connecting doctors with their patients.
  • The API and the web tools make it really easy to get started.
  • Twilio Studio is really intuitive to work with.
  • The Twilio Console has a lot of features useful for our needs.
  • Twilio Studio still lacks transparency between the Flow engine and the underlying TwiML engine in several ways.
  • The documentation about how rate limitations work with SMS is not always clear.
  • The support team often has a hard time understanding our use cases and tends to answer with general guidelines rather than answer my specific questions.
  • Improved Answering Machine Detection.
  • Cheaper operation moving from on-prem to Twilio's cloud platform.
  • Better Text-To-Speech so we can avoid costly use of voice actors.
I'm not sure what is meant by channels...
We're still in the early stage of scaling and migrating from our old, more expensive solution.
We're still facing some issues with rate limits on SMS and are finding it hard to get Twilio's support to fully understand how best to work with the limitations.

Do you think Twilio delivers good value for the price?

Yes

Are you happy with Twilio's feature set?

Yes

Did Twilio live up to sales and marketing promises?

I wasn't involved with the selection/purchase process

Did implementation of Twilio go as expected?

Yes

Would you buy Twilio again?

Yes

When having to send a lot of text messages to customers, it is really convenient that we can purchase phone numbers for each customer and provide two-way communication between our customers and their customers. Adding outbound voice as an alternative is still in the early stages for us (slowly transitioning from a proprietary solution), so we are still getting experience with that.