I've been on both sides of this. As a customer waiting on a service tech, and as the operator dispatching them. The single biggest customer-experience upgrade I've seen in field service software in the last five years isn't AI, isn't automation, isn't even mobile apps. It's the customer being able to see where their tech is, in real time, on a map.
Everybody knows this from Uber and DoorDash. Your pizza is 3 minutes away. The driver is at the corner. We've been trained, as consumers, to expect this. And then you call to schedule a service tech and the dispatcher says "we'll be there between 8 and 5." It's like time-traveling back to 1998.
This piece is about what live customer ETA tracking actually is in field service software, why the old 4-hour window is dead, what to look for when you're buying, and how I built it into ReliableTrack so my own crew uses it every day.
The 4-hour window is a tax on your customer
Let's name the cost. When you tell a customer "we'll be there between 8am and noon," you are charging them four hours of their life. They can't go to work. They can't run errands. They can't take their kid to soccer practice. They sit at home and wait. And then if you slip — which you usually do — they wait longer.
The cost is real and it shows up in three places:
- Cancellations. Customers who can't waste half a day call you back to reschedule. Half of them never call back at all.
- Bad reviews. The #1 complaint in service-business Google reviews isn't price, isn't quality, isn't the tech's attitude. It's "they were late and didn't tell me."
- Repeat business. A customer who got a great service experience but a terrible scheduling experience books elsewhere next time.
The 4-hour window made sense when dispatchers didn't have real-time visibility into where their techs were. That stopped being true 15 years ago. The reason field service companies still quote 4-hour windows is operational laziness, not technical necessity.
What "live ETA tracking" actually means
There are three different things people lump under this label. Be careful, because vendors will sell you the cheap version and call it the expensive version.
Level 1: Status updates (the bare minimum)
The customer gets a text when the tech leaves the previous job: "Mike is on the way." That's it. No map. No live ETA. This is better than nothing — at least the customer knows roughly when to expect someone — but it's a 2010-era experience.
Level 2: Static map link
The customer gets a link to a map showing the tech's current location, but the ETA is the same number the dispatcher entered in the morning. The dot moves on the map, but the "arrives by" time is static. Most field service vendors stop here and call it "real-time tracking." It's not.
Level 3: Live dynamic ETA
The customer's link shows the tech moving on the map AND the ETA recalculates as traffic, the tech's actual pace, and the previous job's completion time change. If the tech finishes the 10am job early, the customer's "arrives by 1:30pm" tightens to "arrives by 12:50pm" before the tech even gets in the truck. This is the Uber experience. Most field service customers have never seen it from a service business.
The buying test: Ask the vendor to demo the customer-facing tracking link on YOUR phone, not the salesperson's. Watch what happens when the tech stops for gas. Does the customer ETA reflect the delay? If the answer is "the ETA updates every 30 minutes," that's not live. That's a slideshow.
Why this matters more in oilfield than in residential service
Most field service software vendors come from the residential service world — HVAC for homeowners, plumbing for homeowners, pest control for homeowners. ETA tracking in that world is mostly a customer-experience play. The homeowner waiting at home wants to know when the guy is coming.
In the Permian Basin, the customer isn't a homeowner sitting on a couch. The customer is a production foreman whose well is shut in. Every hour that well is shut in costs money. Every hour the foreman waits at a remote location to meet the tech costs the operator real dollars. ETA tracking in the oilfield isn't a niceness. It's a tool for the production foreman to plan his day around when the contractor will actually show up.
I run a flare service. When the operator's foreman texts me "where's your guy?", I want him to be able to see the answer himself, on a map, without me having to call my tech and call him back. That used to be a 10-minute interruption five times a day. Now it's zero.
The technical pieces (so you know what to ask for)
If you're shopping for field service software with live ETA tracking, here's what's actually under the hood. You should ask vendors about each of these:
1. GPS sampling rate on the tech's phone
How often does the tech's app send GPS coordinates back to the server? Some cheap apps do this every 5 minutes. That's useless for live tracking — by the time the customer sees the dot, the tech has driven 4 miles. You want at least every 30 seconds while the app is open and the tech is moving, with intelligent batching while parked.
2. Battery drain
The flip side of fast GPS sampling is the tech's phone dying at 2pm. A good app uses geofencing and motion detection so it samples often when the truck is moving and rarely when it's parked. If your techs are running car chargers because the app burns the phone down by lunch, you've got a bad implementation.
3. Customer link generation
When the customer clicks the tracking link, do they have to install an app? Log in? Create an account? If the answer is yes to any of those, your customer is going to ignore it. The good ones generate a public, expiring link that works in any browser, no install, no login. Just open and see.
4. Offline degradation
What does the customer see when the tech goes into a cell-signal dead zone? The bad apps show "last update 47 minutes ago" and let the customer panic. The good apps say "tech last seen at [location], driving toward you, expected to arrive by [time]" — telling the customer what they need to know even when the GPS feed is stale.
5. Dispatcher visibility
The same data that powers customer ETA tracking should power the dispatcher's view of the day. If your software shows the customer a live ETA but doesn't show you, the operator, the same map, you bought the wrong software. You should be able to see all your techs on one map and reshuffle the day when something slips.
What changed at ROS when we turned this on
Three things, measurable:
- "Where's your guy?" calls dropped to near-zero. Before live tracking, I was fielding 3-5 of these a day from operator foremen. Now it's maybe one a week, and it's usually a foreman who hasn't bookmarked the tracking link yet.
- On-time rate stayed the same, but perception of on-time rate went way up. We weren't actually any later before. We just couldn't prove it. Now the customer sees the truck moving and trusts the schedule.
- The dispatcher (me) gets her day back. The 10-minute "let me call my tech and call you back" cycle was death by a thousand cuts. Now I look at one screen and answer in 5 seconds, or the customer doesn't even ask because they're looking at the same map.
The buying mistakes I see
I've talked to a lot of operators shopping for field service software since I built mine. Three patterns I see them get wrong:
Mistake 1: Buying for the dispatcher, not the customer
Most vendors demo the dispatch view — a beautiful map of all your trucks. That's nice, but it's not the value. The value is the customer-facing link. Ask to see THAT and use it on YOUR phone before signing.
Mistake 2: Assuming offline-first means tracking-first
Offline-first apps are great for letting your tech work without signal. But offline-first doesn't automatically mean great live tracking. The two are independent features. Ask both questions separately.
Mistake 3: Not asking about the link expiration
Some vendors hand the customer a tracking link that's permanent. That's a privacy and security problem — a former customer can see your tech's location forever. Good systems expire the link 1-2 hours after the job is closed.
What I'd build if I were starting over
I did build it. ReliableTrack has live ETA tracking baked in from day one because I was tired of the dispatcher loop. The customer gets a text with a link the moment we dispatch the tech, and that link shows them where the truck is and when it'll arrive, recalculated in real time. The link expires 90 minutes after job closeout. The tech's phone doesn't burn battery. The dispatcher sees the same map. That's the whole thing.
If you're shopping, that's the bar. Anything less, you're paying for something other than the real upgrade.
Want ReliableTrack tailored to your crew?
Live customer ETA tracking, offline-first work orders, AI on every page, bilingual Spanish/English. Get started — custom builds delivered in 48 hours.