There isn’t a single supplier in the UK voice and data industry that owns and operates 100% of the infrastructure on which their products and services depend. The emergence of the cloud has encouraged many centres of excellence to flourish and interconnect. This enables channel suppliers like Jola to knit best-of-breed suppliers together with software and service wraps to match the needs of our resellers and dealers. However, this approach brings with it unique challenges in support and incident management.
How quickly are you notified?
Should an incident occur, you need to know what the problem is and how long it will take to be fixed. You want to be on the front foot, pro-actively contacting your customers with detailed communications regarding the incident. If all suppliers in the chain do not have a well thought-through incident management process, a wave of dissatisfied end-user customers will quickly build, with the last reseller in the chain taking the brunt of the criticism. Organisations not used to dealing with the channel may not understand the imperative for fast, accurate information. Those that are not channel-only will often prioritise their direct customers over their channel partners.
How should it be done?
Ideally incidents are categorised by priority. We use the UTIL guidelines categorising incidents by impact and urgency, P1, P2 etc. Suppliers need to get the initial communication out to customers within the first 30 minutes (we aim for 15) explaining the issue. It is important to have clear communication between the engineers working on the problem and the support team managing calls and communications. Updates need to be at least hourly. Communication paths need to be established in advance between suppliers and departments for effective updates.