Severe Weather Outage Frontline Readiness Plan
Equip utility customer support teams to handle high-volume outage inquiries during extreme weather events.
Use this template when preparing frontline contact center and digital support teams for storm-driven grid disruptions. It delivers an operational readiness plan covering staffing surges, inquiry triage, and customer status messaging.
Role: Senior Utility Customer Operations Specialist with 15 years of grid emergency response experience
Context
- Utility provider: {{utility_name}}
- Incoming weather scenario: {{weather_event}}
- Impacted coverage area: {{affected_regions}}
- Total customer population: {{customer_base_size}}
- Active support channels: {{support_channel_mix}}
- Grid operations escalation trigger: {{escalation_threshold}}
Task
Develop a comprehensive support operations readiness plan that aligns frontline customer service agents across digital and voice channels to manage elevated inquiry volumes while maintaining accurate field restoration updates during {{weather_event}}.
Method
- Review the operational impact of {{weather_event}} across {{affected_regions}} against the {{customer_base_size}} account footprint.
- Establish channel-specific capacity allocations across {{support_channel_mix}} to absorb anticipated contact surges.
- Define call and ticket routing logic to separate life-safety hazard reports from standard power restoration inquiries.
- Script frontline macro responses and interactive voice response (IVR) messaging anchored on verified telemetry from {{utility_name}} dispatchers.
- Align agent escalation pathways with the established {{escalation_threshold}} to flag downed lines and critical care facilities directly to dispatch.
- Schedule tier-1 shift handover cadence and real-time briefing loops between grid control centers and customer support floor supervisors.
- Establish callback and proactive SMS update protocols to mitigate repeat contacts from customers waiting on restoration timelines.
Constraints
- MUST prioritize life-safety reports (downed wires, medical equipment dependencies) above general restoration inquiries.
- MUST NOT provide estimated times of restoration (ETR) unless verified by grid dispatch.
- All channel workflows MUST directly reflect the capabilities of {{support_channel_mix}}.
- Recommendations must fit a simple operational shift plan format.
Output format
Provide a structured plan with the following distinct sections:
- Operational Objective (under 80 words)
- Channel Allocation and Staffing Triage (table format)
- Critical Safety vs General Inquiry Workflows (step-by-step routing)
- Agent Communication Matrix (maximum 4 messaging scenarios)
- Supervision and Escalation Protocol (bulleted list)
Self-review
- Ensure life-safety routing is clearly differentiated from general outage reporting.
- Verify all variables including {{escalation_threshold}} are actively integrated into the workflows.
- Confirm no placeholder content or generic corporate boilerplate exists.
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.