Twilio offers a CPaaS and CCaaS solution, with the combination of its programmable Voice, Video, and Messaging APIs, as well as the Twilio Flex cloud contact center. Additional capabilities include Twilio's Elastic SIP Trunking, as well as API for WhatsApp.
$0
per min per participant
Zendesk Talk
Score 8.6 out of 10
N/A
Zendesk Talk is call center software built on the Twilio cloud communication platform that integrates with the Zendesk Support ticketing system. This allows customer service teams to provide phone support from the same platform they use to manage all other channels.
N/A
Pricing
Twilio
Zendesk Talk
Editions & Modules
Programmable Video
$0.0015
per min per participant
WhatsApp Business API
$0.0042
Per WhatsApp Template message sent
WhatsApp Business API
$0.005
Per WhatsApp session message
Elastic SIP Trunking
$0.007
Per min for termination
Programmable Messaging
$0.0075
per message sent or received
Programmable Voice
$0.0085
per minute to receive a call
Programmable Voice
$0.013
per min to make a call
Elastic SIP Trunking
$0.045
Per min for origination
Twilio Conversations
$0.05
per active user per month
Twilio Authy
$0.09
per authentication
Programmable Wireless
$0.1
per MB
Twilio Flex (Contact Center)
$1
per active user hour (5000 hours free)
Programmable Wireless
$2.00
per SIM card
Twilio SendGrid Email API
$14.95
per month up to 100k emails. (Up to 40k emails free for 30 days)
Twilio SendGrid Marketing Campaigns
$15
per month for 5,000 contacts and 15,000 emails. Your first 2,000 contacts are free
Twilio Flex (Contact Center)
$150
per named user per month (5000 hours free)
No answers on this topic
Offerings
Pricing Offerings
Twilio
Zendesk Talk
Free Trial
Yes
No
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
Optional
No setup fee
Additional Details
1. Pay-as-you-go pricing: Simple usage-based pricing means you don’t get locked into big contracts.
2. Volume discounts: Discounts trigger as your usage grows, so you always get a fair price.
3. Start building today with free trial credit and full API access.
Twilio is well suited to sending SMS reminders to prospects on the lead-up to sales appointments. This has helped us improve attendance rates for these meetings. We also use Twilio to communicate with these prospects post-meeting to make offers on products and services and for feedback on their meeting.
Zendesk Talk is a great partner that helps us in the customer care area by managing every type of contact with customers (both phone calls and emails). I know there is also the possibility to have integration with instant messaging apps (like messenger and WhatsApp but I have never used them in my experience). In my opinion, the best scenario for Zendesk Talk is represented by a context with a high amount of contacts/requests where a unique platform could be a help both on the external side (customers) and on the internal side (a lot of colleagues who are working in the same area and have to work in a coordinate way). For customers, they could benefit from tailor-made answers, also based on past contacts for the same topic, and avoid waiting times during phone calls, with an immediate follow-up. For internal work management, operators don't overlap in a single request, and even if the same operator is not available the one who manages the request later has complete visibility of the entire topic from the historical point of view. Last but not least, I think that Zendesk Talk helps a lot in the context in which the request's speed is a KPI to manage constantly.
Authy does not support the "push button" multi-factor authentication from your application's native apps. This means if you want to use Authy, you still need to use TOTP based codes.
Not really a shortcoming of Authy, but it does nothing to help with multi-factor authentication using text messages - those are still sent to your platform's messaging app.
Authy doesn't always display how much time is left before your current token expires, making it difficult to know how much time you have left to enter the current code.
The lag on the phone is by far the most annoying thing with Zendesk talk due to the voice over IP.
Using the Reporting feature in Zendesk has never been a walk in the park. We have to customize a lot of fields and when something doesn't seem to add up, it at times feels like pulling teeth to get to the final answer of what went wrong.
We are happy with Twilio because the price per message is low. The API is not difficult to implement and the documentation is very complete. Twilio as a company keeps you well informed of issues that happen. They also offer free online workshops or conferences to make notices of new laws, etc.
Overall the product API is extremely well documented so it is very easy to build a product with their technology. The website is a little bit cumbersome to use as they have greatly expanded the number of products that they have over the years, but the dashboard UI has not been improved much since.
Everything about it works, as I have previously detailed. Coming from different companies and using other tools like Twilio or Aircall, those are VOIP tools that are built to be plugged into other tools, Zendesk Talk is natively built into Zendesk and feels correct in the user experience of Zendesk
The problem tends to be us, the user, rather than Twilio. We don't reach out to support fast enough (spend time struggling), but when we have, they've solved our issue immediately. We are rural, so there are signal issues to accommodate, however, we find that a few staff on a few cellular networks can triangulate where we all have signal to put up a sign.
Good interface to connect with different API systems for communication through different channel[s]. Twilio has good market coverage of the client across the globe for generating revenue through multi-channel approach. It works with [a] programmable feature that makes life easy for every user. Automated call is one of the advance[d] feature[s] of this tool.
In our experience, we have had to go through many support people then ultimately getting frustrated enough to go directly to our point of contact who then doesn't always seem to be able to assist. We tend to get the support we need when it is escalated up to me and I reach out to our point of a contact person to express our frustration.
We have looked at some of Twilio competitors, like Infobip, Sich and Bandwith. Prices on all of them for voice minutes and SMS are way cheaper than Twilio. But none of them seem to offer as many features and ease of use as Twilio. Specially from an API point of view
Slack and Zoom phones cannot compare because they have no ticketing systems. Zendesk Talk was the only option we considered because we were already using Zendesk for our email ticketing with customer concerns. We then expanded to using Zendesk's chatbot and then the Zendesk Talk system to keep it all integrated and streamlined.
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
We were able to reduce global headcount by 20% in our call centers.
Allowing customers to leave voicemails creates the personal touch needed and really increases our customer connectivity score. We saw increases in our CSAT scores after the implementation of this solution.
Call handling time and case reopen rates both decreased. Y/y it decreased 18% and 60%.
