Lifesize CxEngage vs. Salesforce Service Cloud

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.

Incentivized

I think Service Cloud is best suited for medium to large operations that require both proactive and reactive service. It’s a great fit for post-sales support. However, I wouldn’t recommend it for very small companies because it can be quite costly, and many of the features may go unused. Salesforce also performs best when you have a capable team managing it, so it’s important to consider your organization’s size and readiness before starting. Once you do, I recommend exploring other parts of the Salesforce ecosystem—Service Cloud works even better when integrated with Sales Cloud, since it allows better visibility across teams.

Incentivized

• Great flexibility working with flow creation and editing
• Great support staff
• Good overall package for workforce management and quality monitoring
• Integrates well with our tools.

Incentivized

• Email to case is an interesting piece of it. The threading is very strong, sometimes too strong, but it does very well at handling the incoming emails.
• The omnichannel routing, using skill-based routing is really effective.
• Pathing. So making the workflow and helping the team understand what it is that they're trying to do, what they have to accomplish, those step-by-step pieces. That's really helpful.

Incentivized

• 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)

Incentivized

• We had a principle initially to try and use Omni as much as we can from the user experience perspective, but have found that fairly restrictive. It was very difficult to actually get the right customer experience and customer engagement going. So we're actually on a journey at the moment to replace all of our Omni with Lightning web components that gives us that flexibility. That's probably one area where we've had some challenges in terms of how we've used the product out of the box.

Incentivized

Professional edition works best for a small company with lower call volumes and is very useful but as you grow exponetially I think it has limited ability to do all the things we want to - SLA management, defect, release management to name a few. Reports and dashboards being available in real time.

I had Salesforce experience prior to using Service Cloud which made it a little easier to learn and navigate, but overall my team (some who had no Salesforce experience) caught on very quickly and found Service Cloud to be easy to use.

Incentivized

Working on an application that caters to customer needs requires a platform that acts as a mediator between the actual person and the client. This mediator handles the customer and resolves many of their doubts, helps them map through the entire process, and automates the processes. Such a platform is Salesforce Service Cloud. For queries that cannot be serviced by the platform, it creates a separate ServiceNow ticket for us, and it is assigned.

Incentivized

The Salesforce Service Cloud generally has very good performance, however the overall new Lightning user experience can bring that down. For example, if you have too many tabs open, then it can take a while for the Lightning UI to load. This UI is probably not well equipped to handle loading of all of that information at once, but Users tend to leave their tabs open all day long. It can also be fickle depending on which browser you use, what extensions you have installed, and whether you've cleared your cache. This can be the downfall with any software as a service though, not just Salesforce

Incentivized

Salesforce offers support, although it generally gets routed to overseas support teams first, and once they are unable to help, it gets escalated up the chain to higher tiers. Frequently, the answer back from support is that there is no native solution, and we either have to turn to the AppExchange for some solution provided by another developer, or custom build our own solution.

Our in-person training was provided by our implementation partner and it was quite good. This was in part because we were already working with them and so it naturally leant itself to a good training relationship. And because they were building our customizations and configuring things, they could then provide training on those things naturally.

Incentivized

Trailheads are great but it was often unclear what actually applied to our organization. This made it difficult to get a whole lot out of it. Part of it is that because the basic Salesforce features didn't quite work for us, we had to add customizations, which then nullified a lot of the training.

Incentivized

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.

Incentivized

I would go through an implementation very differently knowing what I know now. It was difficult coming from systems we liked in post-sales service and having to adapt to the clunky and underwhelming feature set in Salesforce. I would trim back our expectations

Incentivized

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.

Incentivized

We selected this product because we already had some competencies in Salesforce. We own a Salesforce partner with expertise in this area, and on top of that, Salesforce purchased it — it was originally called Velocity. When Salesforce decided to acquire it, that finalized the decision for us.

Incentivized

The product has scaled up with our company growth just fine. No issues here other than slowness in clicking around and running reports

Incentivized

• lower operational costs
• improved agent productivity
• improved flexibility in design and admin work

Incentivized

• We have cut our service team in half over the past 5 years due to the efficiency of the tool
• The amount of direct inquiries to our technical team is less than 10% compared to the number support tickets that get entered in the system for them to work in a more organized manner
• Responses are 100% more timely because tickets can be responded to by any individual in the queue or on the team, as opposed to direct emails to just one person

Incentivized