What problem does it solve?
When a network fails, every affected customer tries to find out what is going on at the same moment. Inbound calls spike, queues fill with people asking the same question, and customers with unrelated problems cannot get through. Agents can know little more than the customer when the network operations centre, field teams and the contact centre use different systems and update each other slowly.
An affected customer needs three answers: that the operator knows, why it happened and when it will be fixed. Telling them first can prevent some of these calls, but only if the operator can work out quickly which customers are affected, separate a local power cut from a network fault, and keep the estimate honest as the repair progresses.
How does it work?
- Group the alarms. Models correlate modem, cell and network alarms by location and time into one incident instead of thousands of individual alerts.
- Find the cause and the affected customers. The system estimates the likely cause (a fibre cut, a site failure, a commercial power outage) and the list of affected customers and services.
- Tell customers first. The agent drafts and sends proactive notices in each customer's channel and language, with the cause, what to do (for example contact the power company) and an estimated fix time, using approved message templates.
- Answer questions during the incident. Inbound calls and chats from affected customers are recognised at once and answered with the latest status, instead of joining the queue.
- Update and close. As field teams report progress, customers receive updates, and after restoration a closing message and any compensation that applies.
- Audience
- Customer facing
- Autonomy
- Supervised agent
- Adoption
- Emerging
- Channels
- SMS, Mobile app, Phone and voice, WhatsApp, Web chat, Email
What is it worth?
Benchmarks are computed from the public deployments below: one data point per organization per KPI, with who made each claim.
No public deployment has disclosed a measurable outcome yet.
Value drivers: Customer experience, Lower cost to serve, Speed and cycle time, Compliance quality.
Indicative value
An operator with 2 million fixed and mobile customers
USD 48,000 to USD 672,000
Outage call handling cost avoided per year
How this is calculated
Formula: customers * affectedShare * callsPerAffected * avoidedShare * costPerCall. The low scenario uses every low input, the high scenario every high input.
| Input | Low | High | Basis |
|---|---|---|---|
| Fixed and mobile customers customers, customers | 2,000,000 | 2,000,000 | The reference operator. |
| Share of customers affected by at least one notable outage per year affectedShare, fraction of customers | 0.2 | 0.4 | Editorial assumption, replace with your own incident history. |
| Outage related calls per affected customer callsPerAffected, calls per affected customer | 0.15 | 0.3 | Editorial assumption, replace with call volumes from past incidents. |
| Share of outage calls avoided or answered without a human avoidedShare, fraction of outage calls | 0.2 | 0.4 | Editorial assumption. No public benchmark for outage calls was found. Kore.ai reports about 40% call containment in the first month for a US telecom provider's voice self service as a whole, not for outage calls, so the range stays at or below that. Source |
| Cost of a human handled call costPerCall, USD per call | 4 | 7 | Editorial assumption, replace with your own fully loaded cost. |
What it leaves out: Counts only avoided call handling. It leaves out faster restoration from better diagnosis and dispatch, lower compensation and complaints, the value of keeping lines free for other customers during incidents, and the cost of the AI and network data integration.
Who already uses it?
1 public deployment, strongest evidence first. Grades: A regulator or audit, B the organization itself, C vendor case study, D anonymous or estimate.
Comcast
United States · Telecommunications · 2025
Comcast deployed a proprietary AI tool nationwide across its footprint after trials in the 2024 hurricane season. When many modems go offline it groups the individual alarms by location and time into one alert, then analyses device and network data to determine the cause, for example a commercial power outage. Comcast says this diagnosis lets it notify affected customers with recommendations such as contacting their local power provider, and that the tool streamlines the dispatch of technicians with the tools they need. Comcast does not say that the AI sends the notices itself or that customers hear before they call. Comcast says trials in the 2024 hurricane season raised storm recovery effectiveness by fifty percent in impacted regions.
No outcome disclosed.
How do you implement it?
A model agnostic playbook: what to prepare, the order to build in, and what goes wrong.
Data you need
- Network topology and inventory that map customers to cells, nodes and fibre routes
- Real time alarm and device status feeds
- Field service job status and estimated repair times
- Approved message templates per incident type and language
- Contact preferences and consent for service messages
Systems to integrate
- Network monitoring and alarm correlation
- Network inventory and customer to network mapping
- Field service management
- Messaging platforms (SMS, app push, WhatsApp, email)
- IVR and contact centre routing for inbound calls
Complexity: High
The conversation is the easy part. Linking network alarms to affected customers in minutes, and getting honest fix time estimates from field operations, needs integration across network management, inventory, field service and CRM, and a clear owner for every message sent.
- 1
Map customers to the network
Without a reliable link from customers to the network elements that serve them, every notice is a guess. Fix inventory and mapping first.
- 2
Agree who owns the message
Decide with network operations and communications who approves the cause, the estimate and the wording for each incident class, and which notices the agent may send on its own.
- 3
Start with inbound recognition
Recognising callers in an affected area and giving them the status is low risk and high value. Add proactive notices once the affected customer lists prove accurate.
- 4
Keep estimates honest
Take fix times from field service, give ranges rather than exact times and send an update whenever the estimate changes, even if it gets worse.
- 5
Rehearse major incidents
Test the whole chain on simulated large outages, including emergency call disruption, so messaging scales and escalation to crisis teams works.
Guardrails
- Proactive notices only from approved templates, with human approval for major incidents
- Estimates always come from field service data, never generated by the model
- Messages about disruption to emergency calling follow the crisis communication plan
- Vulnerable and priority customers, such as telecare users, get direct contact
- Service messages respect contact preferences and never include marketing
KPIs to instrument
- Time from first alarm to first customer notice
- Share of affected customers notified before they contacted the operator
- Inbound contacts per affected customer during incidents
- Accuracy of affected customer lists and fix time estimates
- Satisfaction and complaints after major incidents
Human in the loop
Network operations confirm the cause and scope of each incident, and communications or incident managers approve notices for major and sensitive outages. People handle priority customers and complaints, and review every major incident's customer communication afterwards.
Common failure modes
- Wrong customers notified
- Notices reach unaffected customers or miss affected ones. Validate customer to network mapping and measure list accuracy.
- Optimistic estimates
- A fix time that keeps slipping destroys trust. Use ranges from field data and update proactively.
- Silence during the big one
- Messaging fails under the load of a major outage. Load test and rehearse.
- Treating a power cut as a network fault
- Engineers are sent to working equipment. Detect power outages and tell customers what they can do.
What are the risks and rules?
EU AI Act
Depends on design
The customer facing agent is limited risk with an Article 50 duty to disclose AI. AI used as a safety component in the management and operation of critical digital infrastructure is high risk under Annex III point 2, so the classification depends on whether the detection part acts on the network or only informs people.
Rules that apply
Guidance
- Article 50, transparency obligations for providers and deployers of certain AI systems (European Union, Europe). People must be informed that they are interacting with an AI system unless this is obvious from the context.
- Investigation into Three following voice service outage on 25 June 2025 (Ofcom, Europe). Ofcom opened this investigation on 15 December 2025 after a UK wide voice outage that also disrupted calls to emergency services. It shows that sections 105A and 105C of the Communications Act 2003 require providers to prepare for and mitigate failures of network availability, which outage communication supports but does not replace.
- European Electronic Communications Code (Directive (EU) 2018/1972) (European Union, Europe). Sets the EU end user rules for electronic communications services, such as contract information and compensation. Its security articles 40 and 41 were deleted from 18 October 2024 and replaced by NIS2.
- NIS2 Directive, Article 23 (reporting obligations) (European Union, Europe). Where appropriate, essential and important entities, including providers of public electronic communications networks and services, must notify the recipients of their services without undue delay of significant incidents likely to affect those services.
Controls to put in place
- Documented message templates and approval rules per incident class
- Audit log of every notice, with the data it was based on
- Load tests and major incident rehearsals at least yearly
- Accuracy review of affected customer lists after each major incident
- Priority customer register kept current and used in every incident
Frequently asked questions
- Can AI tell customers about an outage before they call?
- Yes, if the operator can link alarms to customers. Comcast describes an AI tool, deployed nationwide, that groups modem alarms into one alert and identifies causes such as commercial power outages, so Comcast can notify affected customers with advice. Kore.ai says a large US telecom provider sends outbound outage SMS to reduce repeat calls. Published figures on calls avoided are still rare.
- Who should approve outage messages?
- Routine local notices can go out automatically from approved templates. Major incidents, especially those affecting emergency calls, need approval from incident or communications managers, because the message is part of the operator's regulatory response.
- How does this differ from AIOps incident triage?
- AIOps helps engineers find and fix the fault. Outage communication uses the same incident data to keep customers informed and to take pressure off the contact centre while the fix is under way.
How to cite this page
Blits.ai AI Use Case Library, "AI agent for network outage detection and customer communication", last verified 27 September 2026, https://www.blits.ai/ai-use-cases/network-outage-communication-agent. Licensed under CC BY 4.0. Method: how we verify use cases.
Changelog
- 27 September 2026: First published