Driftwood found and fixed a shipping bug after 3 tickets instead of the usual dozen.
Driftwood's subscription model meant a steady stream of "where's my bag this month" tickets, plus a growing backlog of tickets marked waiting on the warehouse that nobody had time to chase.
Follow-Up Agent + Insights AgentThe bottleneck
Tickets waiting on a reply from the fulfillment team routinely sat open for two or more weeks with nobody assigned to follow up.
The two-person support team had no way to spot a pattern across tickets, a mislabeled shipping rule went unnoticed for nearly a month before someone connected the complaints.
Renewal and delay communication was reactive, customers found out their order was late by asking, not by hearing from Driftwood first.
Root cause work happened only when someone had a free afternoon, so the same three-week-old shipping problem could keep generating new tickets before anyone traced it back to one cause.
The workflow
The Follow-Up Agent now monitors every open ticket and pings the fulfillment team in Slack automatically when a ticket is waiting on them past a set number of days, so nothing ages out of view.
Shipping delays now trigger a proactive update to the customer before they have to ask, using the same channel the original ticket came in on, which turned a chunk of inbound volume into outbound-only conversations.
The Insights Agent reviews every resolved ticket for root cause, clustering complaints by underlying issue rather than by the words a customer happened to use.
That clustering flagged the mislabeled shipping rule after the third related ticket instead of the twelfth, tagging it as one fulfillment issue rather than three unrelated complaints and routing it straight to the warehouse team.
“We didn't find out about problems, we found out about complaints. Now we see the pattern by the third ticket instead of hearing about it for a month straight.”
Co-founder, Driftwood Coffee Roasters
Lessons learned
Root cause needs a system, not a slow afternoon
Driftwood's support reps were sharp enough to spot a pattern, they just never had uninterrupted time to look for one. An agent that reviews every closed ticket for root cause, continuously, catches what a busy team would only notice by accident.
Stop the bleeding before you find the source
Follow-up nudges to the fulfillment team went live before the Insights Agent did. Closing the loop on stale tickets bought Driftwood immediate relief while the harder problem, tracing complaints back to a shared cause, was still being solved underneath.
Proactive beats reactive even when the news is bad
Telling a customer their order is late before they ask doesn't fix the delay, but it changes the entire tone of the relationship. Small teams often avoid proactive bad-news messages out of instinct; Driftwood's CSAT went up specifically because they stopped avoiding it.
Cluster by cause, not by complaint
Three tickets that read as three different complaints were, underneath, one shipping rule error. Grouping tickets by likely root cause rather than surface-level wording is what let Driftwood catch a bug at ticket three instead of ticket twelve.
“The proactive shipping updates cut our incoming volume before we even fixed the underlying bug. Half the tickets disappeared just because people weren't left wondering.”
Support Lead, Driftwood Coffee Roasters