What is contact centre business continuity?
Business continuity is an organisation’s ability to keep delivering essential services during and after a disruption. For a contact centre, that means customers can still get through and be helped, even if a building, system, telephony carrier or team is unavailable.
It’s usually documented in a business continuity plan (BCP), which sets out the risks, the services that must keep running, who does what, and how quickly things must be restored. Alongside it sits disaster recovery (DR): the technical side of restoring systems, data and connectivity.
Continuity matters more in a contact centre than in many other functions, because disruption often creates demand. A storm that cuts power to an office also triggers a call avalanche from customers whose power is off.
What can disrupt a contact centre
A good plan considers a wide range of scenarios:
- Site loss: fire, flood, earthquake, power cut or loss of building access.
- Technology failure: the contact centre platform, CRM, network or a key integration goes down.
- Telephony failure: a carrier outage, or call capacity running out during a spike.
- People disruption: a pandemic, illness outbreak, transport disruption or severe weather that stops staff getting to work.
- Cyber incidents: ransomware or a security breach that forces systems offline.
- Supplier failure: a key vendor or outsourcer being unable to deliver.
New Zealand and Australia face real natural hazard risk, including earthquakes, cyclones, floods and bushfires, so planning for physical disruption isn’t theoretical.
Building a resilient contact centre
Resilience comes from removing single points of failure:
- Distribute people. Home-based agents across many locations, or multiple sites, mean no single event takes everyone offline.
- Use resilient cloud technology. A CCaaS platform hosted across multiple data centres doesn’t depend on equipment in your building.
- Plan telephony failover. Numbers should be able to route to alternative destinations, with messages ready to update quickly through the IVR.
- Have backup capacity. An overflow or surge capacity partner can take calls if your own team can’t.
- Prioritise critical contacts. Decide in advance which calls must be answered first, such as hazard calls and medically dependent consumers.
- Keep information flowing. Agents need up-to-date scripts and knowledge during an incident, and customers need proactive updates.
Testing the plan
A plan that has never been tested is an assumption. Good practice includes:
- Regular, realistic exercises, ideally taking primary systems offline to see what actually happens.
- Scenario walk-throughs with the people who would make decisions on the day.
- Reviewing results and updating the plan, contact lists and runbooks.
- Testing after change, such as a new platform, site or provider.
Regulatory and customer context
Some sectors face specific expectations. Energy retailers and distributors in New Zealand and Australia have obligations to support medically dependent or life support customers and vulnerable consumers, which depends on being reachable when things go wrong. Government agencies often have their own resilience requirements. Even without a formal rule, customers expect to get through during an emergency, and remember when they can’t.