Energy & Utilities

Customer Energy Advisor

Designed for Utility customer

Help a utility customer understand a surprising bill and act on it by explaining usage drivers, tariff mechanics, and eligible programs in plain language, with confirmation before any tariff switch or program enrollment.

Contract ENE-02 · primary aggregate CustomerEnergyAccount · mode loading

Decision brief

Confirm tariff switch or enrollment: evidence ready for review

This brief starts with the decision, evidence, and accountable owner. The guided workflow then shows how the recommendation was produced.

Decision signals

The evidence and control points that shape this recommendation.

Decision owner

Customer

The named role remains accountable for the consequential decision.

Governed evidence

5 record types

Structured records and cited text ground the recommendation.

Workflow

5 controlled stages

Each transition records its input, output, status, and audit context.

Human controls

1 approval gate

Approval gates prevent the copilot from making consequential decisions.

Business problem

A customer's bill rises 62 percent in August; the advisor attributes 38 percent to cooling degree days, 19 percent to a new on-peak window after a rate change, shows the three hottest afternoons that drove peak demand, and enrolls the customer in a smart-thermostat demand-response program after they confirm the terms..

Decision to make

Help a utility customer understand a surprising bill and act on it by explaining usage drivers, tariff mechanics, and eligible programs in plain language, with confirmation before any tariff switch or program enrollment.

Outcome to show

Submitted change request with confirmation record gives Customer the evidence needed to begin the final governed business outcome, with the decision trail retained for review.

  1. 1Ask why the bill changed
  2. 2Decompose the bill into drivers
  3. 3Explain tariff mechanics in plain language
  4. 4Match eligible programs and alternatives
  5. 5Confirm tariff switch or enrollment

Step 1 of 5

Ready: Start with the business question, then use the single button above.

The output appears here immediately. More technical evidence remains available below.

System logic, GenAI, and human accountability

The demonstration keeps deterministic controls, AI assistance, and approval separate.

System logic

Source systems enforce identity, workflow order, policy filters, and record updates.

GenAI contribution

Retrieval and generation assemble relevant evidence into a cited recommendation or draft.

Human accountability

Customer verifies material claims and approves the consequential action.

Workflow stages

Run the stages in order before using the Copilot. Every stage explains what happens, why it matters, the evidence it uses, and the complete API request and response.

Seeded record
Loading
Document type
Loading
Container
Loading
Partition key
Loading
Current stage
Loading

API demonstration guidance

Run a stage to see its explanation, evidence, full request, and full response.

Grounded chat

Ask a question and receive an answer grounded in retrieved CustomerEnergyAccount evidence.

Answer and evidence

Select a starter question or enter your own.

Evidence

Domain implementation workspace

Loaded live from /api/config, /api/domain/model, and /api/domain/sample.

Domain objective
Help a utility customer understand a surprising bill and act on it by explaining usage drivers, tariff mechanics, and eligible programs in plain language, with confirmation before any tariff switch or program enrollment.
Primary aggregate
CustomerEnergyAccount
Primary container
customerEnergyAccounts
Hierarchical key
/tenantId + /serviceAccountId
Schema version
1

Sample scenario

A customer's bill rises 62 percent in August; the advisor attributes 38 percent to cooling degree days, 19 percent to a new on-peak window after a rate change, shows the three hottest afternoons that drove peak demand, and enrolls the customer in a smart-thermostat demand-response program after they confirm the terms.

Physical Cosmos DB containers

Every container provisioned for this accelerator with its hierarchical partition key.
Container Role Hierarchical partition key Document types
customerEnergyAccounts Primary /tenantId + /serviceAccountId CustomerEnergyAccount, IntervalUsageSummary, BillStatement
tariffCatalog Reference /tenantId + /serviceClassCode TariffDefinition
efficiencyProgramCatalog Reference /tenantId + /programSegmentCode EfficiencyProgram

Document types

Contract document types, their owning container, and their identifier pattern.
Type Container Partition key Identifier pattern Embedding fields
CustomerEnergyAccount customerEnergyAccounts /tenantId + /serviceAccountId account::{serviceAccountId} None
IntervalUsageSummary customerEnergyAccounts /tenantId + /serviceAccountId usage::{serviceAccountId}::{summaryDate} None
BillStatement customerEnergyAccounts /tenantId + /serviceAccountId bill::{serviceAccountId}::{billPeriodEnd} None
TariffDefinition tariffCatalog /tenantId + /serviceClassCode tariff::{serviceClassCode}::{tariffCode}::{versionLabel} tariffSummaryVector
EfficiencyProgram efficiencyProgramCatalog /tenantId + /programSegmentCode program::{programSegmentCode}::{programId} programDescriptionVector

Query patterns