Severe Weather Outage Intake and Escalation Guide
Standardize frontline utility support response protocols during major grid interruptions.
Use this template when call centers face surging inquiry volumes during unexpected grid failures or extreme weather events. It equips customer care leads to deploy a tiered triage and messaging architecture rapidly.
Role: Senior Customer Support Operations Lead specializing in regulated power distribution utilities.
Context
- Utility Name: {{utility_provider}}
- Affected Region: {{service_territory}}
- Cause of Disruption: {{incident_type}}
- Customer Class: {{affected_customer_tier}}
- Inbound Call Surge: {{current_queue_volume}}
- Restoration Target: {{estimated_restoration_window}}
Task
Develop a comprehensive support triage framework for frontline utility agents to classify incoming outage calls, distribute verified restoration data, and route priority safety hazards during active grid disruptions.
Method
- Analyze the operational parameters from {{utility_provider}} across {{service_territory}} to determine incident severity.
- Establish an intake classification matrix distinguishing life-threatening hazards (e.g., downed lines) from standard power failure reports.
- Define specific verification questions agents must ask based on {{incident_type}} to isolate neighborhood-level versus home-specific meter faults.
- Design deflection and queue-management paths suited for {{current_queue_volume}} to relieve agent capacity.
- Draft standardized, empathetic status messaging incorporating {{estimated_restoration_window}} tailored for {{affected_customer_tier}}.
- Detail an internal dispatch handoff protocol to bridge frontline support tickets with field crew repair dispatchers.
- Formulate a post-outage confirmation workflow to close open customer tickets once grid telemetry confirms power restoration.
Constraints
- MUST prioritize life safety and physical hazard reporting above average handle time metrics.
- MUST NOT provide speculative restoration timelines beyond the confirmed {{estimated_restoration_window}}.
- Language must remain calm, direct, and free of overly technical engineering jargon.
- Protocol must be actionable for tier-1 agents within three minutes of call intake.
Output format
Provide the framework structured in 4 mandatory sections:
- Hazard & Priority Intake Matrix (table mapping call type, risk level, and agent action)
- Frontline Scripting & Verification Flow (step-by-step conversational script)
- Field Dispatch Handoff Protocol (bulleted data transfer checklist)
- Queue Deflection & Self-Service Playbook (maximum 300 words)
Self-review
- Are all 6 contextual inputs referenced and addressed within the triage paths?
- Is there an unmistakable safety escalation procedure for downed lines or gas smells?
- Does the framework explicitly avoid unconfirmed restoration commitments?
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.