General support
AuraScore 81/100

Grid Outage Customer Impact Support Report

Analyze support operations and communication efficacy during major power or gas distribution interruptions.

Use this template after severe weather events or equipment failures cause localized or regional utility outages. It structures a post-event support review evaluating ticket volumes, escalation bottlenecks, and customer communications.

Template

Role: Principal Customer Support Lead specializing in electrical grid resilience and utility communications.

Context

  • Operating Utility: {{utility_company}}
  • Impacted Service Territory: {{affected_region}}
  • Event Identifier: {{outage_event_name}}
  • Meter Count Offline: {{total_affected_accounts}}
  • Inbound Inquiry Metric: {{support_ticket_volume}}
  • Restoration Milestones: {{estimated_restoration_timeline}}

Task

Produce a customer operations incident report evaluating support channel performance, inquiry volume surges, and customer sentiment throughout the outage cycle to enhance future grid disruption workflows.

Method

  1. Map inbound customer contact velocity from {{support_ticket_volume}} against the actual restoration curve in {{estimated_restoration_timeline}}.
  2. Identify critical communication gaps between field dispatch updates and customer-facing notification systems across {{affected_region}}.
  3. Segment ticket trends to pinpoint primary driver categories such as medical priority accounts, commercial spoilage risks, or wire-down hazards.
  4. Evaluate compliance with regulatory customer communication standards for {{utility_company}} during {{outage_event_name}}.
  5. Assess frontline agent resolution performance handling the {{total_affected_accounts}} population.
  6. Formulate three systemic recommendations for interactive voice response and digital portal enhancements during surge events.

Constraints

  • MUST break down inquiry data into clear chronological phases: Initial Outage, Sustained Response, and Restoration.
  • MUST NOT speculate on engineering root causes outside the parameters of {{outage_event_name}}.
  • MUST identify at least one specific vulnerability affecting life-support or critical care accounts.
  • Maintain an objective, operational audit tone throughout the assessment.

Output format

Organize into three distinct sections:

  1. Incident Overview & Operational Metrics (summary table and concise text, max 150 words)
  2. Support Channel & Queue Analysis (bulleted evaluation of digital, voice, and field updates)
  3. Remediation Road Map (3-5 numbered strategic process fixes)

Self-review

  • Did I accurately connect {{support_ticket_volume}} patterns to {{estimated_restoration_timeline}} milestones?
  • Are life-support equipment considerations explicitly addressed for {{affected_region}}?
  • Are the remediation recommendations actionable for frontline contact center leadership?
AuraScore breakdown
81/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering10/12 · Adequate

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency7/10 · Adequate

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

support-success
support-general
energy-utilities
outage management
grid support
incident response