Learning centre

Design the workflow. Keep control of the operation.

Practical patterns for teams mapping energy processes into connected, observable AI execution—without hiding the systems or decisions involved.

See practical examples

Workflow design method

01

Map the real process

02

Define data and permissions

03

Set human decision points

04

Test failures and outcomes

01 · Guide

Map a billing-dispute workflow.

Start with the customer's words, identify the account and usage context required, then define correction and escalation paths.

Example configuration

Document what can be resolved automatically, what requires a billing specialist and what must always be explained to the customer.

  • Trigger and identity checks
  • Required account context
  • Exception categories
  • Customer communication path

02 · Guide

Design meter-reading validation.

Separate normal readings, missing context and genuine anomalies before assigning any downstream action.

Example configuration

Use deterministic checks where possible, agent reasoning where useful and a person for exceptions that affect billing or safety.

  • Validation boundaries
  • Anomaly routing
  • Evidence captured
  • Manual review path

03 · Playbook

Build a governed voice operation.

Define what the voice agent may discuss, which systems it may read or update and when the call must move to a person.

Example configuration

For a tariff conversation, constrain the agent to approved offers and make consent, identity and exception requirements explicit.

  • Identity and consent steps
  • Approved claims and offers
  • Tool permissions
  • Warm-transfer rules

04 · Concept

Agents inside workflows.

Use an agent for interpretation and bounded decisions, not as a replacement for every deterministic rule.

Example configuration

The agent can understand a free-form billing complaint; fixed rules should still decide whether a financial adjustment requires approval.

  • Reasoning versus rules
  • Bounded tool access
  • Structured outputs
  • Verified next action

05 · Guide

Connect systems safely.

Authorize accounts through the provider, select the minimum access required and keep each workflow step attributable.

Example configuration

A communication step may use the service inbox while the account lookup step uses CRM—each with its own permission and audit trail.

  • Account-level authorization
  • Least necessary access
  • Separate connections
  • Revocation plan

06 · Checklist

Prepare a process for production.

Test the happy path, missing data, provider failure, policy exception and human handoff before increasing volume.

Example configuration

Review run history with the people who own the process, then expand only after outcomes and failure paths are understood.

  • Success criteria
  • Failure simulation
  • Owner and escalation
  • Observed rollout

Explore the operating model.

Start with one process and define the systems and controls it needs.

Open workspace