When Your Internet Drops, Where Do Your Business Calls Go?

  • Home
  • When Your Internet Drops, Where Do Your Business Calls Go?
When Your Internet Drops, Where Do Your Business Calls Go?

Your office loses internet. Staff can still use mobile data, but customers keep calling the main business number. Does it ring somewhere useful, play a message, or disappear into a queue nobody can answer?

For Australian SMEs using VoIP or a cloud PBX, that is a more useful continuity question than simply asking whether the router has a backup connection. Before summer leave and reduced staffing, test what happens to the customer conversation when the normal answering path is unavailable.

Separate the phone number from the office connection

A cloud phone platform can be operating normally while your premises cannot reach it. The number, provider platform, office internet, local power and staff devices are separate dependencies. A plan that addresses one does not automatically cover the others.

Ask your provider where an outage diversion is applied. A rule held in the provider network or hosted platform may redirect incoming calls without the office equipment being online. A rule that depends on a powered local PBX or handset is a different arrangement. Confirm the actual behaviour of your service rather than assuming every call-forward feature works during an outage.

Telstra’s Business Resumption Service+ illustrates network-based diversion using preconfigured plans and rollback. It is an enterprise product sold in blocks of 25 numbers, not a default recommendation for a small office. The useful principle is to arrange your own provider’s supported fallback before you need it.

Choose the fallback for the conversation, not just the number

Consider a small service business with one published number, a booking queue and three staff. Diverting everything to the owner’s mobile may preserve some calls, but it also creates a single busy person and may send customers to a personal voicemail greeting. Sending callers into an unstaffed queue preserves the technology but loses the service.

A better design names the person or team that will answer, the hours they cover, the overflow destination and the message a caller hears when nobody is available. Check whether queue behaviour, transfers, caller identification and voicemail remain suitable on the fallback path. Features, licensing and diversion charges vary by provider.

Write down the trigger as well. Does the platform detect an unreachable endpoint, wait for a no-answer timeout, or require someone to activate a plan? Agree on an acceptable delay. A working diversion that takes too long to activate can still frustrate customers.

Backup internet and backup power solve different problems

A cellular backup connection can provide another route to a hosted phone system, but it is not a guarantee of uninterrupted calls. Coverage, network congestion, the router’s failover behaviour and the phone platform’s reconnection process all matter. An existing call may drop even if new calls work once connectivity returns.

Check the actual network behind a second mobile service rather than relying only on a different retail brand. Shared infrastructure can leave supposedly separate paths exposed to the same problem. Roof-mounted antennas, where appropriate and professionally installed, address connectivity conditions; they do not implement call diversion or replace a voice continuity plan.

Power needs separate attention. nbn explains that mains-powered equipment connected to its network needs its own backup power, and a premises battery cannot fix a power loss elsewhere in the access network. Review the connection box, router, any powered switching and the phone equipment as a chain. Have your IT provider size and test backup power for the required operating period.

Run a controlled customer-call rehearsal

Book a quiet maintenance window with your phone and IT providers. Tell staff what is being tested, keep an independent working contact method available and record the original configuration. Do not casually disconnect shared services that support alarms, payment terminals or other critical equipment.

  1. Call the published number from outside the business. Confirm the normal greeting, queue and answer path first.
  2. Simulate loss of office connectivity safely. Use the provider’s agreed test method. Record where the next call lands and how long the change takes.
  3. Test a busy fallback and a missed call. Listen to the actual voicemail greeting and confirm someone can retrieve the message. Check who follows up.
  4. Confirm staff can call back appropriately. Ask what caller ID and permissions apply on the supported mobile or alternate-site arrangement. Do not assume a personal mobile call displays the business number.
  5. Restore and retest. Return to the normal route, remove temporary diversions and confirm calls no longer bypass the intended team.

Keep the evidence simple: the number tested, interruption scenario, activation time, person who answered, exceptions and restoration result. Never make test calls to Triple Zero. Ask your provider separately about emergency calling, location information and service limitations, and follow specialist advice for alarm or life-safety services.

Leave a plan someone else can operate

The final result should fit on one operational page: who can activate the fallback, how they securely access the provider portal from another connection, which destination to use and how to reverse the change. Protect administrator access with the provider’s available security controls, and nominate a backup authorised person so leave or illness does not become another outage.

Xpansion Technologies can help review the relationship between your business telephony, connectivity, power dependencies and staff call workflows. Start with one measurable outcome: when the office internet is unavailable, a new customer can still reach the right person or leave a message that is acted on.

Sources


Leave a comment