Case StudyAustralia · Energy SaaSAgentic AI · Agent Workspace

Agentic Customer Care —
Glass × Adora AI

Molly Group grew through acquisitions — billing, CRM and digital products, each built by a different team. We shaped Molly Glass into one centralised customer-care workspace, orchestrated in layers, and brought in Adora, an AI that listens to every call and points agents straight to the answer — progressively reducing their cognitive load.

UX Designer · Individual ContributorPartnered with Josh (UX Designer)Nov 2025 – Jan 2026India ⇄ Australia, remote
~0s

AI-Assisted Resolution

Down from up to 15 min

0%

Actions in 1–2 Clicks

Front-office tasks

0/5

Operator Rating

Lowest score 4/5

0

Checks Re-distributed

High-bill work instruction

Outcome figures as reported by Molly leadership and operator feedback during the Glass rollout.

Adora AI

It Listens to Every Call —
And Takes the Agent Straight to the Answer

The moment an agent picks up, Adora starts listening. It picks out keywords from the conversation, turns them into insight cards, and each card deep-links into the exact part of Glass — billing, usage or customer insights — so the agent never has to go looking.

Molly Glass · Customer profile

Live call

Adora listening

Adora

Tap an insight
Waiting for keywords from the conversation…
BillingUsageCustomer insights

Bill compare

Dec · Estimated

$192.40

Mar · Actual

$347.18

Billing period91 days
Rate changeNone this cycle
Other chargesNo fees

Illustrative re-creation of the interaction model — data mirrors the Glass v2 concept screens.

Listen

Voice-to-text from the moment the call connects.

Detect

Trigger words like “high bill”, “estimated”, “concession”.

Explain

Insight cards with the data point behind the cause.

Navigate

One tap opens the right section inside Glass.

The Ecosystem

Many Acquisitions, Many Systems —
One Platform, Orchestrated in Layers

Molly Billing, Molly Acquire, Molly Customer and Molly Digital each arrived with their own stack, brand colour and patterns. Rather than replace them, the strategy was to orchestrate them: systems of record at the bottom, shared services in the middle, Glass as the single workspace — and Adora as the intelligence on top.

Molly Billing

Multi-utility billing

Molly Acquire

Sales & onboarding

Molly Customer

Front & back office CX

Molly Digital

Self-service & insights

Each acquisition keeps its own platform. They stay the source of truth for accounts, invoices and usage — we orchestrate them rather than replace them.

Exposes account, billing and usage data to shared services

  • Molly CIS · Core
  • Orion · Engage · EOS
  • Genesys telephony
  • Client payment portals

Layers build bottom-up: each one feeds the next

The Challenge · Existing Pain Points

Agents Had All the Data —
Just Not the Right Data at the Right Time

“Systems have all the things, it's just not user friendly.” Generalist agents were juggling telephony, multiple CRMs and payment portals mid-call — with 500+ work instructions to remember and a customer waiting on the line.

Through Sam's eyes

Before Glass + Adora

One high-bill call, start to finish

Ready for calls
Tabs open · 0None yet — the call hasn't started
Intro 1/3 · Meet Sam

Meet Sam, a customer-care agent

Follow one real high-bill call, before Glass + Adora existed.

1 / 15
01

Fragmented Toolset

Genesys for calls, Core, Orion and Engage for customer data, client payment portals, and a separate tab just to check one-time passcodes before a call could progress.

4+ systems open per call
02

High Bills = Longest Calls

The most common and slowest enquiry. Agents had to cross-check the usage tab, every previous invoice and payment history — data that was "not UX friendly at all".

Up to 15 min to resolve unassisted
03

Critical Flags Hidden

Hardship, life support, family-violence PINs and active complaints were not surfaced up front — risking the wrong conversation with a vulnerable customer.

Compliance & duty-of-care risk
04

Generalists, Specialist Work

Agents are generalists, yet concessions, estimated reads and stepped tariffs need deep knowledge. Heavy training was required, and much functionality went unused.

500+ work instructions
05

After-Call Work

Notes lived in notepads or inconsistent tools. When a call ended, agents navigated around again to reconstruct what happened — then wrote the summary.

Time lost after every call
Impact

The Real Cost

Retailers take ~3 years to make a customer profitable. Every extra minute on the phone and every avoidable escalation erodes cost-to-serve — the metric Molly sells on.

Cost-to-serve is the product

Cognitive load — one high-bill call

Before — agent searches

1Answer call, ask reasonGenesys
2Search customer by name / mobileCRM
3Verify 3 points of ID + OTPNew tab
4Open usage tab, decode raw dataCore
5Compare previous invoices one by oneBilling
6Check concessions & payment historyPortal
7Write notes after the call endsNotepad

After — Glass + Adora bring it to the agent

1Glass pops the verified customer on answerGlass
2Risk pills visible before first wordGlass
3Adora hears "high bill" and "estimated"Adora
4Insight cards explain the likely causeAdora
5One tap deep-links to Bill compareGlass
6Quick action: payment plan / meter reviewGlass
7Call summary drafted automaticallyAdora

Discovery & Research

From the CTO to the Call Floor —
Aligning Vision With Reality

We ran structured interviews top-to-bottom: leadership for the north star, product and engineering for constraints, and the operations team for what actually happens on a call. Every conversation was synthesised into pain points and opportunity areas on a shared board.

CTO

North star, agentic AI vision, cost-to-serve

Product Manager — Glass

Reasons for calls, customer lifecycle, Adora role

Tech Lead & Design Lead

Token pipeline, React migration, design foundations

CS Team Lead + Agents

Day-to-day workflow, beta feedback, quick wins

Personas

Four lenses on one problem

Synthesised from the interviews above. Names and portraits are illustrative.

The Visionary

Daniel

Chief Technology Officer

  • Owns the platform north star
  • Accountable for cost-to-serve
  • Final design sign-off

Keep the cognitive load simple. Make it intuitive, with less training needed.

Goals

  • Make Glass the market-leading agent experience
  • True agentic AI with Adora in the front office
  • One tech stack and shared foundations

Frustrations

  • Tech debt from legacy stored procedures
  • Every acquired product looks and works differently
  • Screens still feel busy despite quick actions

Needs from Glass + Adora

  • A consistent design language across all products
  • Adora doing more of the work, safely
  • Faster agent onboarding

How they shaped the design

  • Four-layer orchestration model
  • Agentic Adora concept (V3)
  • “One foundation” principle

Success looks like: Resolution time and cost-to-serve

Keep the cognitive load simple. Make it intuitive, with less training needed.

— CTO

The biggest impact will be Adora — minimising agents’ talk time and looking for information.

— CS Team Lead

Use Glass to expedite, then use Adora to get the next best action.

— Product Manager

Synthesis — pain point to opportunity

Usage tab brings up raw dataVisual usage trends + "top 3 explainers" on high-bill calls
Payments and usage live in separate placesBring payments and usage together in one billing view
Agents prep across many tabsAuto-surfaced "agent prep snapshot" when the call starts
Vulnerability flags easy to missCritical info pills up front, before the conversation
500+ work instructionsAdora condenses instructions into bite-sized, in-context steps
Too much functionality, heavy trainingRole-based IA and progressive disclosure for generalists

Engagement plan

Holiday break
Kick-off & AuditCurrent-state audit
ResearchNorth-star summary
Journeys & IARedefined IA
Concept testingValidated concepts
Build & handoverDev-ready components
NovDecJan

Information Architecture & Journey

Mapping the High-Bill Journey,
Then Redefining the IA Around It

We picked the hardest, most frequent scenario and mapped it end to end — then rebuilt the information architecture around it.

Scenario: High-bill enquiryMost frequentLongest to resolve

The old IA mirrored the systems.
The new IA mirrors how an agent thinks.

Organised by system

CoreOrionEngageUsage tabInvoicesPaymentsConcessionsNotesID / OTP

Agent stitches the story together, tab by tab.

Organised by the call

Who is calling?Profile
What do they have?Services
What helps right now?Adora

User flow — from ring to resolution

01Customer calls

Before

Agent answers with no context on screen.

Genesys

With Glass + Adora

Glass opens alongside the call, ready to go.

Glass

Left · Who

Customer profile

  • Verified identity & customer number
  • DOB, contact, PIN / password
  • Key dates: joined, last contact
  • Payer rating
  • Payment methods

Centre · What

Services by segment → drill into one

ResidentialSmall BusinessCommercial

Overview

Plan, best offer, billing, info pills

Bill information

Overview · Load disagg · Usage

Timeline

Interactions, tasks, payments, filters

Bill compare

Any two bills, drop-down detail

Right · Help

Adora rail

  • Live insights while call is active
  • Ask Adora — natural language
  • Control panel: tasks & new interaction
  • Cross-sell only when relevant

The 14-step high-bill checklist

Mapped from the agent work instruction, then redistributed between agent and Adora

1Estimated reads
2Billing period length
3Other charges & discounts
4Rate increase
5Rebates & concessions
6Average daily consumption
7Weather impact
8Peak / off-peak meter spikes
9Changes in the home
10New appliances
11Customer self-read
12Appliance maintenance
13Verify meter data (VMD)
14Energy-saving tips
Adora surfaces the data point· 8Adora suggests the question· 4Agent-led, needs approval· 2

The Solution

Progressive, Not Big-Bang —
Evolving Glass Towards Agentic AI

Glass was already live with operators, so we couldn't start from zero. We evolved it in steps — each release reducing what the agent has to find, and increasing what Adora brings to them.

Everything on one screen — and that was the problem

Glass already aggregated the account, but profile, services, bill PDF, charts and cross-sell all competed at the same visual weight. Agents said quick actions helped, yet the screen was "still very busy" — and Adora was hidden behind a tab.

  • Adora buried behind a right-panel tab
  • Bill PDF and charts crowd the overview
  • Vulnerability flags easy to miss
V1 · Glass today

V1 · Glass today

Figma design · customer data is fictional

Progressive disclosure

Snapshot first — 9 of 10 enquiries should be solvable from the overview; detail on demand.

Right info, right time

Call state and keywords decide what surfaces — not a fixed dashboard.

Widgets that grow

Components start as small insights and expand as the agent moves down the funnel.

Role-based IA

Permissions hide what an agent can’t act on, reducing noise and escalations.

Human in the loop

Adora advises, the agent decides. Feedback on every card; clear “can make mistakes” cue.

One foundation

Shared tokens, type scale and light/dark themes so every Molly product can inherit Glass.

Impact

Less Searching, More Solving —
For Agents and the Business

Glass rolled out to a first wave of 50 operators, with Adora layered on top. Operators said it was the first time something had been built for them.

Resolution time — complex enquiry

Without assistanceUp to 15 min
Glass + Adora~25 sec

As reported by Molly's CTO for Adora-assisted resolution.

80%

Front-office actions

Completed in 1–2 clicks

4.5/5

Operator rating

Lowest score 4/5

50

Operators

First rollout wave

1

Shared foundation

Tokens & components for all products

Reflection

Designing for AI Means Designing Trust

The hardest part wasn't the UI — it was deciding what Adora should do versus what the agent must own. Splitting the 14-step checklist into “Adora surfaces”, “Adora suggests” and “agent decides” gave the team a shared language for agentic features, and set the path for Adora to become the primary interface over time.

Stakeholder interviews

5+

Journey mapped end-to-end

High bill

Design iterations shown

3