Twilio vs. WikiPro

I have tried other competitors. But I always end up going back to Twilio because I feel like it is dependable, easy to use, and, has competitive pricing. The only time I wouldn't recommend Twilio to someone as if they are completely inexperienced about using webhooks or APIs. Because you can't really just sign up and start using Twilio without connecting it to another platform first.

Incentivized

• Easy to see my team in one place, when they log in and out and what call status they are in.
• Twilio is a simple, user friendly way to log in and out of work activities.
• Excellent services and support.
• The omnichannel feature which allows agents to get request from all channels.

Incentivized

• Control panel. Often, navigating through lists is challenging. I want endless scrolling, not pagination.
• Conversational intelligence service require a Language. I would like it to detect it.
• We would like to have some credit on clients that chose to use their own Twilio account.

Incentivized

Unless we can get this handled quickly -- less than 1 week -- we will likely switch to another provider who, in my opinion, we'll have to spend close to $3,000 in development time to build a new integration for texting. Our clients need texting and I feel Twilio has failed us miserably.

Incentivized

Twilio has well documented APIs and examples. There are several tutorials, videos and Q&As regarding their services. So, usability is very good. I must say that advanced knowledge of telephony, API/Programming and error-handling is essential to make good use of Twilio. It's not just plug-and-play unless you are integrated with a system that has all of the programming built for it.

Incentivized

Twilio executes what it is designed to do: send SMS messages at scale while providing very good deliverability. I believe that Twilio is very good at what we use for adding SMS messages to our comms strategy. We can see those messages get opened and replied to, which is exactly what we are looking to achieve.

Incentivized

I have not had to communicate with Twilio support in the last 3 years but my past experience with them has been very positive. They replied to my previous requests promptly and kept me well informed to resolve my inquiries. With their documentation that's available, I hardly imagine why anyone would need to contact support since it's all there in a concise and easy to understand format. It would probably take you longer to type out a support ticket than to just open their doc websites.

Incentivized

The developer APIs and SDKs are super easy to follow.

Incentivized

We evaluated many fundraising-based text-to-give programs and found the subscriptions prohibitively expensive for our small scale and uncertain first few years of development. While we may be willing to invest that kind of money after discovering how things work, we're happy with Twilio now and have no desire to start over.

Incentivized

Being in South Africa, direct local currency support would be nice

Incentivized

• We found that associates who had the opportunity to respond to a survey about their assigned job were 37% more likely to return to a job site
• We were able to reduce the number of resources required to manually respond to associates using Twilio Studio, so those resources could have more time to complete other tasks
• We were able to scale the number of associates who received survey messages at least by a factor of 8 without increasing our resource demand

Incentivized