When is a Disaster not a Disaster for Support?
When you have a plan

WhenisaDisasterNotaDisater
What is your ability to deliver support if the building loses power? Or if there is a small fire in the kitchen? Or if the roads nearby are closed and people can’t get to the office? None of these things are actually disasters, and all of them can happen for very ordinary reasons. The fact is these and many other situations may disrupt your ability to deliver support to customers. Do you have a plan?

By Jerry Stalick

Vice President at F5 Networks and Chair of the Member Advisory Board for the Association of Support Professionals

Taking the time to create a Disaster Recovery or Business Continuity Plan for support faces two challenges among Support professionals. First, it’s intimidating. Secondly, formal responsibility for DR or BC usually doesn’t belong to the Support organization.

The notion that DR or BC doesn’t belong to Support is a dangerous position to take. I’ve seen too many official corporate plans which focused on things like HR records or corporate financial data but gave no more than passing thought (at best) to how the company would continue to service customers during a disruption.  But when something goes wrong, it’s left to the Support leadership to answer questions about how their organization responded.

Every support organization should be prepared for a disaster, even if the “disaster” is nothing more than a toaster fire.

Related Articles

6 Ways to Apply AI to Technical Support

Support has been relentless in the pursuit of continuous improvement, yet the function of Support has remained fundamentally unchanged for decades. AI is a critical catalyst that will help enable an inevitable Support transformation. This article introduces 6 ways to apply AI to technical support.

Customer Experience vs. Customer Success – Similarities and Differences

The terms Customer Experience (CX) and Customer Success (CS) are commonly used within the service industry. Sometimes CX and CS are used to describe the same or similar things and other times to describe complexly different actions, activities and outcomes. This article offers definitions for each term and identifies similarities and differences between CX and CS.

Time to Resolve

Time to Resolution (TTR) is a metric to measure the elapsed time it takes for Support to resolve a case. This article introduces the definition and inputs required to measure TTR.

Do you have ideas for using AI?

According to Svetlana Sicular of Gartner the reason why AI initiatives are rolling out so slowly, is the lack of ideas. Françoise Tourniaire of FTWorks offers insights and ideas for applying AI to Support.