"My staff don't answer the phones": what the missed-call data actually showed

Five phone systems, five different stories

The manager called us with a problem he was sure he understood. "My staff don't answer the phones," he said. He'd heard it from customers and watched phones ring at the desk and roll 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.

The group runs separate Sales, Service and Parts departments across two stores. Their desk phones run on one system. A separate server runs the department call queues. An auto-dialer makes outbound calls for the appointment-setting team, an AI receptionist handles part of the inbound traffic, and the phone lines arrive through a fifth system with a log of its own.

So there were five systems and five logs, with no shared call ID and no agreement about what happened on any given call. Ask each one "how are we doing on the phones?" and you get five different answers, all of them partial.

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 really missing calls, somebody had to stitch all five systems together. The AI call analytics agent from Arthur Igloo, our AI arm, does that stitching.

How many missed calls is your business phone system hiding?

Usually fewer than the raw log says, and the reason is worth knowing before you read another phone report.

We pulled call records from all five systems over a clean seven-day window where every system had complete data. Then the agent did the cleanup that makes an answer trustworthy. It lined up the time zones and put every phone number in the same ten-digit format, so the same caller looked the same in every log. After that it matched calls across systems by caller number, dialed number and time. With no shared ID, that's the only way to know a call in the line log and a call in the queue log are the same call.

In this dealer's setup, when one customer calls a department, the queue rings every phone in that department at once. Sometimes that was 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 almost every call. 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 to a single row, no matter how many phones rang or how many systems touched it. Then it separated two things people lump together: calls into a department queue, and calls dialed straight to one person's extension. Only after that did the counting start.

The missed calls business phone logs couldn't explain

The top-line number surprised the manager. In this customer's data, 5,478 inbound calls came in over the lines that week, and the phone system picked up 5,285 of them, about 96 percent.

Every department queue answered between 94 and 100 percent of its calls. Sales, Service, Parts: all healthy. The part he was sure was broken was the part working best.

The missed calls were on the direct-dial path, where a customer dials one specific person's extension instead of a department. We found 455 abandoned calls that week, and 434 of them were direct-dial. Someone dialed an individual's extension and hung up, typically after about five seconds. A caller who hangs up at five seconds didn't sit through twenty rings and give up. Something went wrong the moment the call landed.

When we cross-referenced every abandoned direct call against the phone system's configuration, about 206 of them had hit a dead extension: a phone that was unregistered or had no device attached. It physically couldn't ring. Nobody ignored those calls. There was no phone on the other end to do the ignoring. That's a different problem from "my staff don't answer the phones," and it has a different fix.

How did 455 abandoned calls become eight lost customers?

Most of the people who hung up reached the dealership some other way that same week, and we checked that before handing over a scary number.

An abandoned call isn't a lost customer. Plenty of people who hang up simply 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. It found 71 of them, through the AI receptionist or the appointment-setting team. That left eight callers who were truly lost the entire week.

The surface number, 455 abandoned calls, is the kind of figure that starts a meeting about firing people. The real number was eight, and the cause was a couple of dead extensions, not anyone's effort or attitude.

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. Then add a fallback to every direct line, so a call to someone who's out, or whose phone is dead, rolls to a team that answers instead of dying on an empty desk.

That's two configuration changes. No new staff, no write-ups, and nobody has to sit through a "we need a whole new phone system" conversation. Between them they take that eight down toward zero. If you want to see how ring groups and time-of-day routing work day to day, we walk through them in our post on how a PBX handles call management.

This is also where Arthur, the AI receptionist from Arthur Igloo, our AI arm, earns his keep. He installs inside the phone system as a native extension. Make him the last stop on every direct line. A call to an empty desk gets answered, the caller gets a real response, and your team gets a text or email summary. Staff answer what they can, and Arthur takes the rest, around the clock. We explain why an AI receptionist belongs inside your phone system in a separate post.

What else the call data answered

The same data showed call volume by department, the busiest hours and days, and where inbound leads were coming from. It also pulled apart two kinds of outbound calling that had been blurred together: in this customer's data the auto-dialer made 6,287 outbound calls that week and the desk phones made 1,022 across 47 extensions. Those deserve to be measured on their own terms.

What this means in SW Washington

You don't have to be a dealer group with five systems for this to hit home. A dental office in Olympia with a front desk and four operatories has the same blind spot: the receptionist hears the phone ring, the hygienists hear nothing, and nobody knows whether the 4:55pm caller got through. A dealership or a warehouse office along I-5 in Centralia has it too, with more extensions and more places for a call to die.

When Wallaby runs your phones, the call data lives with us. We run the phone system, the network it rides on, and the firewall in front of it, and we watch all of it from The Igloo, our operations center in Tenino. So we can pull the real numbers for any customer in Southwest Washington and show you what's happening instead of guessing at it. A phone that drops off the system is also the kind of thing our 24/7 monitoring is built to flag, so it doesn't sit dead for weeks until a call log turns it up.

If your gut says you're missing calls, we can tell you for sure. Book a free on-site assessment, tell us what you run and what worries you, and we'll scope what it takes to get the real numbers for your setup. Or call (360) 515-2500. Our AI answers it 24/7, so that call is also a demo.