It's the question we hear most often from businesses considering a move to a cloud phone system: "If everything runs over the internet, what happens to our phones when the internet goes down?"

It's a fair question, and the honest answer is: it depends entirely on how the system is designed. A poorly configured cloud phone system can indeed leave you with no inbound or outbound calls during an outage. But a well-designed system — one where business continuity has been thought through properly — handles an internet outage gracefully, often without customers even noticing anything is different. Here's how the key mechanisms work.

The mobile app — calls follow your staff, not your office

Modern cloud phone systems aren't tied to a physical box in your comms room. They're software, and that software can run on a mobile phone just as well as on a desk handset. Most business cloud PBX platforms include a smartphone app that lets your staff make and receive calls on their business number from anywhere with a mobile data connection.

This means that even if your office NBN connection drops completely, inbound calls to your business numbers can still ring on staff mobiles. You can configure this as a simultaneous ring (desk phone and mobile ring at the same time) or as an automatic failover (mobile rings when the desk phone doesn't answer, or when it's unreachable).

The business impact of an internet outage for an organisation running this way is often much smaller than people expect. Customers call your number, and your staff answer on their mobile. The caller has no idea anything unusual is happening.

Call forwarding and auto-attendant rules

Even if staff aren't using a mobile app, your phone system's call routing rules keep working because the intelligence lives in the cloud, not at your premises. Your auto-attendant, hunt groups, and voicemail are all hosted on servers that remain operational regardless of what's happening to your office internet connection.

Well-designed systems allow you to configure failover call routing — if a particular extension or hunt group fails to answer within a set time, the call automatically routes to a nominated mobile number, a different location, or a voicemail service. This rule can be applied broadly: if your office stops responding (which is how an internet outage looks from the cloud's perspective), route all inbound calls to your mobile team.

Setting this up before an outage happens — rather than scrambling to reconfigure your phone system during one — is the key. A good provider will help you document and test your continuity rules at setup, not after the first time they fail you.

4G/5G failover internet — keeping everything running

The cleanest solution for businesses where any internet interruption is unacceptable is a 4G or 5G failover connection. This is a secondary internet connection delivered via a mobile data SIM, housed in a router that monitors the primary NBN connection continuously. When the primary connection drops — typically detected within 15–30 seconds — the router automatically switches all traffic, including VoIP, to the 4G/5G backup.

From the perspective of your desk phones, cloud apps, and any other IP services, the transition is near-seamless. Calls in progress may experience a brief interruption as the failover switches, but new calls route correctly immediately. For most businesses, 4G/5G failover is fast enough and capable enough to sustain normal operations for hours or even days.

The cost of a 4G/5G failover connection is modest compared to the revenue impact of even a two-hour outage for a busy business. It's one of the most cost-effective resilience investments available.

Dual WAN — two primary connections

For businesses with the highest availability requirements, dual WAN takes the failover concept further. Rather than a primary NBN connection with a 4G backup, you run two substantive connections — for example, NBN Enterprise Ethernet and a business-grade 5G fixed wireless service — with automatic failover between them. Both connections are capable of carrying your full traffic load. The router monitors both and switches automatically if either fails.

This approach is also useful for load-balancing traffic across both connections during normal operation, maximising available bandwidth while maintaining the failover capability.

What about traditional phone systems?

A common assumption is that a traditional on-premises PBX is more reliable because it doesn't depend on internet. This is worth examining carefully. A traditional PBX does handle calls locally — but it depends on the PSTN for inbound and outbound calls, and the PSTN connection to your building is not immune to failure. More importantly, a traditional PBX has no mobile app fallback. If the system can't be reached, calls don't route anywhere.

Traditional systems also depend on mains power. Without a UPS, a power cut kills a traditional PBX just as surely as it kills anything else. And traditional systems have no cloud-hosted intelligence — if the box dies, calls don't go anywhere until someone physically replaces or restores it.

Cloud phone systems, by contrast, have their intelligence hosted in data centres with redundant power and connectivity. The vulnerability isn't the phone system itself — it's the last-mile connection between your office and the internet. Address that with mobile fallback and/or 4G failover, and a cloud phone system is often more resilient than the traditional PBX it replaced.

4G failover is an add-on worth asking about. If you're on business NBN through Caznet, ask us about 4G failover as part of your connectivity setup. It's a straightforward addition that can save you significantly during an outage — and it covers your phone system, your cloud apps, and everything else that depends on internet access simultaneously.

Design for failure before you need it

The core principle here is straightforward: think about failure modes before they happen, not during an incident. An outage is not the moment to discover that nobody knows how to redirect inbound calls, or that the mobile app was never set up on anyone's phone, or that the 4G failover router was never configured.

When Caznet designs and installs a cloud phone system, we build and test the continuity configuration as part of the initial setup. We want your business to handle a worst-case internet outage as smoothly as possible — because the test of a phone system's reliability is what happens when something goes wrong, not when everything is working perfectly.

If you'd like to talk through your current setup or are considering a move to a cloud phone system, get in touch with our Adelaide team on 1300 229 638 or through our contact page.