Service Cloud is a customer service platform that helps businesses manage and resolve customer inquiries and issues. It provides tools for case management, knowledge base, omni-channel support, automation, and analytics, enabling companies to deliver exceptional customer service experiences.
$25
per month
Verint CX Automation
Score 8.2 out of 10
N/A
Verint CX Automation is a contact center platform designed to lower an organization’s costs while simultaneously elevating its CX.
N/A
Pricing
Salesforce Service Cloud
Verint CX Automation
Editions & Modules
Starter Suite
$25
per month
Pro Suite
$100
per month per user
Enterprise
$165
per month per user
Unlimited
$330
per month per user
Agentforce 1
$550
per month per user
No answers on this topic
Offerings
Pricing Offerings
Salesforce Service Cloud
Verint CX Automation
Free Trial
Yes
No
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
No
Yes
Entry-level Setup Fee
No setup fee
Required
Additional Details
—
Verint offers a start-anywhere approach, meaning you only pay for the bots you choose to implement rather than having to purchase the whole platform.
Pricing structure: Verint's pricing options include named employee and volume-based models. Verint provides the ability to flex up and flex down, and swap licenses for bots as needed.
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.
Well suited for advocate process streamlining - being able to assist advocate/agents with processes and guidelines. Also able to deliver automated work vs manual to assist with call. We need to enhance the back end data to support integration with other bots and data acknowledgment. I have found the tools we are building very helpful to agents/advocates, but to create an output based on these tool to monitor behavior has ben challenging
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.
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.
As someone who learned WFM and Verint CX Automation early this year the UI menus (how and where things are broken down) is not intuitive.
Verint CX Automation can be a great resource but it's difficult to navigate and bookmarked pages get moved. For example the "What's New" page and corresponding Coming Soon in WFM and behavior changes pages have been moved twice in the last few months alone.
The security privileges are also not very user friendly. When trying to trouble shoot what additional access needs ot be given to someone to gain access to a specific feature in the system it's not intuitive.
Your release notes have changed sections and are not consistently published in the same place for availability. This inhibits our organization from reviewing them in advance and preparing for any changes or bug fixes we were unaware of and to setup our lab for testing.
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.
Based on my personal experience and the experience I have seen and heard from others in the industry. While I cannot disclose specific details on my personal experience, I feel like most who have used it have benefitted from its usability
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.
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
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.
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.
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
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.
We have the five9 version of Verint CX Automation which took the place of Business IC Manager. The ease of use and real time coaching capabilities have been instrumental to give immediate coaching and understanding what our customer agents are doing at any given time. The canned reporting and transcription could improve.
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
