"My Staff Don't Answer the Phones" — What the Call Data Actually Showed

A manager at a multi-location auto dealer group called me with a problem he was sure he understood. "My staff don't answer the phones," he said. He'd heard it from customers. He'd watched phones ring at the desk and go to voicemail. He wanted proof of how bad it was, and he wanted it fixed.

He was right that something was wrong. He was wrong about what.

This is the story of how our new AI Call Detail Reporting agent, part of the Arthur Igloo family and now available to SIP Express Plus customers, took a belief that would have cost real money to act on and turned it into a problem you could fix in an afternoon. If you run a business with more than a couple of phone lines, the lesson here applies to you too.

The Setup: Five Systems That Don't Talk to Each Other

This dealer group runs separate Sales, Service, and Parts departments across two stores. Their phones run on a Cisco CME system with a SIP Express Plus trunk. On top of that, they have a BDC auto-dialer making outbound calls, an AI voice receptionist handling some inbound traffic, and a FreePBX server running the department call queues.

Five systems. Five separate logs. None of them share a common call ID, which means none of them agree with each other about what happened on any given call. Ask each system "how are we doing on the phones?" and you get five different answers, all of them partial.

That's the trap. The manager was looking at one slice, phones ringing at desks, and drawing a conclusion about the whole operation. To know whether the business was actually missing calls, somebody had to stitch all five systems together. That's the job we built the analytics agent to do.

The Investigation: Making Five Logs Tell One Story

We pulled call records from all five systems over a clean seven-day window in June 2026 where every system had complete data. Then the agent did the unglamorous work that makes the answer trustworthy:

• Normalized the timezones so a call logged at 2:05 in one system lined up with the same call in another.
• Normalized every phone number to ten digits so the same caller looked like the same caller everywhere.
• Joined calls across systems on caller number, dialed number, and timestamp. Without a shared call ID, that's the only honest way to know a call in the trunk log and a call in the queue log are the same call.

Here's the part that matters, and it's the reason most "call reports" are garbage. When one customer calls in, a department queue rings every phone in that department at once, sometimes twenty-two phones. One person picks up. The other twenty-one show up in the raw log as "no answer." Count those raw rings and you'll conclude the team ignores 92% of calls. That number is nonsense, but it's exactly the kind of number that gets people yelled at.

So before measuring anything, the agent collapsed every call down to a single row. One customer call equals one row, no matter how many phones rang or how many systems touched it. Then we separated the two completely different things people lump together: calls into a department queue, and calls dialed straight to one person's extension.

Only then did we start counting.

The Finding: The Queues Were Fine. The Belief Was Wrong.

The top-line number surprised the manager. That week, 5,478 inbound calls came in over the trunk, and 5,285 were answered — about 96%. Only 187 didn't get picked up at the trunk at all.

Every department queue answered between 94% and 100% of its calls. Sales, Service, Parts — all healthy. The thing the manager was sure was broken, the queues, was the thing working best.

So where were the missed calls coming from? Not the queues. It was the direct-dial path: customers dialing one specific person's personal extension instead of a department.

We found 455 abandoned calls that week. 434 of them were direct-dial. Someone dialed an individual's extension and hung up after a median of about five seconds. Five seconds. That's not a customer waiting through twenty rings and giving up in frustration. That's a phone that did something wrong immediately.

It did. When we cross-referenced every abandoned direct call against the actual phone system configuration, about 206 of them hit a dead extension — a phone that was unregistered or had no device attached to it. It physically could not ring. Nobody ignored those calls. There was no phone on the other end to do the ignoring.

That's a different problem than "my staff don't answer the phones." Completely different. And it has a completely different fix.

How 455 Abandoned Calls Became 8 Lost Customers

Before we handed over a scary number, we did one more cross-check, the one that turns data into truth.

A call abandoning isn't the same as a customer lost. A lot of people who hang up just call back, or reach you another way. So the agent took the 79 unique callers who abandoned that week and looked for them across the other systems. Did they get through some other path?

71 of those 79 callers reached the dealership another way that same week, through the AI receptionist or the BDC. They weren't lost. They got their answer. That left 8 callers who were truly lost the entire week. Eight.

Sit with the size of that gap. The surface number was 455 abandoned calls, the kind of figure that starts a meeting about firing people. The real number, the customers who tried to reach this business and never got through, was eight. And the cause wasn't effort or attitude. It was a handful of dead phone lines.

The Fix: Two Changes, No Drama

Once you know the real problem, the fix is almost boring:

• Register or repoint the dead extensions so the phones that couldn't ring can ring.
• Add a department-queue fallback to every direct line so that when someone dials an individual and that person isn't there (or the line is dead), the call rolls to a team that answers instead of dying on an empty desk.

No new staff. No write-ups. No expensive "we need a whole new phone system" conversation. Two configuration changes that close the gap between 455 and 8 down toward zero.

The Operations View: While We Were In There

The same data answered a stack of questions the manager hadn't thought to ask. Our operations dashboard broke down call volume by department (Sales around 488 calls, Service around 385, Parts around 334, all answered between 96% and 99%), surfaced the busiest hours and days, and mapped where inbound leads were actually coming from.

It also separated the two outbound worlds that had been blurred together. The BDC auto-dialer made 6,287 outbound calls that week at roughly 9% live contact, which produced 65 appointments. The desk phones made 1,022 outbound calls across 47 extensions, which is a completely different kind of calling that deserves to be measured on its own terms. Lumping those together would tell you nothing useful about either one.

What This Means for Anyone With a Phone System

You don't have to be a dealer group with five systems for this to hit home. The lesson is simple, and it's about how you read your own phone data.

The scary surface number is almost always hiding the real problem, and the real problem is almost always smaller and more fixable than the panic suggests. "Nobody answers the phones" became "two dead extensions and a missing fallback rule." But you only get there if you stitch your systems together, collapse every call to one row before you count it, separate queue calls from direct calls, and check abandoned callers against every other way they might have reached you.

That's hard to do by hand. It takes a tool that knows how phone systems actually behave, which is exactly what we built. If your gut tells you you're missing calls, don't act on the gut. Get the real number first. It's usually a relief, and it always points you at a fix you can actually make.

See What Your Phones Are Really Doing

If you want this kind of clear answer about your own phone system, here's how to start:

Get a Custom Proposal. Tell us what systems you're running and what you're worried about, and we'll scope a call analytics engagement built around your setup. This is the fastest way to get a real answer. Request your custom proposal →

Call 844-486-4766 and talk to me directly. I'm the senior network specialist here, I've spent 20-plus years inside Cisco voice systems, and I'd rather talk through your situation than have you guess at it.

The Calling Analytics agent is available now to SIP Express Plus and Arthur Igloo customers. Learn more about our SIP Express Plus 20-phone and 50-phone bundles, or meet the Arthur Igloo AI agents.

You've probably got a belief about your phones right now. Let's find out if it's true.