Grid Outage Support Volume Diagnostic
Evaluate customer support ticket spikes and response bottlenecks during severe utility outage events.
Deploy this template after major storm or grid failure events to analyze support surge patterns. It identifies communication delays, queue overload points, and self-service deflection weaknesses.
Role: Outage Communications and Support Operations Lead specializing in emergency grid disruption and customer care response.
Context
- Utility enterprise: {{utility_name}}
- Disruption trigger: {{outage_event_type}}
- Geographic territory: {{affected_region}}
- Channel volume metrics: {{support_channel_metrics}}
- Baseline first-response time: {{first_response_time_baseline}}
- Inbound sentiment transcripts: {{customer_sentiment_notes}}
Task
Produce a post-incident support volume diagnostic evaluating channel deflection, ticket spikes, and customer communication efficacy for {{utility_name}} during the {{outage_event_type}} in {{affected_region}}.
Method
- Plot the inbound ticket and call surge curve against physical restoration milestones across {{affected_region}}.
- Compare actual queue wait times against {{first_response_time_baseline}} across phone, chat, and mobile portal channels.
- Analyze {{customer_sentiment_notes}} to extract top customer distress triggers and safety-related escalations.
- Evaluate self-service deflection performance using the data in {{support_channel_metrics}}.
- Identify operational friction points between field dispatch status updates and live agent visibility.
- Isolate the specific outage phases where agent overload caused dropped calls or delayed status updates.
- Formulate high-impact communication updates to reduce repeat call volume during future major grid incidents.
Constraints
- MUST separate voice channel performance from digital self-service portal metrics.
- MUST NOT blame agent handling speed for volume surges driven by delayed restoration estimates.
- Ground all diagnostic statements in {{support_channel_metrics}} and {{customer_sentiment_notes}}.
- Maintain a constructive, operations-focused perspective.
Output format
- Incident Volume Timeline: Summary of surge peaks versus field restoration progress (max 120 words)
- Omni-Channel Performance Scorecard: Formatted comparison of handle times, abandon rates, and deflection percentages
- Escalation & Sentiment Analysis: Three detailed bullet points outlining primary customer friction drivers
- Actionable Protocol Upgrades: Four concrete changes to outage communication and support queue routing
Self-review
- Ensure the baseline metric {{first_response_time_baseline}} is explicitly used to measure performance degradation.
- Check that the analysis accounts for geographic nuances specific to {{affected_region}}.
- Confirm recommendations offer tangible guidance for customer support dispatch integration.
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.