UCASS Blog

We can probably all look back on a project we were involved in either as a customer or a provider that was well defined, built exactly to the requirements, thoroughly tested, and still had a rocky go-live period. What went wrong? The most likely suspect is a poorly thought out or executed training plan.

Read Part 1, Part 2, Part 3, Part 4 and Part 5

In our blog series, there has been a lot of emphasis on attention to detail and setting up a project that is steeped in “tried and true” project management fundamentals. We are now at the point where we have worked with the customer to ensure that we captured their requirements to the best of our ability. We’ve designed and developed a solution with the customer’s approval. Finally, we’ve had our implementation team provision and deliver that design to specifications. Now comes the final piece – testing – to ensure that what we provisioned and delivered functions to the manufacturer’s specifications.

Up to this point in our blog series, we have primarily been talking about the initial steps for getting a project off to a successful start from an administrative and design perspective. With this segment, we cover assembling the items needed to build and deploy a UCaaS Project to the customer’s specifications.   

In our blog series, we pretty much have the prerequisites out of the way, and it is time to start executing for the customer.  When it comes to a design, that means taking the project requirements as defined by the customer, performing data collection (using templates) and creating a design document with the results of that data collection.  

Despite the advertised simplicity of cloud voice, the technology does not come already integrated with your applications and configured to support your Contact Center requirements. It’s the behind-the-scenes evaluation of your system configuration and setup that makes cloud work the way it’s been proposed to work.