73% of customers call to ask where the truck is.
I counted. Two-week audit at a six-truck operation in Atlanta. Out of every ten inbound calls, seven were some version of “how far away are you guys?” Each call ate four to seven minutes. Dispatcher time. Driver interruptions. A customer pacing their empty living room. All to relay a data point a map pin could show in two seconds.
I used to be on the truck side. Drove delivery routes for three years before moving into ops. Every run, same thing. Phone buzzes. Dispatcher relays the customer question. I pull over, estimate time, call back. Customer hears “about forty minutes,” hangs up, calls again in twenty. Nobody is lying. Nobody is wrong. The system just has no single source of truth.
The $26,000 Phone Loop
One dispatcher spending 2.8 hours a day on location calls. At loaded cost, that runs $26,200 a year. For one person. At one desk. Answering the same question.
Here is what makes it worse. The dispatcher does not actually know where the truck is either. She is calling the driver, waiting for a callback, estimating based on the last check-in, then relaying a guess wrapped in confidence. Three humans in the loop to communicate one GPS coordinate.
I talked to an owner in Tennessee who thought he spent 20 minutes a day on location calls. We tracked it together for a week. One hour and forty minutes. Every day. He had never measured it because it did not feel like a task. It felt like answering the phone.
That is the trap. Location calls do not register as a cost center because they are mixed into the noise of daily operations. But add them up over a month, a quarter, a year. The number gets uncomfortable.
What Customers See vs. What They Need
Not a surveillance feed. Three things.
A dot on a map. An ETA. A notification when something changes.
That covers it. Speed data, break stops, route history? None of the customer’s business. A crew grabbing lunch at a gas station looks like a delay on a raw feed. Your lead guy taking a bathroom break looks like the truck stopped for no reason. Strip the customer view down to the basics. Show the dot. Show the time. Nothing else.
Separate dashboard for management. That is where you log idle time, speed, route deviations. Same GPS hardware, two different views. When you explain this split to your drivers, most of them relax immediately. A few will actually prefer it. No more phone interruptions mid-route is a trade they accept fast.
A Dallas Fleet, Before and After
Six trucks. Residential moves across the DFW metro. Dispatchers were logging 4.1 hours a day on location-related calls before tracking went in.
After: 42 minutes.
The freed-up time did not just disappear into breaks and small talk. Dispatchers started route planning. Actually looking at traffic patterns, sequencing pickups, consolidating loads. The kind of work that generates value instead of just managing anxiety. Fuel costs dropped. Customer satisfaction scores went up. Not because the trucks moved faster. Because the information was already on the screen before anyone felt the need to call.
The owner told me something I have heard versions of from a dozen operators since. “I did not realize how much of my business was just describing where things are.”
Selling It and Surviving It
A late truck with no communication produces a one-star review. A late truck with live tracking and a status update? Often three or four stars. Same delay. The difference is the customer felt informed instead of ignored.
One operator in Phoenix added “real-time truck tracking included” to his estimates. Close rate went from 31% to 38% in six months. His tracking system costs $85 a month.
But tracking creates a new problem if you are not careful.
Dead zones. Rural routes. A frozen map dot for thirty minutes triggers exactly the call you were trying to eliminate. If you are running moves to areas with spotty coverage, understanding how phone-based tracking works in the field saves you from making a promise the technology cannot keep. Set honest ETAs. Tell the customer upfront that the map may lag on certain stretches. That one sentence prevents more complaints than any feature ever will.
Pad your arrival windows. A system showing 2:00 PM when the truck pulls up at 2:30 creates a complaint. Show 2:45, arrive at 2:15. Same math. Opposite reaction.
Start With Two Trucks
Do not outfit the whole fleet on day one. Pick two trucks, two weeks. Measure call volume before and after. Get driver feedback. Fix the workflow gaps before you scale.
Train your office staff first. A dispatcher who cannot answer a tracking question creates more confusion than no tracking at all.
Those seven out of ten calls are not going to stop on their own. Your customers already told you what they want. They told you every time they picked up the phone.