Network Outage Communication: Supporting Customers When Service Is Down
An outage has two durations. There is the engineering duration, measured from fault detection to service restoration, and there is the customer duration, measured from the moment they notice until the moment they understand what is happening. Network outage communication is the discipline that governs the second one, and it is the only one the contact centre can shorten.
The two are frequently confused in post-incident reviews. A provider that restored service in four hours and left customers uninformed for three of them has run a good engineering response and a poor customer one, and the complaint volume will reflect the second number.
- The fault sets the floor; the silence sets the damage
- In the UK, the customer’s report starts the compensation clock
- What network outage communication must contain
- The channel paradox, and the coverage problem
- The second wave most providers do not staff for
- FAQ: Network Outage Communication: Supporting Customers When Service Is Down
The fault sets the floor; the silence sets the damage
Delay research has been consistent on this point for three decades. The foundational study is Shirley Taylor’s examination of how delays affect service evaluations, published in the Journal of Marketing in 1994 and tested on delayed airline passengers. It found that delays damage evaluations of the service, but that the damage is mediated by the customer’s affective reaction — and that two factors move that reaction indirectly: how much control the customer believes the provider had over the delay, and whether the waiting time was filled.
Both are communication variables, not engineering ones. A customer told that a contractor severed a fibre route attributes less control to the provider than one told nothing. A customer given a restoration estimate has a filled wait; one refreshing a status page has an empty one.
In the UK, the customer’s report starts the compensation clock
There is a regulatory dimension here that rarely appears in incident planning, and it inverts the usual view of the contact centre as a cost during an outage.
Under Ofcom’s automatic compensation scheme, residential fixed broadband and landline customers of signed-up providers receive money back without having to claim it. Missed appointments and delayed starts are paid automatically. Loss of service is different: the customer must first report the fault to the provider. Where the service is not fully repaired after two full working days, compensation currently runs at £10.34 for each calendar day, with £32.31 for a missed engineer appointment.
The operational consequence is uncomfortable. A customer who cannot get through to report a fault is a customer whose entitlement has not started — which means an under-resourced queue produces a quieter compensation bill and a considerably angrier subscriber base. Any provider treating contact suppression as a saving during an outage should be clear that this is the trade it is making.
What network outage communication must contain
Most outage messaging answers the question the provider finds easiest rather than the one the customer is asking.
| What the customer wants to know | What providers typically say | Why the gap matters |
|---|---|---|
| Is it me or you? | “We are aware of an issue” | Until this is settled, the customer keeps troubleshooting their own equipment |
| Is my address affected? | A regional or national notice | A generic notice cannot be acted on |
| When will it be back? | “As soon as possible” | An unfilled wait is the worst-evaluated kind |
| What caused it? | Nothing | Attribution reduces perceived provider control |
| What am I owed? | Nothing until asked | Silence here converts an incident into a complaint |
| Do I need to do anything? | Nothing | The compensation clock may depend on the answer |
The first row is the most expensive omission. A customer who does not know whether the fault is theirs will restart the router, re-cable the socket, and eventually call — generating a contact that a single clear message would have prevented.
The channel paradox, and the coverage problem
Outage communication faces a constraint no other service scenario shares: the channel most providers prefer is the one the outage has disabled. App notifications, web chat and status pages all assume connectivity the affected customer may not have. SMS and voice survive a broadband failure; neither survives a mobile network failure.
The coverage problem is sharper still. Faults do not schedule themselves inside office hours, and contact volume arrives within minutes rather than building gradually. Distributed handover arrangements of the kind described in this analysis of follow the sun support models exist precisely for demand that does not respect a working day.
Because the surge is unpredictable, brief and large, holding the capacity permanently in-house is difficult to justify. It is more commonly contracted, with telecom bpo services partners engaged against an incident volume band rather than a fixed number of seats. What determines whether that works is not the headcount but the briefing: an external team without the incident detail and the compensation position will absorb contacts without resolving anything.
The second wave most providers do not staff for
Outages are followed by a predictable secondary problem. Customers who have just been told their service is faulty are unusually receptive to a caller claiming to be from their provider, offering to fix it or to process a refund.
This is the same tension examined in this piece on verifying customers without insulting them: the disruption that makes people call is the disruption that makes them least able to distinguish a genuine contact from a fraudulent one. Outage messaging that states plainly what the provider will never ask for costs nothing and belongs in the first notification, not the third.
FAQ: Network Outage Communication: Supporting Customers When Service Is Down
It is the set of messages a provider issues to affected customers during a service failure, covering scope, cause, expected restoration, required customer action and compensation position. It is distinct from incident management, which addresses the fault itself, and it is measured by how quickly customers understand their situation rather than by how quickly service returns.
On a published cadence, with an update issued whether or not there is progress to report. A stated interval — hourly, for example — converts an open-ended wait into a bounded one, and an update confirming that the previous estimate still holds is more useful than silence. Missing a promised update is worse than never promising one.
Only partly. Under Ofcom’s scheme, customers of participating providers must report a total loss of service to trigger compensation, which then applies where the fault is not repaired after two full working days. Missed appointments and delayed service starts are paid without any customer action. The scheme covers residential fixed broadband and landline products
Generally yes, at the level of what happened rather than who is at fault. Delay research indicates that customers who attribute less control to the provider react less negatively, and a factual cause — a cable strike, a power failure at an exchange — reduces the assumption of negligence that silence invites.
Yes, provided the partner receives the same incident information as internal staff and has a defined position on compensation. The common failure is engaging surge capacity as a queue-absorption measure without the briefing that lets agents resolve anything, which increases contact volume rather than reducing it, because unresolved callers call again
Offshore BPO analyst covering the UK, South Africa, and the Philippines. Writing on outsourcing strategy, compliance, and CX operations across all three markets — from British buyers to offshore operators.
