Skip to main content

Help guide

Will your business phones work in a power or internet outage?

Maybe, but do not assume they will. Your phones need every part of their calling path to work: the handset, local equipment and power, any connection they use, and the relevant provider’s service. A local phone system, a cloud service and a mobile can fail in different ways. A battery or an internet backup does not guarantee calls.

Plan for emergency calls first

For urgent police, fire or ambulance help, call Triple Zero (000). Keep an alternative working phone available, such as a charged mobile, and make sure staff know where it is and the site address. ACMA advises that most NBN-connected services will not work during a power outage, so an office phone may not be able to reach 000.

A mobile 000 call can use another available mobile network if your own provider has no coverage, but it still needs coverage from at least one Australian mobile network. Network outages can also affect calls. The Australian Government warns that 000 cannot be reached from a mobile if no network has coverage. If a call cannot connect, use another working phone or, if safe, move to a place with coverage and try 000 again. Follow your site’s emergency procedures. Plan an alternative with your provider and safety lead if coverage is unreliable; never assume a mobile is a guaranteed emergency path.

Agree separate arrangements for anyone who needs accessible emergency communication. Never call 000 simply to test a phone or a continuity plan. If an emergency is happening, call for help rather than starting a test.

Dependency map

A working phone may depend on more than the handset

  1. Power Check power to the equipment your service needs.
  2. Connection Identify the internet or network path used for calls.
  3. Voice service Check the provider and any configured fallback.
  4. Endpoint Identify a working desk phone, softphone or mobile.

The actual path differs by system. A working mobile and emergency calling can still depend on coverage and battery.

Trace the path your calls take

Ask your phone administrator or provider to identify the actual equipment and services at each site. You may use more than one of these paths:

  • On-premise system: A phone system at your site may need power for its controller, handsets, network switches and gateways. It also needs a working outside line or connection and provider service for external calls. Some internal calls may work when the external connection fails, but only if your particular system and endpoints still have what they need.
  • Cloud phone service: A working hosted platform is only one part of the path. A desk phone or computer still needs power, a working local network and a connection to that platform. A separate location or approved mobile app may be an option if its device, connection and service work; confirm how calls reach it with your provider.
  • Mobile phone: A charged handset using ordinary mobile calling depends on a usable handset and mobile network. A business phone app may instead depend on mobile data or Wi-Fi and the app’s service. A mobile will not automatically receive calls to the business number unless the relevant arrangement is in place and working.

Powering just the desk phone is not enough if a switch, router, connection box or phone controller also loses power. NBN Co explains that connected equipment needs its own backup power and that outages can last longer than batteries. An upstream network outage can still interrupt service even when equipment at your site is powered.

Build a one-page continuity card

With the person responsible for phones, record the following for each site. Keep an accessible offline copy with staff who need it, and update it when equipment, providers or contacts change. Record roles and approved contact methods, not passwords or security codes.

  • Site and essential calls: Identify the site address, the main business number, who answers it and which calls must be prioritised.
  • Dependencies: List the handsets, phone system, switch, router, connection box, power supplies and providers involved. Mark each backup-power or backup-connection arrangement as confirmed or unknown; include the expected battery limits only when verified.
  • Emergency path: Record where the alternative working phone is kept, how it is kept charged and the known coverage limitations. Note the agreed action if that path is unavailable.
  • Incoming and outgoing calls: Record the agreed alternative, who may activate it, whether customers can still reach the usual number, and any limits. Do not assume diversion or automatic failover is configured.
  • People and return to normal: Record the decision-maker, provider escalation route, who updates staff and customers, and who confirms the normal call path has been restored.

Example: A reception team uses a cloud phone service over its office internet. The manager records that an internet outage may stop desk-phone calls even if the lights stay on. A charged mobile is the separate emergency option, subject to coverage. The provider has not yet confirmed a diversion for the main number, so incoming business calls are marked unknown, not “covered”. The manager assigns a follow-up to confirm the routing and arrange a supervised test.

Continuity card

Agree the fallback before an outage

  1. Contacts Keep provider and escalation details accessible offline.
  2. Alternative Identify a working alternate phone or communication method.
  3. Dependencies Check power, connectivity, mobile coverage and battery.
  4. Test Agree safe, non-emergency tests with the responsible provider.

In an emergency, use an available working phone to call 000. Do not make test calls to 000.

Agree a controlled test

Start with a discussion of a power outage, an internet outage and a provider outage separately. For each, ask what should still work, what is unconfirmed and what staff should do. A desktop walkthrough can expose gaps without disrupting service.

Before any live test, agree the scope and timing with the site decision-maker and authorised phone and network providers. Identify affected users and safety-critical services, the person running the test, the alternative available during it, a stop condition and a way to restore normal operation. Do not unplug, reset or change shared equipment or routing without approval. Do not simulate an outage if it could compromise emergency access, monitored alarms, lift phones or other critical services; involve their equipment provider first.

Using an agreed non-emergency number and another consenting caller, check an incoming call to the business number and an outgoing call from the intended alternative. Confirm both people can hear each other and, where applicable, that the right person answers. Record the scenario, actual result, limitations, owner and follow-up. Stop if an unexpected service is affected or the agreed emergency alternative is unavailable. After restoration, repeat the ordinary call checks and have the owner confirm the normal route. A successful test shows what happened under those conditions, not what every future outage will do.

When to ask for help

If the equipment, emergency path or call routing is unknown, ask your authorised phone administrator and the relevant phone or internet provider to confirm it before relying on a workaround. Ask the supplier of any safety-critical device about its separate continuity arrangements. If Comm Centre is your provider, you can check the Comm Centre Support page for contact options; use a verified working contact method for urgent matters rather than assuming a web request has been received.

Sources and further reading