IBM Energy Australia

AGL Energy

Customer Service Automation

AGL needed to offer always-on digital support across web, account and mobile channels while reducing the load on frontline agents and enabling more transactions to be completed in self-service.

125,000 customers each month are starting a chat
36-38% of these chats are successfully serviced without requiring a frontline agent
4.5 million energy, telecommunications and Netflix customer services

Reported impact

Business outcome

AGL increased the share of customer interactions resolved in self-service, broadened the assistant from FAQs to transactions, and created a stronger 24x7 support option for millions of customers across multiple channels.

  • Customer Experience
  • Productivity Improvement
  • Scalability

Solution

AGL evolved its customer-support assistant into a multichannel self-service platform built on IBM watsonx Assistant. The team replaced an earlier bot with a new assistant that answers FAQs, personalizes interactions through APIs and serves different content depending on whether the customer is on the public website, authenticated account portal or mobile app. Over time the implementation expanded from simple question answering into transactional journeys that can complete actions, not just route them. Those journeys are integrated with the company's ERP software, and newer flows include validating concession cards with the issuing body in real time and writing the result back to CRM without agent intervention. With IBM and systems integrator ISW, AGL also modernized the experience through Watson Actions. The result is a customer-service layer that combines conversational support, API orchestration and enterprise-system integration to automate routine service requests at scale.

Data flow

Customer chats enter through AGL.com.au, My Account or the mobile app, watsonx Assistant calls APIs and ERP-connected workflows to personalize the interaction, and results such as validated concession-card updates are written back to CRM without agent handling.

Solution architecture

1 components · 1 layer
  1. Serving
    • IBM watsonx Assistant Powers the AGL Assistant across channels and executes both FAQ and transactional self-service journeys.

Architecture clues

  • AGL and ISW have moved parts of the experience to Watson Actions while preparing for future generative-AI enhancements.
  • Real-time validation with card issuers lets the assistant complete concession-card workflows end to end.
  • The assistant is channel-aware and serves different content depending on where the user starts the interaction.

Evidence from the source

36-38% of these chats are successfully serviced without requiring a frontline agent
The AGL Assistant provides customers with another option for 24/7 support
Today, 125,000 customers each month are starting a chat with the AGL Assistant
validate the card with the card issuer in real-time and add the card to the CRM without agent intervention
Transparency Evidence & methodology 90/100 reference value · 89% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value90/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact15/25
    1 metric describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence89%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    4 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. IBM

    AGL Energy customer story

    First-party
    https://www.ibm.com/case-studies/agl-energy
    Source type
    Vendor-published customer story
    Published
    Jan 10, 2025
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date

Date evidence

Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.