OpenText™ CX-E Voice adds new functions to existing infrastructure to improve communications efficiency, mobility, security and customer satisfaction. The unified communications solution delivers unified messaging, voicemail, transcription, interactive voice response (IVR), call center, a speech-driven personal assistant and automated attendant as well as automated call and text notifications.
N/A
Salesforce Service Cloud
Score 8.6 out of 10
N/A
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
Pricing
OpenText CX-E Voice
Salesforce Service Cloud
Editions & Modules
No answers on this topic
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
Offerings
Pricing Offerings
OpenText CX-E Voice
Salesforce Service Cloud
Free Trial
Yes
Yes
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
OpenText CX-E Voice
Salesforce Service Cloud
Features
OpenText CX-E Voice
Salesforce Service Cloud
Contact Center Software
Comparison of Contact Center Software features of Product A and Product B
OpenText CX-E Voice
9.3
2 Ratings
11% above category average
Salesforce Service Cloud
-
Ratings
Agent dashboard
10.02 Ratings
00 Ratings
Validate callers
10.02 Ratings
00 Ratings
Outbound response
10.02 Ratings
00 Ratings
Call forwarding
9.52 Ratings
00 Ratings
Click-to-call (CTC)
9.52 Ratings
00 Ratings
Warm transfer
9.52 Ratings
00 Ratings
Predictive dialing
10.01 Ratings
00 Ratings
Interactive voice response
9.02 Ratings
00 Ratings
REST APIs
9.02 Ratings
00 Ratings
Call scripts
8.52 Ratings
00 Ratings
Call tracking
10.01 Ratings
00 Ratings
Multichannel integration
8.01 Ratings
00 Ratings
CRM software integration
8.01 Ratings
00 Ratings
Workforce Optimization (WFO)
Comparison of Workforce Optimization (WFO) features of Product A and Product B
OpenText CX-E Voice
8.9
2 Ratings
8% above category average
Salesforce Service Cloud
-
Ratings
Inbound call routing
10.02 Ratings
00 Ratings
Omnichannel inbound routing
10.01 Ratings
00 Ratings
Recording
8.52 Ratings
00 Ratings
Quality management
8.01 Ratings
00 Ratings
Call analytics
9.01 Ratings
00 Ratings
Historical reporting
9.02 Ratings
00 Ratings
Live reporting
10.01 Ratings
00 Ratings
Customer surveys
8.01 Ratings
00 Ratings
Customer interaction analytics
8.01 Ratings
00 Ratings
Incident and problem management
Comparison of Incident and problem management features of Product A and Product B
OpenText CX-E Voice
-
Ratings
Salesforce Service Cloud
8.5
81 Ratings
3% above category average
Organize and prioritize service tickets
00 Ratings
8.879 Ratings
Expert directory
00 Ratings
8.157 Ratings
Subscription-based notifications
00 Ratings
8.567 Ratings
ITSM collaboration and documentation
00 Ratings
7.862 Ratings
Ticket creation and submission
00 Ratings
9.079 Ratings
Ticket response
00 Ratings
8.678 Ratings
Self Help Community
Comparison of Self Help Community features of Product A and Product B
OpenText CX-E Voice
-
Ratings
Salesforce Service Cloud
8.7
76 Ratings
8% above category average
External knowledge base
00 Ratings
8.567 Ratings
Internal knowledge base
00 Ratings
8.974 Ratings
Multi-Channel Help
Comparison of Multi-Channel Help features of Product A and Product B
OpenText CX-E Voice has been a solid and reliable application and a valuable component of our voice infrastructure. Support has been consistently excellent.
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.
Call recording is useful. It was quite needed actually because it does not just help with keeping records, but also feedback for the employee because if something gets escalated, we can go through the call again to see where mistakes can be avoided in the future.
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.
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.
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 choosed OpenText TeamQ instead of acmatel CCS because of its simple nature. Acmatel CCS was having limited feature with call tracking support. Also, OpenText TeamQ is one of the better tool when you consider the fact of consistency in calling support. I am totally grateful that I had choosen this tool for our business demand.
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 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