General agents
AuraScore 81/100

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.

Template

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

  1. Establish the operational triggers that activate the agent upon declaration of {{outage_trigger_event}}.
  2. Define ingestion and reconciliation mechanics for raw field restoration estimates from {{dispatch_system_integration}}.
  3. Construct tone, clarity, and safety parameters tailored to distinct customer vulnerabilities across {{customer_segments}}.
  4. Design channel-specific message synthesis guidelines for {{primary_channels}} adhering to {{sla_target_minutes}} cadences.
  5. Establish automated validation checks that prevent hallucinated or unverified Estimated Time to Restoration (ETR) disclosures.
  6. Formulate fallback procedures for routing anomalous, emotionally distressed, or critical-care customer inquiries to human staff.
  7. 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:

  1. Incident Activation & Data Ingestion Flow (max 200 words)
  2. Customer Segmentation & Messaging Matrix (table covering each tier in {{customer_segments}})
  3. Guardrails, ETR Validation, & Human Escalations (5-7 clear numbered protocols)
  4. 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}}.
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 efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness5/5 · Strong

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

ai-agents
agents-general
energy-utilities
utilities
outage-response
agent-deployment