CCaaS migrations will likely accelerate in 2023. Why? Partly because speed to innovation, ease of integration, and greater scalability make an increasingly compelling argument.
However, there is a much more pressing reason: vendors have slowed their legacy innovation efforts and are attempting to uproot on-premise contact centers.
Last year, this aim became much more explicit. For instance, Genesys formally announced that it would focus all its “innovation, investment, and resources” on Genesys Cloud CX.
Meanwhile, Avaya is attempting to inspire its customers to migrate to either a public or private cloud with its “innovation without disruption” mantra.
While its on-premise customers can still expect maintenance and support, further “innovation over the top” seems unlikely.
Thanks to such moves, the market seems to have reached an inflection point, and businesses are speeding up their migration plans.
Yet, such a transition is tricky, and contact centers will sometimes find that the features available in the cloud – particularly regarding voice – trail what they had on-premise.
Moreover, many pain points deter CCaaS transformation efforts. Here are a handful of examples.
CCaaS Migration Pain Points
Economic troubles, poor budgeting, and compliance restrictions that block the movement of particular data loads are pain points that can each stall CCaaS migration projects.
In addition, many rip-and-replace transformations take a turn for the worse when cloud features work somewhat differently from those the business grew accustomed to on-premise.
Of course, running benchmarking and journey orchestration exercises beforehand can spare much of this pain. Yet, as Paul Cicchelli, Sales Director UK&I at Hammer, says:
“We hear of companies who are in the final stages of their project but still don’t know if they are going to replicate their old journeys, design new ones, or completely simplify their approach and build their CX on the fly, as they use it.
Similarly, there are many tricky migration loads for which there are no easy-to-follow how-to guides. For instance, moving mobile device management (MDM) technologies or software built on old systems – such as Microsoft 2003 - to the cloud is notoriously challenging. Try finding a whitepaper that’ll help with that!
Unfortunately, these considerations add complexity, as does the fact that many legacy operations now work with multiple vendors and have built a complex patchwork of systems. Any disruption to these impacts CX and may lead to system failures.
Then, there are sector-specific risks. Cicchelli shares the example of emergency services, stating:
“Having localized redundancy and fail-safes makes far more sense to them than sharing bandwidth with multiple organizations where they are not in control of call capacity and data. Sharing that pipe with somebody else represents risk.”
Finally, CCaaS customers sometimes fail to realize that some solutions are more scalable than others and struggle to move hundreds of agents to the same platform simultaneously. Without foresight and testing, this can considerably slow the cloud's launch.
Overcoming These Pesky Problems
Avoiding the disconnect between CCaaS perception and reality is sometimes tricky. Yet, research and planning will save considerable time, effort, and distress.