Current Location ：
When the Phones Fail: What Staff Should Actually Do
Business continuity plans for voice tend to be documents about infrastructure: failover paths, redundant links, recovery time objectives. They are written for the people who will fix the system. The people who will experience it, the staff answering the phones, usually have no instruction at all, and their improvised responses often make things worse: everyone rings the switchboard mobile at once, the one working number becomes unusable, and customers get conflicting information.
The First Five Minutes
Staff need three answers immediately: is this affecting everyone or just me, is someone already working on it, and what should I do with the customer in front of me or on hold. A one-page card that answers those three questions, printed and kept at each desk, is more useful than a fifty-page plan that lives on a shared drive nobody opens during an outage.
| Situation | Immediate action | What not to do |
|---|---|---|
| No dial tone on one phone | Try another phone, report it, continue working | Reboot repeatedly and lose the fault evidence |
| Whole office affected | Follow the fallback instruction, notify the nominated contact | Every team ringing the same mobile number |
| Customer on hold | Take details, promise a callback, end the call politely | Leave the caller holding indefinitely |
| Inbound calls failing | Check the published alternative and use it | Publish a new number nobody has tested |
| Call quality poor but calls connect | Log examples with times and numbers | Assume it will resolve on its own |
One Person Talks to the Outside
During an outage, consistency of message matters as much as the technical fix. One nominated person should update the status message, the website notice, and the team, so that every customer hears the same thing. When five people improvise five explanations, the business looks chaotic and the support team spends the recovery answering questions about the message rather than the fault.
- Keep a printed one-page procedure at each main desk
- Nominate one person to own external communication during an outage
- Prepare and test the fallback number before it is needed
- Ask staff to record examples with time, number, and direction
- Review every outage afterwards with the people who lived it
The Fallback Must Be Tested
A fallback that has never been used is a hypothesis. A diverted mobile number that was correct last year, a message that refers to a service that has closed, an email address nobody monitors. Testing means deliberately routing calls to the fallback during a quiet period, confirming that someone answers and that the caller experience is acceptable, and recording the date. That test is uncomfortable and takes twenty minutes, which is why it is usually skipped and why it usually fails.
Afterwards Is Where the Value Is
The debrief after an outage is where most of the learning is, and it is the part that gets cancelled when the pressure ends. A short review covering what happened, what staff did, what worked, and what would have helped, produces concrete changes: a clearer card, a different fallback, a spare handset at reception. Without it, the next outage repeats the same improvised response.
Redstone Approach
Redstone deployments include a documented fallback arrangement and a staff-facing summary of what to do when the phone system is unavailable. We test the fallback path as part of commissioning, so that the procedure describes something that has been demonstrated rather than something that has been assumed.
Redstone Systems, Inc. founded in Delaware, USA in December 2002, has been the ODM vendor for many well-known communications companies, serving the Southeast Asian market. In 2020, Redstone Systems will begin to return to the North America market with its self-developed brand.
Redstone has a complete product line of intelligent voice gateways, providing IP-PBXs, analog VoIP gateways (FXS/FXO), digital VoIP gateways (E1/T1), border appliances, and session boundary controllers (SBCs).
With advanced technology in digital signal processor (DSP), speech coding and speech processing, as well as efficient operational tools such as cloud remote management, auto provisioning, Redstone gateways are widely used in markets of enterprise communications, cloud communications, call centers, operators’ IMS/SIP trunks, bringing users friendly, efficient and reliable communication experience.
For more information about Redstone, You can follow us on Facebook, Linkedin, and Youtube to be the first to get the latest news.
