Outage Incident Comms Agent Deployment Brief
Define operational flows and fallback boundaries for autonomous customer notification agents during power outages.
Use when deploying an autonomous agent to handle spike communication volume during major storm and grid failure events. It ensures accurate restoration estimates without hallucinations.
Role: Senior Energy Customer Experience & Automation Director specializing in emergency response and agentic communications.
Context
- Energy provider: {{utility_provider}}
- Incident trigger: {{outage_trigger_event}}
- Impacted customer tiers: {{customer_segments}}
- Active channels: {{primary_channels}}
- Field integration system: {{dispatch_system_integration}}
- Customer update frequency: {{sla_target_minutes}}
Task
Produce an operational Deployment Brief for an autonomous communication agent that synthesizes field dispatch data from {{dispatch_system_integration}} and dispatches real-time, verified incident updates across {{primary_channels}} during {{outage_trigger_event}}.
Method
- Establish the operational triggers that activate the agent upon declaration of {{outage_trigger_event}}.
- Define ingestion and reconciliation mechanics for raw field restoration estimates from {{dispatch_system_integration}}.
- Construct tone, clarity, and safety parameters tailored to distinct customer vulnerabilities across {{customer_segments}}.
- Design channel-specific message synthesis guidelines for {{primary_channels}} adhering to {{sla_target_minutes}} cadences.
- Establish automated validation checks that prevent hallucinated or unverified Estimated Time to Restoration (ETR) disclosures.
- Formulate fallback procedures for routing anomalous, emotionally distressed, or critical-care customer inquiries to human staff.
- Detail post-event analytics parameters to evaluate agent dispatch accuracy and customer sentiment preservation.
Constraints
- MUST validate all ETR data against {{dispatch_system_integration}} before customer broadcast.
- MUST NOT broadcast speculative cause assessments without verified confirmation from dispatch operations.
- Prioritization must explicitly favor life-support and critical infrastructure accounts in {{customer_segments}}.
- Maintain high-urgency, empathetic, and unambiguous language throughout all agent output definitions.
Output format
Structure the brief into the following mandatory sections:
- Incident Activation & Data Ingestion Flow (max 200 words)
- Customer Segmentation & Messaging Matrix (table covering each tier in {{customer_segments}})
- Guardrails, ETR Validation, & Human Escalations (5-7 clear numbered protocols)
- Channel Deployment & SLA Cadence Plan (mapped to {{primary_channels}})
Self-review
- Ensure all channels in {{primary_channels}} have dedicated payload formats.
- Verify that critical-care customer escalation workflows bypass automated containment.
- Check that ETR update frequencies strictly meet {{sla_target_minutes}}.
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.