01The challenge
Disruption arrives all at once. A single cancelled flight could put three hundred travellers in the phone queue, and the queue was where Kestrel lost the most goodwill.
Any agent that touched bookings had to satisfy a strict security review, and Kestrel's engineers wanted to read exactly what the agent would do at each step.
02The approach
The rebooking agent is a flow with custom code at its core: Kestrel's engineers wrote the itinerary search as a function in Parley, versioned alongside the rest of the agent and covered by simulations of real disruption days.
Engineers manage the agent from the Parley CLI and review changes as code. Traces show every step, every call and its timing, which is what the security team reviewed.
“Rebooking used to mean a forty minute hold. Now most travellers are rerouted before they reach the gate.”
03The results
Most disrupted travellers are now offered a new route before they reach the gate. The median rebooking takes two minutes, down from a forty minute hold.
The security review took one pass. Engineers can read every step as code, so nothing about the agent is a black box.