The email that eats a support team.

Every distributor has the same email, many times a day. A customer, or a retailer’s store, wants to know where an order is. Answering it is simple, and it takes most of a morning.

We spent three months inside the customer service operation of a distributor that sells consumer electronics and lifestyle brands into UK and Irish retail, before we built anything. Here is what that email actually costs, and what changed.

What one “simple” query involves

A query lands in the shared inbox. Someone reads it and works out what it is: a tracking question, an investigation into a lost parcel, a return or a refund. They find the order number, sometimes in the subject line, sometimes in a forwarded thread. They open the right carrier’s portal (DHL, Royal Mail, DPD or Parcel Force, each with its own format) and match the order by hand. Then they check the retailer’s return rules or the brand’s warranty terms, which live in someone’s head or an old email. Then they write a reply.

Multiply that by the season. At peak, volume rose three to four times. The team did not. Internal logistics messages sat in the same inbox, adding noise to the real queries.

Narrow on purpose

The client could have asked for a chatbot, or a platform. We agreed one scope, deliberately narrow: classify every customer email and draft the reply, for a person to approve. One workflow, done properly.

The system reads each email and filters out internal noise. It sorts the query into one of four types and pulls out the order number. It checks live tracking with the right carrier and looks up the policy that applies. Then it drafts a reply in the brand’s voice. A person on the team reviews it, edits it if needed, and sends it from Outlook, the same tool they always used.

What changed

Drafting got 98% faster: under 12 seconds to a draft reply. About 65% of queries were approved exactly as drafted; over one weekend, it was 9 of 14. The team now has 10 times the peak capacity it had, and 8 to 12 hours of capacity freed every week.

The number we like most is less obvious. Every edit the team makes to a draft teaches the system. In the first weeks, 47 corrections were applied. The drafts got better because the people using them kept correcting them, and that only happens when the system lives inside their real work.

Why it stuck

Three things made this a system the team kept using, rather than a pilot they tolerated:

• No new tool. The team works in Outlook. The dashboard is there when they want the whole picture, not as another inbox to check.
• Their data, their servers. Customer data could not sit on outside servers, so the system runs on the client’s own infrastructure.
• Weekly sessions from day one. The dashboard was rebuilt in the second month, on the team’s feedback.

What came next

Once one system worked, the conversation changed. The client’s Commercial Director came to a call with his own list of new use cases across three business units: briefings for field sales, search across systems, onboarding new brands, finding leads for the 3PL arm, and documenting procedures. A new brand can now be added to the knowledge base in 48 hours.

The support system turned out to be the foundation, not the destination. Every carrier complaint in support is also a delivery insight for sales.

Where to start

Count your “where is my order” emails for one week, and time ten of them. Then count how many carrier portals your team opens to answer them. If the answer is more than one, the first system is probably sitting in your inbox.