Case study · Distribution
Ten times the peak. The same small team.
Every customer email read, checked against the carriers and answered in a draft the team approves.
- Client
- JDM Products
- Sector
- Distribution, UK and Ireland
- Engagement
- AI system build
- Runs on
- JDM’s own infrastructure

Draft ready: tracking query
01
The situation.
JDM Products distributes consumer electronics and lifestyle brands into UK and Irish retail, including Boots. Founded in 1999, it manages more than 3,000 active trading accounts with a deliberately lean team.
Every customer email came into a shared inbox. Someone read it and worked out whether it was a tracking question, an investigation, a return or a refund. Then they opened the right carrier portal, matched the order number by hand and wrote a reply.
At peak season the volume rose three to four times. The team did not. Warranty terms, retailer return rules and brand templates lived in people’s heads and old emails. Internal logistics messages sat in the same inbox as real customer issues.
02
What we built.
A multi-agent system that reads each query, classifies it, pulls live carrier data and drafts a reply for a person to review. It runs entirely on JDM’s own infrastructure. We agreed one deliberately narrow scope: one workflow, done properly.
Customer email → reply
6 steps · a person approves
A customer email arrives in the shared Outlook inbox.
The classification agent reads it, filters out internal noise and sorts it: tracking, investigation, return or refund. It pulls out the order number.
The carrier agent pulls live tracking from the right carrier: DHL, Royal Mail, DPD or Parcel Force.
The knowledge base is checked: warranty terms, FAQs and the brand’s own templates.
A draft reply is written in the brand’s voice.
Customer service reviews it, edits if needed and sends it from Outlook. Every edit teaches the system.
Customer service
03
How it works day to day.
The team works in Outlook, as before. Each query is also a card on a dashboard, with its full conversation history and a carrier breakdown, moving along a pipeline from new to resolved.
Nothing goes out without a person. The system reads, checks and drafts, and the team decides. Since going live in January 2026 we have held a weekly session with the team. The dashboard was rebuilt on their feedback in February, and 47 corrections from their edits were applied in the first weeks.
04
The results.
- 98%faster drafting: under 12 seconds to a draft reply
- ~65%of queries auto-resolved, approved as drafted (9 of 14 over one weekend)
- 10×peak capacity
- 8 to 12 hrsof customer-service capacity freed every week
- $30Ka year saved on infrastructure
- 48 hrsto onboard a new brand into the knowledge base
SourceFigures as recorded with JDM Products, March 2026.
05
How we got there.
Apr to Jun 2025
Discovery
Inside the customer-service operation: query volumes, carrier workflows, retail portals, seasonal patterns. Scope agreed.
Aug to Oct 2025
Build
Carrier integrations, two-way Outlook sync and the dashboard, deployed on JDM’s on-premise environment.
Jan 2026 onward
Go-live and weekly iteration
Live on real customer queries. Weekly feedback from day one. Dashboard rebuilt in February. Backend moved to Supabase.
06
What happened next.
In February, JDM’s Commercial Director laid out new AI use cases across three business units, unprompted:
- field-sales briefings
- cross-system search
- new-brand onboarding
- lead detection for its 3PL arm
- SOP documentation
He also asked for a presentation to give to his own board, and he now calls the system a “locally hosted AI team”. The foundation (classification, knowledge base, carrier integrations and the learning loop) is reused by each new workflow.
“locally hosted AI team”
07
Tools and systems.
- Outlook (two-way sync)
- DHL
- Royal Mail
- DPD
- Parcel Force
- the Boots portal
- Hyper-V (on-premise)
- an Ubuntu VM
- Azure OpenAI
- Airtable (moved to Supabase)
- Supabase
Bring your busiest inbox. We will show you where AI pays, before your next peak.
Start with a conversation.
A free 45-minute strategy call with a founder. No pitch deck. You leave knowing where AI would pay in your business, whether or not you work with us.
On the call
- 01Where AI would pay in your business.
- 02What your first system could be.
- 03What your AI Blueprint would cover.
Before you book
What does it cost?
Every engagement starts with the AI Blueprint, priced up front. The first system is a fixed fee, set from what the Blueprint finds. Nothing is quoted cold.
Where does our data go?
Nowhere new. It runs in secure environments, on your cloud or your own servers. Every action is logged, and nothing trains anyone else's model.
How much of our team's time does it take?
Most at the start, while we learn how the work really happens. After that, a short weekly session with the people using it.
Who owns what you build?
You do. The systems, the data, the prompts and the documentation.
Pick a time that suits you.
Book a strategy callPrefer email? Write to hello@braind.io.


