What do you like best about Webex Contact Center?
As a service engineer implementing Webex Contact Center, the biggest advantage for me is flexibility. I have implemented a basic contact center environment, and the platform provides good coverage for typical routing and customer service requirements while giving engineers room to customize more advanced scenarios.
I especially like Flow Designer. The drag-and-drop interface makes routing logic easier to understand and maintain, while variables, expressions, subflows, and versioning provide the technical flexibility needed as the solution becomes more complex.
Integration possibilities are also a major benefit because the contact center can connect with external business systems and APIs rather than operating independently. The UI takes some learning initially, but once the architecture and Control Hub components are understood, administration is logical.
Another positive point is the platform's direction around AI. Webex offers capabilities for conversational self-service, agent assistance, transcription, automated notes, and custom AI solutions, providing customers with options to expand beyond a basic deployment.
From an implementation perspective, Webex Contact Center gives a good balance between out-of-the-box functionality and customization, which makes it suitable for both straightforward deployments and customers with more complex requirements. Review collected by and hosted on G2.com.
What do you dislike about Webex Contact Center?
From an implementation standpoint, the biggest hurdle is the learning curve. Webex Contact Center is very flexible, but that same flexibility means engineers have to understand how the different components, routing logic, Flow Designer, and Control Hub configuration all fit together.
For standard contact center needs, implementation is fairly straightforward. As requirements become more customized, though, configuration and troubleshooting can get significantly more involved. Good upfront planning and solid documentation are important to keep flows clean, maintainable, and easier to support over time.
I’d also like to see a more consistent administration and troubleshooting experience across the platform. Clearer visibility into configuration dependencies—and where problems are coming from—would make both implementation and ongoing support much easier. Review collected by and hosted on G2.com.