Business continuity for the phone line
Most continuity plans say where the calls go. Far fewer say what happens to the person on the other end of them, which is the part that decides how the day is remembered.
Short answer. The communications section of most plans is written outward: who is told, in what order, what goes on the website. The inward half, the calls that arrive because of the incident, is usually one line about diverting to a mobile. That stops the phone ringing out and does very little else. What a plan needs is a named arrangement that answers every caller, tells them something true, and writes down what they said somewhere the response team will actually see it.
What the communications section usually says, and where it stops
Open most continuity plans at the communications section and you find the same structure. Who can declare an incident. Who is notified, in what order. What goes on the website and the social accounts. Who is permitted to speak to the press. It is a good structure and it is almost entirely about what you say outward.
The telephone usually gets one line, and it names a destination: calls divert to a mobile, or the answering service picks up. That line is where the plan stops and the problem starts, because a destination says nothing about what the caller experiences once they arrive at it. During an incident the phone is not a channel you are broadcasting on. It is the channel people use to reach you, and the volume goes up for exactly the same reason the plan was invoked.
The call tree, and why it ages fastest
The call tree is the cascade for reaching your own people. One person rings two, those two ring four, and so on until everybody has been told. Nearly every plan has one and it earns its place.
Two things about it are worth saying plainly. It ages faster than anything else in the plan, because it is built on mobile numbers and on who is on call this month, and both of those change constantly while the document does not. Most are a spreadsheet, exercised once a year, and quietly wrong somewhere by the time they are needed.
The second is more structural. The call tree only points outward. It is a mechanism for telling your staff what has happened. It does nothing whatever for the people ringing in, and in most incidents those are the larger number and the more anxious.
Diverting to a mobile: what it solves, and what it moves
Diverting the main number to a mobile is worth having. It takes minutes to arrange, it costs nothing, and it stops the phone ringing out into an empty office. Every plan should know how to do it and who is authorised to.
It is worth being clear-eyed about what it does not do. A mobile answers one caller at a time, so the second and every caller after them get voicemail. Nothing is written down except in whatever notes that person manages to take while doing something else. Nothing is triaged, so the genuinely urgent call and the routine one are indistinguishable until answered. And the phone is usually held by whoever has the most to do that day, which is the worst possible allocation of an incident's attention.
The divert solves a ringing telephone. It moves everything else onto one person.
Not engaged is not the same as answered
Somebody ringing during a disruption wants three things, in this order. To be answered rather than queued. To be told something true, even when the true thing is that you do not know yet. And to have what they said written down somewhere a person will act on it, so that ringing once was enough.
A line that connects but takes a message satisfies the first and fails the other two. That gap is where complaints come from afterwards, and it is worth designing for in advance, because the calls that arrive in the first hour of an incident are the ones people describe for years.
Where disaster recovery planning usually puts the phone
Technical recovery plans are thorough about systems and thin about the switchboard. Servers have a recovery time objective; the telephone rarely does. If your plan sets a target for restoring a finance system but says nothing about how long the main number may go unanswered, that is worth correcting, because the phone is the first thing anybody outside the organisation notices.
An arrangement that is live in hours, without a procurement cycle
Speed and governance normally trade against each other, and every organisation standing up an urgent line has had to choose. Fast means handing the calls to a third party, who then holds the recordings and the data. Governed means a security review, a data processing agreement and several weeks you do not have.
Enquiry 360 sits differently, and not by being clever about it. It deploys into your own Microsoft tenant, so the calls, the transcripts and the records stay inside your own environment under your own retention policy. There is no vendor platform for your security team to assess and no new processor holding your callers' data, because there is no vendor holding anything. Where you engage us to help configure it, that access is granted by you and covered by our published processor terms. The configuration is the work, and the configuration is hours.
That matters more in an incident, not less. A public health line takes health information from worried people. An incident line after a fire takes details about vulnerable residents. Those are precisely the calls that should not end up on somebody else's platform under a contract signed in a hurry.
It answers multiple calls at once, so nobody meets an engaged tone, it asks the questions you configured in the order you set, and every call becomes a structured record in your own Microsoft Dataverse that the response team can sort, count and act on. Where a call needs a person, it puts them through to a number you nominate, with what they have already said attached. What it will not do is claim a transfer it cannot make.
What to write in the plan
Useful whether or not you ever buy anything. If your communications section answers these six, the telephone half of your plan is in better shape than most:
- Which numbers must stay answered, and who owns each one. Main switchboard, out of hours, and any line printed on something you cannot recall.
- What a caller hears in the first ten seconds, in the words you would want used, including what is said when you do not yet know the answer.
- What must be captured from every call. Name, number, location, and the one or two things that let you rank urgency. Agree it in advance and it will be the same on every call.
- Where those records land, and who reads them. A message nobody has been assigned to read is not a record.
- Who can put the arrangement live, and how long it takes. Name people rather than roles, and write down the actual elapsed time rather than the intended one.
- When it was last tested, and by whom. Include the phone in the exercise. Most plans test the call tree and never ring the main number.
Hear what a caller would hear. Ring 01905 918444. It is a live line, not a recording, and it takes about a minute.
From £99 + VAT a month. Free setup, cancel anytime. Or read where your call data lives and the product terms and governance.
Frequently asked
What should a business continuity plan say about the telephone system?
More than where the calls go. Name the numbers that must stay answered and who owns each one, say what a caller should hear in the first ten seconds, say what has to be captured from every call, and say where those records land and who reads them. A destination on its own is not a plan, because it says nothing about what happens to the person on the other end of the line.
What is a call tree in a business continuity plan?
The cascade for reaching your own people: one person rings two, those two ring four, and so on until everybody has been told. It is useful and most plans have one. Two things are worth knowing about it. It ages faster than anything else in the plan, because it is built on mobile numbers and on who is on call, and both change constantly. And it only points outward. It tells your staff what has happened. It does nothing at all for the people ringing in.
How do you divert calls in an emergency?
Most organisations divert the main number to a mobile, which is genuinely worth having and takes minutes to arrange with your provider. What it does is stop the phone ringing out. What it does not do is answer more than one caller at a time, keep a record of what was said, or tell the difference between an urgent call and a routine one, and the person holding that mobile is usually the person with the most to do.
What goes in a business continuity communication plan?
Usually who declares an incident, who is told in what order, what goes on the website and who speaks to the press. That covers everything you say outward. The gap in most plans is inward: the calls that arrive because of the incident, from people who are worried, and what happens to those between the first ring and somebody acting on them.
Does this help with ISO 22301 or FCA operational resilience?
It gives you something concrete to point at where those frameworks ask how a service stays available and how it is tested. The duties sit with you, and no supplier can discharge them for you, so treat this as a capability you can name in the plan rather than a compliance answer in itself.
How quickly can a line be stood up?
Hours rather than weeks, and the reason is structural rather than a claim about how fast we work. The deployment goes into your own Microsoft tenant, so there is no vendor platform for your security team to review and no new processor holding your data. The configuration is the work, and the configuration is hours.
Can we test it before we need it?
Ring 01905 918444. It is a live line rather than a recording and it takes about a minute. Testing what a caller actually hears is worth more than reading about it, which is also true of the arrangement you have in your plan today.