Electric and gas utilities face outage events that demand rapid, accurate public communication across SMS, outage maps, social media, IVR, and press channels. Operations tracks crew dispatch and estimated time of restoration while communications staff translates technical status into customer language. Conflicting ETAs or premature all-clear messages draw regulator attention and erode public trust during storms and equipment failures.
An ai workflow utility outage communications assigns incident severity tiers and channels, pulls crew status and ETR feeds automatically, drafts SMS web and social updates, requires joint operations and communications approval before publish, and produces post-incident summaries for regulators. AI accelerates drafting; control center and comms leads confirm facts. Utilities often automate feed parsing with AI code tooling and prepare IVR scripts with AI voice assistants after human approval of wording.
Incident Severity Tiers and Channels
Define severity tiers that map to communication channels, update frequency, and approval depth before any AI draft generates. Tier 1 events may affect life safety or critical infrastructure; tier 3 may be localized single-circuit outages. Channel mix includes SMS, mobile push, outage map banners, X posts, Facebook updates, local media holds, and regulator notification templates.
| Tier | Typical scope | Primary channels |
|---|---|---|
| Tier 1 critical | Wide area, hospitals, life safety | SMS, map, social, media, regulator |
| Tier 2 major | Thousands of customers, multi-hour ETR | SMS, map, social |
| Tier 3 localized | Neighborhood or single feeder | Map, optional SMS subset |
Life Safety Overrides
Life safety messaging uses pre-approved templates that bypass creative AI variation for heat, cold, medical device, and downed line warnings. Operations triggers these templates through controlled codes; comms approves release but does not rewrite core safety language without legal review.
Pull Crew Status and ETR Feeds
Integrate outage management system, ADMS or SCADA-derived ETR, and crew dispatch status into a staging feed AI drafts reference with incident ID, customers affected, cause category, crew assigned, and ETR timestamp. Stale ETR is the primary source of public anger; display feed freshness in approver dashboards. Parsing scripts maintained with code AI should alert when feeds lag beyond configured minutes during active tier 1 events.
- Ingest ETR changes as discrete events, not overwritten silent updates.
- Include crew status: en route, on site, repair in progress, restoration pending patrol.
- Map cause codes to customer-safe descriptions approved by comms and legal.
- Exclude personally identifiable crew detail from public drafts.
- Log feed version on every published message for post-incident review.
Draft SMS, Web, and Social Updates
AI drafts channel-specific messages from the same confirmed fact bundle: SMS within character limits, map banner headlines, and social posts with accessible language and link to outage map. Each draft states affected area at appropriate granularity, current status, ETR with uncertainty when confidence is low, and safety reminders where tier rules require them.
- SMS: lead with action or ETR, include map short link, avoid jargon.
- Web map banner: sync text with map polygon labels customers recognize.
- Social: plain language, no emoji during tier 1 unless brand guide allows.
- Multilingual: queue parallel drafts for languages your comms team certifies.
- Misinformation response: pre-approved correction snippets when false claims trend.
Voice and IVR Alignment
After written messages approve, generate IVR script variants for call center and voice AI systems using identical ETR and area facts. Voice channels must not announce restoration before operations confirms patrol completion. Record script version IDs tied to the same incident event log as SMS sends.
Joint Ops and Comms Approval
Publish no customer-facing outage update until operations and communications approvers both confirm facts, ETR, tier classification, and channel selection on a shared incident record. Dual approval prevents optimistic ETAs from comms-only drafts and prevents opaque ops jargon from reaching the public without translation.
- Ops confirms crew status and ETR against OMS screen at approval time.
- Comms confirms tone, tier, languages, and regulatory notification triggers.
- Legal joins tier 1 drafts when injuries, fires, or investigations are active.
- Publish to channels simultaneously where policy requires parity.
- Issue correction workflow when ETR moves beyond public tolerance bands.
| Update type | Ops approver | Comms approver |
|---|---|---|
| Initial outage notice | Control center lead | Duty comms officer |
| ETR revision | Outage manager | Duty comms officer |
| Restoration all-clear | Patrol confirmation required | Duty comms officer |
Post-Incident Summary for Regulators
After restoration, AI assembles post-incident timelines from approved message logs, ETR change history, customer impact counts, and crew deployment summaries for regulatory filings and internal after-action review. Engineers and comms edit executive summaries; legal reviews before submission to state commissions or federal reporting portals when applicable.
Regulator summaries should cite message IDs and timestamps, not reconstructed memory. Include misinformation responses issued and multilingual reach metrics where commissions request equity documentation.
After-Action Learning
Compare predicted ETR accuracy to actual restoration at incident close and feed lessons into tier thresholds and template wording quarterly. AI draft edit rates signal where prompts need tighter fact binding to OMS fields rather than narrative flourish.
Governance and Tabletop Drills
Run quarterly tabletop exercises that walk joint approval workflows with simulated feed lag and ETR reversals so staff trust the process during real storms. Store drill outcomes separately from production incident logs. Enterprise AI with appropriate data handling should process outage counts; avoid public tools with unreleased critical infrastructure detail.
Media Relations and Vulnerable Customer Programs
Tier 1 events activate media holding statements drafted from the same OMS fact bundle as SMS, with comms and executive approval before reporters receive callbacks. Holding statements avoid speculative cause until operations confirms investigation stage appropriate for public release. AI drafts talking points; spokespeople deliver approved language only.
Critical Needs Registry Outreach
Customers on medical baseline or critical needs registries may require targeted outreach sequences beyond mass SMS when tier 1 outages hit their circuits. Workflow rules cross-reference registry IDs with outage polygons before sending specialized messages comms and customer advocacy teams approve. Registry messaging uses templates reviewed by accessibility and medical liaison staff annually.
Mutual Aid and Border Events
When mutual aid crews arrive from neighboring utilities, narratives should describe restoration progress without exposing crew home utility identities if security policy restricts that detail. ETR improvements after mutual aid dispatch should trigger update drafts only when operations confirms new crew assignments in OMS notes.
Outage Map and Mobile Push Parity
Outage map polygons, mobile app push notifications, and SMS must refresh from the same approved message bundle during active incidents so customers who check multiple channels see aligned ETAs. Map UX teams publish banner text only after comms approval records link to incident IDs. Push character limits follow SMS templates unless comms approves expanded app copy.
Map estimates sometimes lag OMS by minutes during storm scale; workflow dashboards show map sync age alongside OMS feed age so approvers delay publish until both systems align within tolerance or comms adds explicit map lag disclosure language legal approved.
Gas Versus Electric Workflow Branching
Gas odor and leak events use distinct template branches from electric outage tiers because life safety instructions and regulator notification windows differ. Do not route gas emergencies through electric outage prompts even when the same comms team publishes both. Branch selection should be a required field before AI drafts any text.
Storm Scale Throttling and Message Cadence
During widespread tier 1 events, throttle AI draft generation to approved cadence intervals so customers receive meaningful ETR changes rather than minute-by-minute noise that trains them to ignore alerts. Comms sets minimum minutes between SMS revisions unless ETR moves beyond a material threshold operations defines in advance.
Social channels may shift to hourly pinned updates while SMS carries material changes only; cadence rules should be documented in the incident record so post-event reviews evaluate whether throttling helped or hindered customer understanding.
Commission Reporting Hooks
Map incident tiers to regulatory notification timers your commission requires and surface countdown timers in approver dashboards during active events. Missed notification deadlines belong in post-incident summaries with corrective actions, not as hidden metadata. AI drafts commission cover letters from approved timeline exports legal reviews before filing.
Frequently Asked Questions
How do life safety messages differ from standard outage SMS?
Life safety templates use fixed wording approved by legal and emergency management, triggered only when tier 1 criteria met, and may omit ETR in favor of shelter and medical device guidance. AI should not paraphrase downed line or gas leak warnings. Operations owns trigger conditions; comms owns release timing within seconds of trigger.
How should utilities respond to social misinformation during outages?
Use pre-approved correction templates that restate verified facts and link to official map updates without engaging argument threads. Comms approves corrections with ops-confirmed data; do not debate speculative causes AI or staff cannot verify. Document corrections in incident logs for regulator review.
What multilingual standards apply to public updates?
Publish only languages your comms team certifies each storm season; machine translation may assist draft creation but human review must precede SMS send for tier 1 and tier 2 events. Track language coverage in post-incident reports when commissions measure equitable access.
How do you prevent premature restoration announcements?
Gate all-clear messages on patrol confirmation status fields operations sets, not on SCADA restoration alone when policy requires line patrol. Workflow software should block comms publish until patrol flag is true, even if AI drafts restoration text early.
Outage Communications That Match Field Reality
Utilities keep public trust during outages when severity tiers drive channels, crew and ETR feeds stay fresh, AI drafts align across SMS web and social, joint ops and comms approve every send, and regulator summaries reconstruct verified timelines. The workflow succeeds when customers receive accurate ETAs, not when post volume peaks.
