All work
Agents · 2026
Relay
A support agent that closes tickets
An agent that reads the order, checks the policy and answers the customer, handing a person only what needs one.
Client
Relay Commerce
Year
2026
Role
Agent design and build
Built in
6 days
Result
71% of tickets closed alone

The brief
A homeware shop answered 600 tickets a week by hand, and most were the same five questions: where is my order, can I return it, it arrived broken. They wanted an agent that could act, not a chatbot that apologises.
Claude API
Node.js
Postgres
What I built
01
Tools, not scripts
The agent looks up orders, reads photos, checks the policy and issues refunds through the same systems the team uses.
02
A trace for every answer
Each step the agent took is shown beside the ticket, so a person can check it in seconds.
03
Hands off when it should
Anything over $200, any angry second message and any edge of the policy goes to a person, with a summary.

The build, day by day
Day 1
Six weeks of tickets read and sorted into the questions that repeat.
Day 2
The tools: orders, refunds, the policy and the photo check.
Days 3–4
The agent loop, its guardrails and 120 old tickets replayed as tests.
Day 5
The console for the team, with the trace beside every reply.
Day 6
Live on one ticket in ten, then on all of them by Friday.
brief.md
The prompt that did the most
›
You may refund up to $200 without asking. Above that, or if the customer is upset twice, write a two-line summary for a person and stop. Never promise a date the carrier has not given.
What it does now
71%
of tickets closed without a person
12s
median time to an answer
4.8
customer rating, up from 4.1
Relay answers most of our tickets before anyone on the team has opened them. It paid for itself in the first month.

Sofia Marchetti
Head of support, Relay
