A lost internet connection can stop far more than email. Card terminals may fail, cloud files can become unavailable, VoIP phones go quiet and staff may be unable to access the systems they need to serve customers. This business connectivity outage checklist gives small businesses a clear, calm way to respond without losing valuable time to guesswork.

The goal is not to turn your office manager into a network engineer. It is to make sure everyone knows what to check, who makes decisions and how the business keeps moving while the fault is investigated.

Business connectivity outage checklist: first 30 minutes

The first half-hour matters because it separates a minor local issue from a wider service failure. Start by confirming the scope. Ask whether one person, one area of the office or every device is affected. If staff can connect using mobile data but not office Wi-Fi, the problem is likely within the business connection or local network. If only one computer cannot get online, it may be a device issue rather than an outage.

Check the basics before restarting anything. Look at the broadband router, firewall and network switches for warning lights, unusual flashing patterns or a loss of power. Confirm that the building has electricity and that no one has unplugged equipment while moving desks, cleaning or carrying out other work.

Next, test more than one service. Try a wired computer and a wireless device. Check whether websites load, whether cloud applications such as Microsoft 365 are available, and whether the phone system can make and receive calls. This gives your IT support provider useful evidence and helps avoid a vague report that “the internet is down”.

Record the time the issue started, the systems affected and any recent changes. A new router, a power cut, building work, software updates or a changed network cable can all be relevant. Keep this record simple, but keep it accurate.

Tell staff what is happening

Silence creates confusion. Send a short internal message explaining what is affected, what staff should do for now and when they will receive another update. For example, ask people not to restart network equipment, not to use personal email for customer data and not to move files onto unapproved USB drives.

Give one person responsibility for updates. In a small business, that may be the office manager or director. This prevents several people calling the broadband provider with different descriptions of the problem, which can slow down fault handling.

Protect customer communication

If your main number uses internet-based calling, arrange a temporary route for urgent calls where possible. This could be a mobile number, call diversion already configured with your communications provider, or a pre-agreed message on your website and social channels. The right option depends on the nature of the business. A garage with customers booking repairs needs a clear alternative contact method; a charity may need to prioritise a helpline or donor enquiries.

Be honest but measured. Tell customers there is a temporary technical issue and offer the next practical step. Avoid promising a restoration time until the supplier or IT team has confirmed one.

Keep the business working safely

Connectivity failures put pressure on teams to find workarounds. Some are sensible. Others can create security, compliance and data-loss problems that last longer than the outage itself.

Where staff can work from approved mobile devices or company-managed laptops using mobile data, prioritise essential tasks. Focus first on customer-facing work, payroll deadlines, scheduled appointments, dispatches and time-sensitive supplier activity. Lower-priority work can wait.

Do not ask staff to send sensitive files through personal email accounts, share passwords over messaging apps or use unapproved file-sharing services. A rushed workaround can expose customer information and leave the business unable to prove where documents have been stored.

If your business has a second connection, such as a 4G or 5G failover service, check whether it has activated correctly. Failover is valuable, but it is not always identical to the primary service. It may have less capacity, so large downloads, video meetings and automatic cloud backups may need to be paused while essential operations take priority.

Check whether the fault is internal or external

Your IT provider can perform deeper checks, but a few observations help establish the next action. If the router shows no internet connection and neighbouring businesses have the same issue, contact the internet service provider and request a fault reference. If the internet connection appears live but staff cannot reach internal systems, a firewall, switch, Wi-Fi access point or DNS setting may be the cause.

Cloud services require a separate check. A working broadband connection does not guarantee that every application is available. If Microsoft 365, a line-of-business system or a hosted phone platform is having its own outage, check the provider’s status information through an available mobile connection and report the impact to users.

Do not factory-reset routers, firewalls or phone equipment unless your IT support team instructs you to do so. It can remove settings needed for internet access, security and calls, turning a provider outage into a longer recovery job.

Escalate with the information suppliers need

When contacting IT support or your connectivity provider, give a concise incident report: when the issue began, the affected sites and services, what has been tested, whether power is available, and whether the fault affects wired and wireless devices. Include the broadband circuit reference if you have it.

Ask for a ticket or fault reference number, the current diagnosis and the next update time. If the issue is affecting customers or trading, make this clear. A supplier cannot always restore a fault immediately, particularly where physical line work is needed, but they should provide a clear escalation path.

For businesses with several technology suppliers, it is easy to be passed between the broadband provider, phone supplier, cloud provider and IT company. This is one reason a single accountable IT partner is useful. My Tech Team can coordinate the technical checks, speak to relevant suppliers and keep the business updated in plain English.

After service returns, do not just move on

Restored connectivity is the start of recovery, not necessarily the end of the incident. Check that phones can make inbound and outbound calls, cloud files are syncing, card terminals are processing payments and staff can access the applications they need. Pay particular attention to systems that may not reconnect automatically after a fault.

Review any work completed offline. Make sure customer notes, job records, orders and financial information have been entered into the correct business systems once access is available. Watch for duplicate orders, missed emails, delayed bookings or messages left on diverted numbers.

Then hold a short review while the details are fresh. Consider how long the outage lasted, what it cost in lost time or revenue, whether staff knew what to do and where communication broke down. The answer may be a simple update to contact details, a documented call-diversion process or a better-labelled power supply. For some businesses, it may justify a backup internet connection, improved Wi-Fi coverage or a more resilient phone setup.

Make the checklist part of business continuity

Print the essential steps and keep them somewhere staff can reach without internet access. Include key supplier numbers, account references, router locations, the person authorised to approve emergency spending and the process for customer updates. Review it after office moves, staff changes and any major technology change.

An outage checklist cannot prevent every fault. It can stop a technical problem becoming a day of uncertainty, poor communication and unsafe shortcuts. With a tested plan and the right support behind it, your team can stay focused on customers while the technology is put right.