General marketing
AuraScore 81/100

Behavioral Demand Response Campaign Architecture Specification

Architect a trigger-based behavioral marketing specification to drive residential energy conservation during peak grid events.

Apply this specification when orchestrating multi-channel demand-reduction campaigns for extreme weather or supply scarcity scenarios. It aligns behavioral economics nudges, smart meter data triggers, and community equity protocols.

Template

Role: Lead Energy Customer Engagement Architect specializing in behavioral science and dynamic demand management.

Context

  • Regional Transmission Organization / Grid Operator: {{regional_grid_operator}}
  • Stress Scenario: {{seasonal_peak_scenario}}
  • Target Capacity Reduction: {{target_load_reduction_mw}}
  • AMI Metering Infrastructure: {{smart_meter_penetration_rate}}
  • Alert Escalation Tiers: {{communication_tier_triggers}}
  • Low-Income & Medically Vulnerable Protections: {{vulnerable_customer_safeguards}}

Task

Design an operational Behavioral Demand Response (BDR) Campaign Architecture Specification that mobilizes residential customers across {{regional_grid_operator}} territory to achieve {{target_load_reduction_mw}} during {{seasonal_peak_scenario}} without damaging customer satisfaction.

Method

  1. Define customer behavioral engagement personas based on {{smart_meter_penetration_rate}} capability and historical responsiveness.
  2. Map behavioral economic nudge techniques (social proof, loss aversion, civic duty) to each alert stage in {{communication_tier_triggers}}.
  3. Architect multi-channel event notification sequences across SMS, email, mobile push, and automated voice channels.
  4. Design mandatory exclusion algorithms and safety filters dictated by {{vulnerable_customer_safeguards}}.
  5. Establish Day-Ahead, Day-Of (T-4h, T-1h), and Post-Event feedback communication blueprints.
  6. Detail post-event 'thank you' and personalized energy conservation scorecards to cement habitual behavior.
  7. Formulate operational protocols for real-time message throttling during rapid grid emergency condition changes.
  8. Specify baseline measurement methodology to calculate customer load reduction against control groups.

Constraints

  • MUST enforce absolute exclusion rules for life-support and medically vulnerable accounts under {{vulnerable_customer_safeguards}}.
  • MUST NOT send unsegmented, broad-scale emergency alerts when targeted feeder-level notifications are feasible.
  • All SMS notifications must stay under 160 characters and provide instant, zero-penalty opt-out links.
  • Technical specifications must account for smart meter sync latency within {{smart_meter_penetration_rate}}.

Output format

Provide a technical campaign specification containing:

  1. Executive Architecture Overview (100-150 words)
  2. Alert Cadence & Channel Trigger Matrix (Trigger condition, Timing, Channel, Objective, Character limit)
  3. Behavioral Framing & Message Specimen Library (Pre-event, In-event, Post-event copy specs)
  4. Vulnerability & Safety Exclusion Protocol (Algorithmic filtering logic)
  5. Post-Event Feedback & Gamification Engine Specifications
  6. Impact Measurement & Verification Analytics Plan

Self-review

  • Ensure the sequence directly responds to the exact conditions described in {{seasonal_peak_scenario}}.
  • Confirm that medically vulnerable safeguards in {{vulnerable_customer_safeguards}} override all automated marketing triggers.
  • Validate that message copy formats fit strict character and channel delivery constraints.
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 engineering12/12 · Strong

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.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

marketing
marketing-general
energy-utilities
demand-response
behavioral-marketing
grid-operations