01The challenge
Fernway's support team is twelve people covering every city it delivers to. On a normal day more than half of their tickets were delivery questions: a bike held at the Leeds depot, a missed scan, a courier slot that moved.
Each answer meant opening three tools, finding the order, reading the courier notes and writing the same reply in slightly different words. The team was good at it, and tired of it. Repair bookings and billing disputes, the conversations that needed judgement, waited behind the queue.
02The approach
The CX team wrote the delivery playbook themselves in Parley, in the same plain language they use to train new hires: how to find an order, what each courier status means, when to offer a new slot and when to hand over.
An order lookup action connects the agent to Fernway's order system, and a courier status action reads the latest scan. Every reply cites the order and the scan it came from, so a person taking over sees exactly what the agent saw.
Before launch the team ran the playbook against two hundred real past conversations in simulations, fixed the six that went wrong, and went live on web chat first, then WhatsApp a week later.
“Parley took parcel questions off our queue in three weeks. Our team finally gets to work the hard cases.”
03The results
Three weeks after the first draft, the agent was answering delivery questions on its own. It now resolves 68% of them without a person, and first replies are three times faster across every channel.
The conversations that do reach the team arrive with the order, the courier history and a one-line summary attached. Maya's team now spends its day on repairs, refunds and the customers who need a person.