Choose which optional cookies we can use. You can change your mind at any time from "Cookie settings" at the foot of every page.

Illustrative scenario

A retailer swamped by repetitive customer enquiries

  • Retail and e-commerce
  • Customer comms

Overview

How we'd approach customer communications for a small retail or e-commerce business answering the same questions all day.

The situation

The pain point Answering the same questions takes most of one person's day, and replies slow down at busy times.

A small online and high-street retailer answers a steady stream of "where's my order", "do you have this in stock" and returns questions across email and social media. The same answers get written again and again.

Diagram: the same questions about orders, stock and returns pile up by email and social media on one person, who writes the same answers from scratch most of the day. At busy times, replies slow down.

Where AI could help

The realistic opportunity is customer comms: drafting accurate replies to common enquiries from the retailer's own order and product data, for a person to approve and send. The aim is to take the repetitive load off, not to put a chatbot between the business and its customers.

Diagram: a customer question, with the order and product data, feeds an AI that drafts an accurate reply. A person checks the draft, then approves and sends it, with no chatbot between the business and its customers. Some questions stay with a person.

How we'd approach it

  1. Intake. Which enquiries actually repeat, and what data a good answer needs.
  2. Opportunity scoring. We'd separate the questions that really do repeat from the ones that need a person, because not everything should be automated.
  3. Proof of concept. We'd build a working demo that drafts replies to a set of the retailer's real, anonymised enquiries, so they can judge tone and accuracy before any build.
  4. Report. Where it's safe to assist, where a person must stay in the loop, and the running cost.
  5. Build or handover. We build it, or hand a clear brief to their own team or supplier, including how to keep the customer's experience personal.
Diagram: five steps, from intake and scoring what should stay with a person to a proof of concept drafting replies to real enquiries before any build, then a report on where a person stays in the loop, and build or handover.

What success would look like

In the proof of concept we'd measure how many enquiries get an accurate first-draft reply, the time saved per day, and response times at peak. Whether it's worth it depends on those numbers for this business, which is exactly what the proof of concept is for.

Diagram: three things measured today and in the proof of concept: enquiries with an accurate first draft, time saved per day, and response times at peak. Whether it's worth it depends on those numbers.

See it on your own data

Every business is different, so the proof of concept is where we find out whether this works for yours.