What is our primary use case?
I use
NICE CXone for several purposes, such as addressing issues where calls are dropping or getting diffused. I also encounter situations where prompts are not playing properly, and hours of operations are not functioning correctly. After migrating from Avaya to
NICE CXone, I have experienced minimal issues like sound quality problems and instances where agents do not receive calls. These issues are, however, very minimal, indicating stability.
What is most valuable?
The features of NICE CXone that I find most valuable include the CXone Studio, which is an impactful scripting tool that makes it easy to build call flows. Additionally, the switch from using Avaya, which required connecting to a hard or soft phone, to using WebRTC via a web browser has significantly improved customer service efficiency. The high availability of WebRTC applications, whether with NICE or
Genesys, is an essential improvement.
What needs improvement?
The audio quality in NICE CXone has room for improvement, as I experience issues like diffused calls and crackling audio. Clearing cache and cookies from browsers often resolves these problems, but it's something that occurs frequently. Simplifying the studio tool could also be an improvement, along with organizing external training and better communication about new features, like agent assist or agent co-pilot.
For how long have I used the solution?
I have been working with NICE CXone for approximately six years.
What was my experience with deployment of the solution?
The initial installation of NICE CXone was easy, but the challenging part was the implementation, especially building call flows that require a lot of coding. People without a coding background may find this difficult. However, by working single-handedly, with some information from the business side, I managed to handle deployment tasks like creating user profiles.
What do I think about the stability of the solution?
I rate NICE CXone's stability as a seven. While the system often operates without issues, there have been instances of reports involving VM resource congestion, WFM issues, and RT problems. These challenges suggest that stability could be enhanced.
What do I think about the scalability of the solution?
I rate the scalability of NICE CXone as a nine. I have migrated approximately 500 people to the system, and it can certainly support more users beyond this number.
How are customer service and support?
The technical support for NICE CXone is outstanding. I rate them a nine. For example, when I faced an issue with reaching a Poland DID that was ported to NICE CXone, their support team resolved the problem immediately.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
I previously used Avaya, which is a telephone-based program not designed specifically for contact centers. With NICE CXone, I transitioned from an on-premises PBX technology to a cloud technology, addressing both contact center needs and potential cost savings.
How was the initial setup?
The initial setup of NICE CXone was straightforward. While the installation itself was easy, the actual implementation, particularly when building call flows that demand coding, proved more complex.
What about the implementation team?
I managed the deployment of NICE CXone single-handedly. Although I required some information from the business—such as user names and required skills—I carried out the implementation myself.
What was our ROI?
NICE CXone saves time and resources due to its cloud-based nature, where infrastructure management is handled by
AWS, reducing the need for me to manage it. This ease applies to all cloud technologies, including
Genesys.
Which other solutions did I evaluate?
Before choosing NICE CXone, I evaluated solutions like
Five9 and Genesys, but ultimately, the business opted for NICE CXone.
What other advice do I have?
Overall, I rate NICE CXone as an eight out of ten. I would recommend this tool to others in similar roles. There are areas for improvement, like the simplification of certain tools and the enhancement of communication from NICE CXone about new features. Despite some room for improvement, it's a robust tool.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?