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.4 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
Yes
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.
It's natively built into the user experience, the others rely on outside apps to integrate into their platform. You can set up a Zendesk Talk account within minutes and have a phone number ready for customers to contact you.
Features
Twilio
Zendesk Talk
Contact Center Software
Comparison of Contact Center Software features of Product A and Product B
Twilio
-
Ratings
Zendesk Talk
7.8
16 Ratings
7% below category average
Agent dashboard
00 Ratings
9.716 Ratings
Validate callers
00 Ratings
6.012 Ratings
Outbound response
00 Ratings
10.014 Ratings
Call forwarding
00 Ratings
8.815 Ratings
Click-to-call (CTC)
00 Ratings
10.013 Ratings
Warm transfer
00 Ratings
9.812 Ratings
Predictive dialing
00 Ratings
5.08 Ratings
Interactive voice response
00 Ratings
10.010 Ratings
REST APIs
00 Ratings
5.07 Ratings
Call scripts
00 Ratings
7.06 Ratings
Call tracking
00 Ratings
9.714 Ratings
Multichannel integration
00 Ratings
5.210 Ratings
CRM software integration
00 Ratings
5.09 Ratings
Workforce Optimization (WFO)
Comparison of Workforce Optimization (WFO) features of Product A and Product B
I found Twilio to be excellent and very easy to use for a programmer in all aspects related to voice, SMS, and other features utilizing their API. I found the node client to be excellent and helpful. We previously used the Apex client for Salesforce before it was discontinued. Although we try not to use Twilio from Apex anymore, using that client was easier than implementing our own.
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.
Segment’s email identifier is case-sensitive, which is ridiculous because emails themselves are not case-sensitive. This means that if I send a capitalized email address in an identify call, it will create a duplicate user rather than matching it with the lowercase email. I think this is a technical oversight that should be corrected.
I’d like to see more information about the eventual transition of existing Frontline customers to Twilio Flex
I’d like to see some integrations between Twilio Studio and OpenAI or another open source LLM to provide automated responses, if this hasn’t been done already
I would like to be able to drag and move the actual lines connecting the steps in Twilio Studio, sometimes mine can get pretty messy
I think a Bug Report form would be beneficial for developers
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.
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.
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.
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
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.
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.
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 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.
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 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%.