IVR and phone menus

Emergency and Outage Messages for Your IVR: Plan Before You Need Them

How to prepare phone-menu messages for outages, closures and urgent incidents: what to say, who approves it, how to switch it on fast and how to lift it.

Call editorial team · Published · 5 min read

Phone systems fail at inconvenient times: a flood closes the office, a carrier has an outage, a data-centre problem knocks out a booking system. In those moments your IVR is the first thing callers meet. A clear message turns a confusing silence into a minor inconvenience. A missing one turns it into dozens of repeat calls. This guide helps you prepare messages and a process before the day you need them.

A person looking at a laptop in a dim office during a power outage
Illustrative image

The kinds of incident to plan for

Not every disruption needs the same message. Grouping them helps you prepare a small set of ready-to-use templates instead of improvising.

Common scenarios

  • Site closureWeather, power cuts, building problems or a public holiday that came as a surprise.
  • Phone system or carrier outageCalls cannot reach your agents, or only some can.
  • System outage behind the phonesAgents can answer but cannot see orders, bookings or accounts.
  • Safety or service incidentA product recall, a data issue or a local emergency where callers need instructions.
  • High volume eventA sudden spike after a news story or a service failure, where waits are far above normal.

What an emergency message should contain

Good emergency messages are short and follow a pattern. Callers want to know that you are aware, what they should do now, and when to expect an update.

A three-part structure

  1. Acknowledge"We are experiencing a problem with our phone lines." Say it plainly, without blame or drama.
  2. DirectTell them what to do: call back later, use a website or email address, or contact emergency services if life or safety is at risk.
  3. UpdateSay when more information will be available, or where it will be posted.

Keep the whole message under twenty seconds if you can. Callers who are worried are not in a mood to listen to long explanations. Avoid technical details, speculation about causes, and promises you cannot be sure to keep.

When safety is involved

If your service touches health, safety or property damage, include a clear instruction to contact local emergency services for life-threatening situations, and do it before anything else. A business that cannot answer the phone must never leave a caller with an urgent problem and no direction. Our guide to Veterinary Emergency Calls shows how a sector with urgent calls handles this.

Templates to adapt

SituationStarting wording
Site closed"Our office is closed today because of [reason]. Our phones are not being answered. Please leave a message or visit our website, and we will reply when we reopen."
Phone outage"We are having trouble with our phone lines. Please try again later or contact us by email. We are working to fix this."
Systems down"Our team can take calls, but some systems are unavailable, so we may not be able to access your account. You may prefer to call again later."
High volume"We are receiving many more calls than usual. If your matter can wait, please try again tomorrow, or leave a message and we will call you back."

The process behind the message

A message is only useful if someone can switch it on quickly. In many businesses the person with authority is unreachable at 2 a.m., and nobody else knows how. Fix that in advance.

Emergency message readiness

  • Templates written for each scenario and approved
  • Named people able to switch the message on and off
  • A recorded voice or text-to-speech choice ready for each template
  • A diversion destination agreed for when phones cannot be answered on site
  • A test scheduled at least twice a year, including the lift
  • A way to tell staff and update the website or social channels at the same time

After the incident

Lifting the message is part of the job. Many businesses leave an emergency greeting running for days because nobody was assigned to remove it. After you do, place a test call, check hours and holiday settings are correct, and review what callers heard and when. Note what worked and what confused people, then update the templates. Related planning appears in Contact Center Crisis Readiness and After-Hours Call Handling.

Do not rely on the phone alone

A phone message reaches only people who call. Customers who are not yet calling need to learn of the problem elsewhere, and your team needs a shared story. When an incident starts, ask a few quick questions: where else can customers find out, and who updates those places?

Using the same sentences everywhere avoids mixed messages, and saves drafting time at a stressful moment. The email side is covered in Auto-Replies Done Well.

Tone in a bad moment

People in an emergency read tone more than content. Be calm, direct and sorry where an apology is due. Avoid phrases that sound defensive, such as "through no fault of our own", and avoid cheerful marketing language. A short "we are sorry for the inconvenience" is enough. If the incident affects safety, drop the apology and give the instruction first.

Finally, keep your promises small. "We will update this message by noon" is only worth saying if someone is assigned to do it. If you cannot be sure, say where to look for updates instead of naming a time.

Emergency messages in Call

Call has an emergency closure: while it is on, every queue plays the emergency closure message until the closure is lifted. It is switched on and lifted by the platform operator, not by a workspace administrator or manager, so agree in advance who contacts them and keep your closure message ready. Closures for specific dates, such as public holidays, are added by your team to a holiday calendar on the Inbound ops page, which queues use to decide when they are closed. Each queue also has hours, a closed greeting and a choice of taking a message or sending calls to an overflow queue when closed. The routing simulator lets you walk a pretend call through these rules to check where it would end up, without dialling anything. For the full picture, read Business Hours and Holidays in Call.

Frequently asked questions

How long should an emergency message be?

Aim for under twenty seconds: say what is wrong, what to do and when to expect news. Longer messages lose callers, who are already worried.

Should I name the cause of the outage?

Only if you are sure and it helps the caller. Speculating can create more questions or worse, be wrong. "We are having technical problems" is usually enough.

What if I cannot reach anyone to record a message?

Prepare text-to-speech versions of each template in advance so that wording can be activated without a recording session.

Do I need a different message in each language?

If your regular menu offers several languages, the emergency message should too, at least for the main ones. Pre-translate templates and check them with native speakers.

Can I divert calls to a mobile during an emergency?

Many phone systems support diversion to an outside number. Agree the destination and the authority to use it beforehand, and make sure that person can answer.

How often should I test the process?

Twice a year is a reasonable minimum, and after any change to the phone system or staff. Include the lifting step in every test.

Prepare an emergency closure message in Call

In the demo console you can try incoming calls in a simulation.

Related guides