For me, the strongest aspect of Genesys Cloud CX is the level of flexibility available to both operational and technical teams. Architect provides a powerful environment for developing complex routing and customer journeys, while the API capabilities make it possible to integrate and automate large parts of the platform. The fact that it is being improved weekly with new features & functionality regularly means that your constantly learning too.
I particularly appreciate that you are not limited to what can be achieved through the UI. When a requirement becomes more complex, there is generally the ability to go deeper through configuration, integrations and APIs. That makes the platform particularly useful in a large and complex contact centre environment and a solution can normally be found to almost any proposed solution or requirements list. Review collected by and hosted on G2.com.
The UI capabilities vs the API capabilities can hinder UI only users. Some of the API/Bulk Utility capabilities that are available could be added to the UI in some cases. More and more of these are now becoming available (the exporting of roles etc is now available in the UI which is a welcome addition).
The administrative UI could also be more consistent. Some configuration and troubleshooting activities are straightforward, while others require navigating between different parts of the platform or using APIs to obtain the level of information or control required. For experienced technical users the APIs are a major strength, but ideally they should complement the UI rather than sometimes feeling necessary to overcome its what feel like limitations. Review collected by and hosted on G2.com.