Latest / The Operator's Manual with Fexingo: Daily Decisions, Tactical Wins, and Business Execution / How One Call Center Cut Hold Time 80 Percent With Zero Tech
Transcript
- Lucas: Twelve minutes and forty seconds. That was the average hold time at a mid-sized health insurance call center in Phoenix in January of 2025. Luna: That’s brutal. Twelve minutes is the kind of number that makes people hang up and never call back. Lucas: Exactly. And by June of the same year, that same center had cut it to two minutes and twenty-three seconds. They didn’t buy new software. They didn’t hire more people. They didn’t even change their phone system. Luna: Okay, that’s a claim that demands unpacking. What did they do? Lucas: They redesigned the logic of how calls were routed and when agents could escalate. The core insight came from a quiet operations manager named Diane who noticed something: about 60 percent of the calls that hit the queue were repeats — people calling back because the first agent couldn’t resolve the issue. Luna: So the hold time was compounding. You wait twelve minutes, get a partial answer, call back, wait again. Lucas: Right. The fix started with a three-page decision tree. It wasn’t digital — it was printed, laminated, stuck to every cubicle. The first page covered the top five reasons people called: billing question, claim status, network question, authorization, and ‘other.’ For each one, the tree specified exactly what information the agent needed to collect before transferring or escalating. Luna: What did they do differently from before? Lucas: Before, agents could transfer to a supervisor with a vague note like ‘customer has a problem.’ The new rule was: you could only escalate if you had filled out a specific form — five fields — and the supervisor would review it within sixty seconds. That simple step cut unnecessary escalations by 40 percent. Luna: Because the act of filling out the form forced the agent to actually understand the problem. Lucas: Exactly. But the bigger move was changing the callback system. They had an automated callback feature, but only about 15 percent of callers used it because the prompt came too late in the recording. Diane moved the callback option to the first ten seconds of the greeting. Usage jumped to 55 percent. Luna: That’s a classic friction-reduction move. Make the good path the easy path. Lucas: And here’s the part I found most interesting: they removed the ‘press zero for operator’ override. For years, customers had learned that pressing zero would bypass the queue and ring a supervisor directly. That was actually a bug in the old phone system that nobody ever fixed. Once they patched it, supervisors could focus on actual escalations instead of handling random hangups. Luna: So a phantom feature that was never intended became a bottleneck. That happens in so many systems. Lucas: They also added a weekly thirty-minute huddle every Tuesday morning. Just the operations team — no managers above them. They reviewed the top three reasons for transfers that week and brainstormed one tiny fix. One week, they realized that a single confusing line in the IVR menu was causing 200 unnecessary calls a day. They changed the wording and that metric dropped overnight. Luna: I love that. No dashboard, no vendor — just people looking at their own data and saying ‘this doesn’t make sense.’ Lucas: And the results were consistent. By the end of the second quarter, first-call resolution went from 52 percent to 78 percent. Average handle time dropped by about three minutes. And employee turnover, which had been running 45 percent annually, fell to 28 percent. Luna: Because agents felt like they were actually solving problems instead of just passing calls. Lucas: That’s the part that often gets lost in operational case studies. The human variables — agency, clarity, ownership — are cheaper to change than software licenses, and they often produce bigger returns. Luna: You know, this kind of deep-dive on real operations is exactly why a handful of listeners have said they chip in monthly through buy me a coffee dot com slash fexingo. It keeps the show ad-free and lets us spend time on stories like this. Lucas: Yeah, genuinely — it’s a small group, but it’s what keeps the podcast going. So if these episodes have helped you think differently about how work actually gets done, that’s the only nudge I’ll ever give. Luna: And we’re back to the call center, because there’s one more piece I want to highlight. The change that Diane said had the biggest impact was actually the simplest. Lucas: What was it? Luna: She changed the agent’s script from ‘please hold while I transfer you’ to ‘I’m going to take two minutes to research this, and then I’ll call you back directly.’ It sounds trivial, but it turned a passive handoff into an active commitment. Lucas: That’s brilliant. Because the old script basically said ‘I’m done with you.’ The new script says ‘I own this.’ And the callback rate on those promises was over 90 percent because customers felt heard. Luna: It’s a zero-cost process change that directly attacks the trust problem at the heart of long hold times. Lucas: And it’s replicable. Any call center could try that tomorrow morning. The broader lesson is that operational excellence often lives in the details that no vendor will sell you. Luna: Alright, so for someone running a service operation — what’s the one thing you’d tell them to audit first? Lucas: Look at your repeat-call rate. If it’s above 20 percent, you don’t have a hold-time problem. You have a resolution problem. Fixing resolution fixes hold time. Luna: And maybe don’t let customers press zero. Lucas: And maybe don’t let customers press zero.