“Support used to forward a bug and hope. Now the ticket shows who owns it within the morning, and when it ships the agent gets a list of everyone to reply to.”
Where bug reports went to wait
Quarry connects 4,000 building-material suppliers with contractors who order by the pallet. When an order breaks, a contractor calls support, and support used to forward the problem to a shared engineering inbox. Then they waited.
“Nobody owned the inbox,” says Imke de Waal, who manages Quarry’s three engineering teams. “Everybody assumed somebody else had read it. Median time from a report to someone owning it was 41 hours, and some never got an owner at all.”
One inbox per team, one key per decision
Quarry connected Lantern, their support desk, so agents link tickets to Keel issues from the ticket sidebar. Error spikes from Tripwire arrive the same way. Each team has a triage inbox, and one engineer per team takes the morning shift on a rota.
Keel Assist suggests a label, a priority and an owner for each report, with its reason: “Bram changed pricing.ts 7 times this month.” The engineer on shift presses 1 to accept, or changes what is wrong first. Most mornings the inbox is empty by 11:00.
Closing the loop with customers
When a linked issue ships, every Lantern ticket attached to it reopens with a drafted reply. In September, the fix for delivery slots on bank holidays went out to 64 contractors the same afternoon.
“Support stopped asking engineers for updates. The ticket already says ‘Fix in review’.”
Six months in
| Shared inbox | Keel triage | |
|---|---|---|
| Report to owner, median | 41 h | 3.2 h |
| Reports merged as duplicates | untracked | 31% |
| Customers told when fixed | when remembered | every linked ticket |