TL;DR: An HR software company in Austin had six support reps handling everything - billing, technical, onboarding, feature requests. "Whoever grabs it first" was the system. 35% of tickets got reassigned at least once. Average time to reach the right person: 4 hours. We built an agent that reads ticket content, classifies by category, and routes to qualified reps based on expertise and workload. Reassignment dropped to 6%. Time to right person: 8 minutes. Customer satisfaction jumped 18 points.
Support Hot Potato
Every support team knows this game.
A ticket comes in. Someone grabs it. They read it. Realize it's not their area. Forward it. The next person reads it. Maybe it's theirs. Maybe they forward it again.
Meanwhile, the customer waits. Watches their ticket bounce. Wonders if anyone is actually going to help them.
Jordan ran support at a 42-person HR software company in Austin. Six reps. 400+ small business customers. Tickets came in via email, chat, and phone.
The "system" was simple: whoever sees it first, grabs it.
That worked when they were smaller. Three reps who knew everything. But at six reps with distinct expertise—billing, technical, onboarding, integrations—the generalist model broke down.
"I spend half my time forwarding tickets I shouldn't have grabbed," one rep told Jordan. "And half the tickets I get are things someone else should have kept."
The Numbers That Hurt
Jordan tracked ticket flow for a month. The results explained why customers were getting frustrated.
35% of tickets got reassigned at least once. More than a third.
4 hours average from ticket creation to reaching the right person. Some resolved quickly after that. But four hours of bouncing before work even started.
Customer satisfaction dropping. The trend was clear. Scores that used to be in the 80s were now in the low 70s.
Reps frustrated. Nobody felt like they were doing good work. Everyone felt like they were shuffling paper.
For more on how to calculate what inefficiencies like this actually cost, we've written about the hidden math.
The Skills Mismatch
The deeper problem wasn't workflow. It was expertise.
When reps grab any ticket, they handle things outside their specialty. A billing specialist gets a technical question about API integrations. A technical rep gets a question about invoice disputes.
Two bad outcomes:
Wrong answers. The billing specialist gives their best guess on the API question. It's wrong. Customer tries it. Fails. Escalates. Now it's a bigger problem.
Slow answers. The technical rep knows the billing question isn't their area but tries anyway. Spends 20 minutes researching something the billing specialist could answer in 2.
Either way, customer confidence erodes. Reps feel incompetent. Everyone's worse off.
The solution seemed obvious: specialize. Route billing to billing, technical to technical.
But that required someone to do the routing. And the "someone" was already six people grabbing tickets as fast as they could.
The design is next. The design, the build guide, the running costs and the take-away are free to subscribers. Enter your email below and the rest of this Blueprint opens. New ones arrive every Tuesday and Friday.
