When the Line Goes Quiet: A Calm Outage Playbook for UK SMEs
Photo: Francisclarke, CC BY-SA 4.0, via Wikimedia Commons
A connectivity outage rarely arrives with drama. More often, the first sign is a quiet office: no incoming calls, a payment terminal that will not connect, or a colleague asking whether the internet is down for everyone. The temptation is to improvise. Someone reboots the router, someone else rings the provider, and a third person starts searching for emergency alternatives. None of that is wrong in itself, but without a simple plan the first two days become expensive and confusing.
For UK SMEs, the aim is not to eliminate outages. It is to contain them. A calm response protects customer service, keeps staff productive and gives the provider the information it needs to fix the fault. It also prevents panic buying that adds cost without solving the problem.
Name one owner before anything happens
The most useful preparation is also the least technical: decide who owns an incident. That person does not need to fix the fault. They need to coordinate the response, keep a log and make decisions. A deputy should be named for holidays and sick leave. A separate communications lead can handle staff and customer messages, while a technical liaison speaks to the provider.
This sounds bureaucratic for a small business, but it prevents the familiar scene in which five people ring the same supplier and receive five different answers. One owner, one log, one escalation path. The log should record times, symptoms, tests, ticket numbers, names and promised call-back times. It becomes the evidence base for the provider and for any later review.
The first hour: confirm, contain, communicate
Start by confirming the scope. Is it one desk, one office, one service or every site? Check whether power, cabling or a recent change is responsible. Do not reboot every piece of equipment in sequence; that destroys useful evidence. If the provider has a status page, check it. If the fault affects only your business, raise a ticket with the specific circuit or account reference.
Staff need a short instruction, not a technical briefing. Tell them what is affected, what to do instead and when the next update will come. Customer-facing teams need a holding message. For example: “We are aware of a telephone issue and are working with our provider. Please email us in the meantime.” The wording should be plain and honest. Avoid promising a fix time until the provider has given one.
Hours two to eight: escalate with evidence
When you contact the provider, be ready with the account number, circuit ID, site postcode, service affected, first symptom and tests already completed. Ask for the current service level agreement position and the next update time. If the fault is significant, ask whether it can be treated as a major incident. Keep to one ticket. Opening duplicate tickets usually slows resolution rather than speeding it up.
Record the name of each person you speak to and any reference they give. If a call-back is promised, diarise it. A polite follow-up at the agreed time is more effective than repeated calls every twenty minutes. Where the provider offers an escalation manager, use that route.
Day one: establish a rhythm
By the first day, the incident should have a rhythm. Send staff updates at fixed times, even if there is no change. Decide which workarounds are acceptable: mobile tethering for priority tasks, call diversion to a mobile, or a temporary reception arrangement. Protect the processes that matter most, such as incoming sales enquiries, payments, dispatch or customer support.
Be careful with workarounds that create new risks. A mobile hotspot may be fine for email but unsuitable for a cloud accounting system. Diverting calls to one person’s mobile may overload them. The incident owner should approve workarounds rather than letting each team invent its own.
Day two: decide what not to buy
The second day is when panic purchasing often begins. Suppliers may offer emergency 4G routers, replacement phone systems or accelerated fibre installations. Some of these may be sensible. Many are not, at least not until the cause is clear.
Avoid committing to a long contract for a temporary fix. Avoid buying failover equipment that has not been tested with your firewall, phone system or payment terminals. Avoid replacing hardware before the provider has confirmed whether the fault sits in your equipment, the local network or the wider network. Avoid cancelling an existing service in frustration before a replacement is live.
If you do buy, favour short-term, returnable or already-compatible options. Ask how the purchase will be supported and how it will be removed once normal service resumes. The goal is continuity, not a permanent change made under pressure.
Close the loop
When service returns, do not simply move on. Confirm that all services are working, including inbound calls, outbound calls, card payments and remote access. Update the log with the cause and the resolution. Hold a short review: what worked, what wasted time and what should be changed in the plan.
A good outage plan is short enough to use. It names an owner, gives staff a script, keeps escalation disciplined and prevents rushed purchases. For a UK SME, that is usually enough to turn a disruptive day into a managed one.
