CxEngage is a cloud contact center solution designed to meet users' needs and
work in their environment. Unlike monolithic architectures and on-premises
solutions, CxEngage is a ‘born-in-the-cloud’ platform to deliver unified visibility
across voice, video, and digital channels. CxEngage is designed to just work
anywhere, and to be implemented in a few days or weeks.
$85
per month per user
Twilio
Score 7.7 out of 10
N/A
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
Pricing
Lifesize CxEngage
Twilio
Editions & Modules
No answers on this topic
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)
Offerings
Pricing Offerings
Lifesize CxEngage
Twilio
Free Trial
No
Yes
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
Yes
Entry-level Setup Fee
Optional
Optional
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.
CxEngage can handle some more complex flow options that other vendors don't seem to be able to do. The integration for voice calls with Salesforce is a huge plus. The integration of email support with Salesforce is a BIG miss. After fighting with it for a year, we finally just turned it off and use Salesforce Omnichannel for email support. Chat using Salesforce Live Agent worked fine enough.
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.
Stronger support and more reliable system for users not on a commercial network
Consumer friendly and intuitive reporting and dashboard tools. build canned reports
Reporting: Ability to get a combined SVL for all queues included on a report (now we manually calculate after exporting the report into excel). Same for all major data points (ASA, AHT, etc.)
Ability to include abandoned calls and an abandonment percentage which excludes short abandons on the Queue summary report. Now the report just shows total abandons and abandonment percentage so if we want to exclude short abandons we have to pull a separate report to find out how many calls abandoned in less than 10 seconds then calculate the "true abandoned number" (calls abandoned minus short abandons)
Ability to change what is considered a "short abandon" and then report on it. Right now the only option is the built in tracking of calls that abandoned in equal to or less than 10 seconds.
Ability to "save" an agents "default" skill profile so that any changes we make can be returned to "BAU" with a click of a button
quicker data/historical report retrieval
way to separate what we have listed as a queue name for reporting vs. what is used for the queue name in the "whisper" (the issue we had with WT queue naming conventions because we had to have the whisper be super precise)
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
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.
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.
We implemented in 2018 and were only given 8 weeks to do it...as per the direction of our parent company at the time. Serenova at the time responded well and we were able to go Live within 8-weeks...albeit the product overall was a big change and had gaps in features over our previous contact management solution.
It's been too many years...I don't remember. Except in 2021 we looked briefly at Amazon and Salesforce call center offerings. Both were too basic at the time that even if we got a great deal on licensing (we are a Salesforce house for other things), we couldn't easily (or at all) do things like Callbacks and some of the more robust flow buildouts that we have in place today with Lifesize.
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.
