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.
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 …
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.
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)
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.