Preparing Your Phone Lines for Emergencies and Outages
Prepare phone support for outages, closures and emergencies: risks, backup routes, caller messages, communication, drills and post-incident review.
Phone lines fail at the worst time. A fire alarm empties the office, a carrier has a fault, a storm knocks out power, a product problem sends every customer to the phone at once. In those moments nobody has time to write a plan. The teams that cope are those that wrote it earlier, kept it short and rehearsed it.

This article offers a practical outline for small and mid-sized teams. For the messages themselves, see Emergency and Outage Messages in Your IVR, and for the numbers that tell you how bad things are, What Contact Center Supervisors Should Monitor.
List what can go wrong
Make a short, honest list. For each risk, write what it looks like, how likely it is and how bad it would be. Not every risk needs a plan; start with the ones that are both plausible and painful.
| Risk | What callers experience | First response |
|---|---|---|
| Carrier or number fault | Calls do not connect or ring forever | Contact the provider; switch to backup route if available |
| Internet or power failure at a site | Agents cannot sign in | Move to home or another site; divert queues |
| Platform outage | System unavailable | Status check, divert to a backup number or message |
| Product or service incident | A flood of calls on the same topic | Clear message in the menu; brief agents; update frequently |
| Staff shortage | Long waits | Offer callbacks; call in cover; reduce menu options |
| Local emergency or closure | Site unavailable | Closure message; divert to another site |
Principles for a good plan
Keep the plan usable
- SimpleA page or two. If it needs a manual, nobody will read it in a crisis.
- SpecificNames, numbers and steps, not intentions.
- OwnedOne person decides, with a named deputy.
- ReachableStored where it can be opened if your main systems are down.
- PractisedDrilled at least once a year and after changes.
Backup routes for calls
Decide where calls go if your normal route fails. Options include forwarding to another site, to staff mobile phones, to an outside answering partner, or to a recorded message with voicemail. Each has limits: mobiles may not handle volume, partners need briefing, and voicemail needs someone to check it. Choose the simplest route that meets your needs and test it, including who has the authority and access to switch it on.
When the main route fails
- DetectAlerts, staff reports or a test call reveal the problem.
- DecideThe owner confirms the incident and the response level.
- DivertSwitch to the backup route or the closure message.
- TellUpdate callers, staff and key partners.
- RestoreReturn to normal and confirm with test calls.
Prepare the words in advance
A message written in a hurry is often vague, wrong or too long. Draft templates now for the likely situations: an outage, a site closure, a product incident, an unusual wait. Each should state what is happening, what the caller can do and when to expect an update. Keep them short and calm. Record and store the audio, or text for speech, so that switching on a message takes a minute. Avoid promising a fix time you cannot control.
- "We are experiencing a problem with our phone lines. Please leave a message and we will call you back, or contact us by [alternative channel]."
- "Our office is closed today because of [reason]. We will reopen on [day]."
- "We are aware of an issue with [service] and are working on it. You can find updates at [place]."
Leave callers a way to reach you for something truly urgent if that applies to your business. Keep the template wording in the same place as the plan.
Think too about the staff who will carry the plan out. In an emergency, people worry about their own safety and families first. Make sure your plan puts their wellbeing ahead of call volumes, and that it allows for the possibility that some key people cannot be reached. A plan that depends on one person answering their phone at midnight is not a plan.
Who does what
Write a simple contact tree: who is told first, who decides, who speaks to customers, who talks to the provider and who looks after staff. Include out-of-hours numbers and a deputy for each role. Give frontline staff clear permission to follow the plan without waiting for approval at every step. Staff should also know what to say to callers who ask about the incident, and what not to say, such as speculating about causes. Designing Escalation Paths That Work covers how to set up reliable handoffs.
Communicate beyond the phone
During a phone outage, customers need another way to learn what is happening. Prepare to post notices on your website and social profiles, send messages to those who have asked for them and update any automated email replies. Keep the same wording across channels. After the incident, thank customers for their patience, and follow up on anyone who tried to reach you and could not, using voicemails, missed-call lists and callback requests. Replying to Missed Calls with a Message and Callback Completion Rate explain how to make sure none are forgotten.
Know your providers
Your resilience depends partly on others: the phone carrier, the platform, the internet provider. Keep a one-page list of each provider with the support contact, how to report a fault, what their status page is and what backup options they offer. Ask each one what happens during their own outage, how you will be notified and whether you can switch routing yourselves. If a provider's answer is vague, treat that as a risk and plan for it. Review the list at least yearly, since contacts and procedures change.
Practise and review
A plan that has never been used will have gaps. Run a short drill once or twice a year: pick a scenario, walk through the steps, switch on a backup route and message, and place test calls. Time how long each step takes. Fix what you find, such as a password nobody has or an out-of-date number. After every real incident, however minor, hold a short review.
After-incident review
- What happened and when did we notice?
- How long did callers wait or receive no useful message?
- Did the backup route and messages work as planned?
- Were staff, customers and partners told in time?
- Which calls were missed, and have we followed them up?
- What three changes will we make to the plan?
Finally, keep the plan alive. Put a recurring reminder in the calendar to check contact details, test the backup route and re-read the messages. Small checks done regularly are what make a plan work when it is needed.
Preparing in Call
In Call, holidays and planned closures can be set so that callers hear a closure message, queues can be paused or drained, and queues can offer voicemail or callbacks. An emergency closure of every queue is switched on and lifted by the platform operator, so agree in advance who contacts them and keep your closure message ready. Supervisors can watch waiting calls and alerts, and a how-to guide describes the operator's option to divert all inbound calls in an outage. Test each of these before you need them. See Business Hours, Holidays and Closures in Call, Per-Queue Voicemail in Call and Callback Requests in Call.
Frequently asked questions
What should be in the first version of a crisis plan?
A list of likely risks, a backup route for calls, drafted caller messages, a contact tree and a named decision-maker. One or two pages is enough.
How often should we test the plan?
At least once a year, and after major changes to systems, sites or staff. Short drills are more useful than rare large ones.
What do we tell callers during an outage?
What is happening, what they can do instead and when to expect an update. Avoid guessing about causes or promising fix times.
Do we need a backup phone number?
Not necessarily. Many teams use call forwarding, a recorded message or voicemail. Choose according to your risks and ask your provider what is available.
What should we do after the incident?
Restore normal service, test, follow up with callers who could not get through and hold a short review to improve the plan.