Service-level promises and the drive times behind them
Promising a technician within the hour is easy on a map. Check the drive areas on usual roads, then live speeds at the hours that matter, before you sign.
Part of the guide Location intelligence automation
A service-level promise such as "a technician on site within 60 minutes" is only as good as the drive time behind it, and that drive time changes with the hour. Check it in two steps. First draw the area your base can reach on usual roads, so you know which customers sit inside the promise at all. Then measure live road speeds around your base and your key customers at the hours calls come in, and see how far below free flow they fall. Customers near the edge of the area at a slow hour are the ones whose promise you will break.
This is for operations and commercial teams who write response times into contracts: lift and HVAC maintenance, IT field engineers, security patrols, equipment rental, medical device service, roadside assistance. It explains why straight-line promises fail, how to read drive areas and live speeds, a worked example, and an AI employee that keeps checking.
Why promises drawn as circles get broken
Sales teams often draw a circle round the depot and promise everything inside it. A circle ignores rivers with few bridges, motorways with no exit for kilometres, one-way centres and hills. Two customers the same distance away can be ten minutes and forty minutes from the depot. The first time a large client in the second group calls at five in the evening, the contract is broken on day one.
The fix has two parts, because two different things vary. Geography decides where the roads go, which is fixed. Traffic decides how fast you move along them, which changes every hour.
Step one: the area on usual roads
The Travel area block draws the area that can be reached from a place within a travel time or a distance by road, by car, on foot or by bike, following the roads. Its travel times are for usual traffic, not the traffic at the moment of the run. That makes it the right tool for the first question: which customers could ever be served within the promise from this base?
Put your bases in a table, draw the drive area of each, and match your customer list against those areas. Customers outside every area should not be offered the standard promise at all, or need a different base.
Step two: live speeds at the hours that matter
The Traffic Flow block measures how traffic is moving on the roads around each place at the moment the flow runs: the current speed, the speed when the roads are free, the jam factor from 0 to 10, and the congestion as a percentage below free flow. It does not count cars and has no built-in peak hours; you get the rush hour by running it at the rush hour.
Schedule it at the times your calls arrive, for example 08:00, 12:30 and 17:30 on weekdays, around your depots and your biggest customers. After a few weeks you know, for each place and each slot, how much slower than free flow the roads typically are. A customer whose roads run at half their free speed at 17:30 is, in effect, twice as far away at that hour.
Turning the two into a promise you can keep
- Draw each base's drive area for the promised time on usual roads.
- Mark every customer inside or outside those areas.
- For customers inside, run Traffic Flow around them at each service hour for a few weeks and note the congestion.
- Tighten the promise for customers whose roads are often heavily jammed at the hours they call, or serve them from a nearer base.
- Write the contract by zone and hour, for example a standard time in the core and a longer one at the edge after 16:00, rather than one figure for everyone.
A worked example with made-up figures
All numbers below are invented to show the reasoning. A lift maintenance firm in Sao Paulo promises a technician within 60 minutes for entrapments. It has two depots and wants to bid for a contract covering 40 office towers.
- It draws a 15-minute drive area on usual roads around each depot as its core zone, where a technician can be on the road and arrive well within the hour. 34 of the towers sit inside one core zone or the other; 6 sit outside both.
- Traffic Flow, run at 18:00 on weekdays for three weeks, shows the roads around 9 of the 34 often at less than half their free-flow speed.
- The firm offers 60 minutes for 25 towers, 90 minutes after 16:00 for the 9 slow ones, and checks the 6 outside the core zones by hand before pricing a third depot for them.
In this example the bid is less impressive on paper and far more likely to be met, which is what keeps a maintenance contract renewed.
Mistakes to avoid
- Using a radius. A straight-line distance hides rivers, motorways and one-way systems.
- Checking traffic once. A single measurement tells you about that minute. Build up readings at the same hours over weeks.
- Expecting car counts. Live traffic data measures speed and jams, not how many vehicles pass. Car counts by hour exist only for some roads in the United Arab Emirates, through Regional data.
- Ignoring closures. A closed bridge on the only route breaks the promise whatever the speeds. Add Traffic incidents to see closures and roadworks.
- Forgetting the time to park and get in. In dense centres the last minutes are spent finding a bay and passing security, which no road data measures.
An AI employee that guards the promise
In xMap Flows a road watcher can do the measuring for you: Schedule at each service hour on weekdays, My data with your depots and key customers, Traffic Flow, a Filter on jam factor so only slow places pass, and Email or a Slack message to the dispatcher. Add Traffic incidents for closures near each customer.
Each run, the dispatcher sees which customers' roads are jammed right now and by how much, and can send a nearer technician before the promise is at risk. For the planning side, the Road speeds outside my depots, every hour and Who my warehouse reaches in 15 minutes templates are close starting points.
Questions
Does Travel area use live traffic?
No. Its travel times are for usual traffic. Use Traffic Flow, run at the hours you care about, to see how live conditions compare with free flow.
Can I get rush-hour speeds without running at rush hour?
No. Traffic Flow measures the roads at the moment it runs, so schedule it at the hours your calls come in and keep the readings.
How many vehicles use the roads near my customer?
Live traffic data does not count cars. Hour-by-hour car counts exist only for roads in the United Arab Emirates, as a Regional data dataset.
What does the jam factor mean?
It runs from 0, free-flowing, to 10, standstill or closed. The congestion percentage says how much slower than free flow the traffic is moving.