A power outage at the office rarely affects only the phone system. Routers, switches, Wi-Fi, IP phones, and local servers all shut down at the same time. What Are Your Phone Options During a Power Outage? Whether it still works, therefore, does not depend solely on the telephone system. The decisive factor is whether power, Internet access, end devices, and call routing are designed as an integrated system.
For businesses, this isn't just about incoming calls. Customers must still be able to reach a phone number, employees need clear escalation procedures, and emergency calls must be able to be placed reliably. A good solution therefore separates the reachability of the company's phone number from the availability of a single location.
Which phone services actually continue to work during a power outage
The short answer is: Mobile phone service is often the fastest fallback option during a local power outage. Cloud-based telephony can also continue to operate if the phone system is running in the data center and calls are automatically rerouted to accessible cell phones or other locations. Traditional IP phones at the affected location, on the other hand, will not work without a local emergency power supply.
Even a cellular network is not an inexhaustible resource. Cellular sites typically have battery backup, and some also have additional emergency power systems. However, how long they remain operational during a widespread or prolonged outage depends on the specific network, its load, and the local situation. Capacity may decrease if there are many simultaneous calls or data connections.
The once-common assumption that an analog landline connection would always have a power supply is no longer viable for today’s business planning. Telephony is now predominantly IP-based. Even if a connection is technically available, routers and phones will remain offline without power. Anyone who relies on being reachable should therefore not base their emergency strategy on outdated assumptions about landline service.
Cloud PBX: The phone number remains separate from the office
With a hosted cloud PBX, the central call-handling logic is located not in the office but in a secure data center. If the office location goes down, the system can still answer calls, play IVR messages, and execute defined rules. So a caller won’t simply hear a busy signal just because the lights go out at the office.
The configuration is key. In the event of an outage, clear objectives are needed: for example, forwarding the main number to an on-call service, to Teams users on their cell phones, or to a secondary location. Time-based rules and queues can also be configured to operate differently during normal operations than during emergency operations.
A local telephone system can also be designed to be fail-safe, but this requires significantly more on-site infrastructure. In addition to the system itself, the network, SIP trunk, session border controller, and end devices must all be powered. The more components that are operated locally, the more careful the emergency power planning must be.
Microsoft Teams and softphones as a fallback option
Microsoft Teams or a softphone on a smartphone can be very helpful in the event of an office outage. Employees can answer business calls using their usual phone number, provided that the PBX or Teams integration is accessible from outside the office and the mobile device is connected to the internet via cellular data or a working Wi-Fi network.
This is particularly useful for distributed teams. However, a softphone is no substitute for an emergency power plan: If the battery is dead, the cell tower is overloaded, or the phone number isn’t routed correctly to Teams or mobile devices, reachability remains limited. The technology must be set up and tested with the responsible individuals before an incident occurs.
How to Ensure Reliable Phone Service During a Power Outage
A robust solution combines multiple layers. It’s not enough to simply place a UPS under the router or just set up call forwarding. Companies should first define which communication functions must remain available and for how long. For a small business, it may be sufficient to forward the main number to the owner’s cell phone for two hours. For a medical practice, a service organization, or a company with 24-hour on-call support, the requirements are usually more stringent.
1. Prioritize critical communication channels
Not every extension needs to be available during a power outage. Priority is generally given to the main number, on-call numbers, emergency contacts, and communication with key customers or suppliers. Determine who will answer calls, who will make decisions, and how customers will be notified.
A brief emergency announcement can be helpful—for example, one that mentions limited operations and provides an alternative way to contact the company. It should remain factual and be activated only when delays are actually expected. Being easily reachable does not mean that all processes must continue unchanged. It is important that callers receive guidance and that no call is lost.
2. Plan the Power Supply for the Network and Telephony Systems
An uninterruptible power supply (UPS) bridges short outages and provides time for an orderly switchover. At a minimum, the following should be protected: Internet routers, firewalls, central switches, Wi-Fi components, DECT base stations, local PBX components, and, if necessary, a session border controller. For IP phones with PoE, the PoE switch must also be connected to the UPS.
The runtime of a UPS is not a fixed value. It depends on the connected load. A small battery can power a router and firewall for a while, but not an entire office floor. For longer outages, a generator or a second location with an emergency power supply should be considered. Equally important: The UPS must be maintained. Aging batteries often deliver less power than expected in an emergency.
3. Set up redundant Internet access
Having power on-site alone isn’t enough if the internet connection goes down. For VoIP and cloud services, it therefore makes sense to have a second access path, such as a separate fiber-optic or cable connection, or an LTE/5G backup. The backup connection should use a different technical route than the primary connection. Having two contracts is of little help if both lines terminate at the same building entry point.
Automatic failover in the firewall ensures that traffic is rerouted in the event of a failure. Prioritization and sufficient bandwidth are key to ensuring voice quality. A cellular backup is generally well-suited for individual calls and administrative tasks, but may reach its limits when handling many concurrent calls.
4. Route calls regardless of location
The SIP trunk and PBX rules should be able to redirect incoming calls to specific destinations when a user is unavailable. Possible destinations include cell phone numbers, another company location, external on-call services, or a separate emergency response team. This rule should not have to be set up manually only after the server room has already been shut down.
With a cloud PBX, such scenarios can be managed centrally. An Ayrix phone system, for example, can connect the business phone number to IP phones, cell phones, and Microsoft Teams without creating a new siloed solution for every change. Careful planning of call routes and permissions remains crucial.
Considering Emergency Calls, Data Protection, and Security
Emergency calls are A separate checkpoint. For calls made via softphone, Teams, or call forwarding, it must be clear what location information is being transmitted and from where the call is being made. In Germany, the 110 and 112 numbers are particularly relevant. Employees should be aware that, in an emergency, they must clearly state their actual location, especially when working remotely or from home.
The security architecture must not be compromised during backup operations either. An LTE router that is used temporarily without firewall rules or VPN permissions creates new risks. A preconfigured, controlled failover path with clear access rights is recommended. This ensures that communication remains possible without unnecessarily compromising confidential data.
For companies with recording requirements, CRM integration, or sensitive customer data, it’s also important to check which features remain available during emergency mode. A call can be forwarded, while call recording, CTI pop-ups, or CRM documentation may be limited. This is not a problem as long as those responsible are aware of this difference and define processes to address it.
Test for an emergency before it happens
An emergency plan is only reliable once it has been tested. During a scheduled maintenance window, disconnect the primary Internet connection or simulate a power outage for the relevant components. Afterward, check not only whether a phone rings, but also whether the main number is being forwarded correctly, whether the automated messages are working, and whether the appropriate personnel can answer the call.
Document the results clearly and concisely: Which devices are connected to the UPS? How long did the communication last? Which phone numbers were redirected? Who is authorized to activate or change the emergency policy? Update this information whenever there are changes to staff, phone numbers, or locations.
Winet does not plan for such scenarios as an add-on after the telephony setup is complete, but rather as part of the communications architecture. A dedicated contact person can help determine whether a cloud PBX, a SIP trunk with failover, a Teams integration, or a combination with mobile networks provides the right backup solution for your business.
The most sensible next step is to take a quick inventory: Which phone number must always be reachable, which equipment is currently connected to a single power circuit, and who will answer the first customer call if the site goes down? These three answers form the basis of an emergency plan that goes largely unnoticed in day-to-day operations but works when it counts.
Current
Centrally Manage Corporate Communications
Guide to Emergency Planning for Telephone Services in the Workplace
How to Set Up Emergency Routing for Business Calls Correctly
Digital Sovereignty in Telephone Systems
Plan for VoIP Downtime and Stay Reachable
