Skip to content
E-commerce · 2024

AI Customer Support Agent

An e-commerce operation was answering the same small set of questions hundreds of times a week — where is my order, what is the return window, does this ship to my pin code. Volume spiked unpredictably around campaigns, and the team was reactive rather than useful.

  • AI agents
  • Retrieval
  • Escalation rules

Seconds

First response time

60%

Routine tickets deflected

2024

Delivered

Automation

Discipline

The problem

What we walked into.

The same order questions answered manually, hundreds of times a week.

High-volume repetitive queries crowding out the complex ones that actually needed a person

First response times stretching during campaign peaks, exactly when they mattered most

An off-the-shelf chatbot trial that answered confidently and wrongly, which had damaged internal trust

Policy content scattered across several pages, some contradicting each other

The approach

How it was built.

01

Content curated before any model work

One authoritative source per topic, with outdated versions retired rather than left alongside. Contradictory documents produce contradictory answers, and this is where most of the accuracy came from.

02

Retrieval, chunked by meaning

Policies chunked so a clause is never split mid-sentence, each chunk carrying its source URL so answers can cite where they came from and be checked.

03

Read-only tools for live facts

Order status, stock and shipping come from narrow read-only function calls rather than the model's guess. Anything touching refunds was deliberately left out of scope until the correction rate proved itself.

04

Escalation carrying context

Low retrieval confidence, frustration signals, complaints and anything about money escalate to a human — with the transcript, what the agent found and what it was unsure about attached, so the person starts where the agent stopped.

05

Internal, then suggest-only, then live

The agent first answered the team's own questions, then drafted replies for human approval so the edit rate could be measured, and only went autonomous on the question types where corrections were already near zero.

The outcome

What changed.

Grounded AI agent resolving routine requests and escalating with context.

Around 60% of routine tickets resolved without a human

First response in seconds, holding through campaign peaks

Escalations arrive with transcript and context rather than as an empty ticket

Unanswered topics logged as a content backlog, so gaps get fixed rather than guessed at

Your process could be next.

Tell us where the manual work is and we will show you what removing it looks like — scope, sequence and what it costs, before you commit to anything.

Start a project