The calls started before my first coffee.
I managed a crew of 8 delivery drivers for a regional distributor outside of Charlotte. Every shift began with the same pattern repeating itself. Dispatch would call me because a customer had called them. Then I would call the driver to ask the question everyone already knew was coming. Where are you?
On a typical shift I fielded more than 30 of those calls. Nobody was frustrated or trying to micromanage. The phone was simply the only tool any of us had for answering that question. The customers were not being difficult, the dispatchers were not being nosy, and the drivers were not being evasive. Everyone in the chain simply lacked access to the same piece of information at the same time.
The thing I eventually realized is that “where are you” was never actually a question about location. Nobody calling me cared whether the driver was on Oak Street or stuck behind a train on the bypass near the old cotton mill. What they wanted was a time. A countdown. A specific answer to the question they were really asking: when will you be here? Location was just a rough proxy for arrival, and it was a terrible one. Knowing that a driver is “about ten minutes away” required the caller to trust the driver’s estimate, factor in traffic they could not see, and translate a street name into a prediction. Most people gave up on the math and just called again later to check.
What “Where Are You” Actually Costs a Team
Each call lasted roughly a minute and a half. That does not sound like much until you multiply it across an entire shift. I was spending close to 45 minutes of every working day relaying location updates. That time was not productive in any meaningful sense. I was not solving problems or making decisions. I was acting as a human GPS relay, converting a dot on a map into a verbal estimate and passing it down the line by phone.
The drivers paid a steeper price than I did. Every call interrupted their actual work. A driver backing into a loading dock does not need a vibrating phone on the dashboard. A driver navigating an unfamiliar neighborhood does not need to answer a call about a stop he has not reached yet. The interruptions created small delays that compounded across the day. Later deliveries fell behind schedule. That generated even more “where are you” calls from the customers waiting on those deliveries. The cycle fed itself.
One of my drivers, Marcus, summed up the absurdity better than I ever could. I had called him mid-route to ask for his location on behalf of a customer. After he told me he was about seven minutes out, he said something that made me put down the phone and stare at my screen. “You called me to ask where I was while I was literally watching my dot move on your screen.” He was completely right. I had the live tracking dashboard open the entire time. His dot was clearly heading toward the next stop. I called him out of pure muscle memory. Years of phone-based dispatching had trained me to reach for the handset the moment anyone asked.
That moment embarrassed me into changing how I worked. It proved that the problem was not a lack of technology. Most field teams already carry the tracking hardware they need in their pockets. The real gap was behavioral. A stubborn habit of calling when the screen already had the answer.
ETA Answers the Question Nobody Knew How to Ask
Real-time ETA tracking changed how information moved through our team. Instead of showing a dot on a map and forcing everyone to guess what it meant, it displayed a countdown. That countdown updated itself every few seconds. It used the driver’s actual speed, current traffic conditions, and remaining route distance. The math everyone had been doing in their heads was now automatic. The result was right there on the screen for anyone with access.
The difference between a GPS position and an ETA is the difference between raw data and a useful answer. A dot on a map tells you where someone is right now. That forces you to interpret geography, estimate distance, and guess at traffic. An ETA skips all of that and gives you the one thing you wanted: when the driver will arrive. Dispatchers do not need to decode a map. Customers do not need to call and ask. Live ETA tools replace the guessing game with a countdown that recalculates every time conditions change.
When I rolled out live ETA across my crew, the call volume did not decline gradually. It dropped sharply within the first few days. Dispatchers could see arrival times for every driver without picking up the phone. I could check on any delivery without interrupting the driver who was making it. Customers who received a tracking link stopped calling altogether. The answer to their question was updating itself on their screen. The “where are you” call did not just become less frequent. It almost entirely vanished from our daily routine.
The Habit Outlasts the Problem
I still catch myself reaching for the phone. It has been months since we switched to live ETA as our primary visibility tool. My first instinct when a customer calls dispatch is still to phone the driver. That reflex was built over years. It does not disappear because someone installed better software. Then I look at my screen, see the ETA updating in real time, and put the phone down. Fewer interruptions meant fewer mistakes at delivery points. Marcus told me the afternoon shift stopped feeling like a gauntlet of phone calls he had to survive.
The real transition was not about adopting a new tool. It was about building trust in a screen instead of a voice. Trusting that a number updating every few seconds is more accurate than a verbal estimate. Trusting that silence from a driver means everything is on track. That trust took weeks to build. The data was reliable from day one, but habits forged over years of phone-first dispatching do not yield to logic alone.
“Where are you” is a symptom, not a question. Every time that call happens, it reveals a visibility gap. Someone in the chain lacked information that should have been available without asking. Real-time ETA tracking does not just answer the question faster. It eliminates the conditions that caused the question to exist. It pushes arrival information to everyone who needs it before they go looking.
My crew still makes plenty of calls during a shift. Drivers call about access problems at delivery sites. Dispatch calls about last-minute schedule changes. I call about severe weather or road closures. Those conversations carry actual information that requires discussion. But the “where are you” call, the one that consumed 45 minutes of every shift and interrupted drivers during their most focused work, that particular call is gone. Nobody has ever asked for it back. If your team still fields those calls dozens of times a day, what would your shift look like if that question simply answered itself?