Customer Stories

Customer Stories

How Lumenpay rebuilt support around resolution, not deflection

How Lumenpay rebuilt support around resolution, not deflection

Lumenpay replaced a deflection chatbot with an agent that issues refunds and closes tickets. Their head of support explains what changed.

Lumenpay replaced a deflection chatbot with an agent that issues refunds and closes tickets. Their head of support explains what changed.

Portrait of Rhea Natarajan

Rhea Natarajan

6 min read

Abstract data illustration for “How Lumenpay rebuilt support around resolution, not deflection”

Daniel Okafor runs support at Lumenpay. Two years ago his team measured success by deflection. Today they measure resolution — and 68% of tickets are resolved without a human touching them.

Why deflection stopped working

Customers who needed something done still waited. The chatbot was good at answering questions and useless at refunds, card replacements and limit changes — the reasons most people write in.

Giving the agent real tools

Lumenpay gave its agent the same permissions as a week-two hire and the same policy document. Every action writes an internal note with a trace link, so the team can see what happened when a customer follows up.

The question used to be ‘did the bot answer?’ Now it’s ‘did the customer get what they needed?’

Read the full case study for the rollout plan and the numbers.

Portrait of Rhea Natarajan

WRITTEN BY

Rhea Natarajan

Head of Agent Operations

Rhea leads the team that helps customers move agents from shadow mode to full autonomy. Before Cairn she managed a 200-person support org.

Field notes

One email a month. Only the useful parts.

Lessons from running agents in production, new templates and the releases worth knowing about. Unsubscribe in one click.

Create a free website with Framer, the website builder loved by startups, designers and agencies.