An AI employee that watches the roads around a depot
Set up a road watcher for a depot: what it checks every hour, when it should stay quiet, how it tells dispatch, and how to change it with a sentence when routes change.
Part of the guide AI employees
An AI employee that watches the roads around a depot checks, on a timetable you set, for closures, roadworks and other incidents within a few kilometres of each depot, reads how fast the traffic is moving on the roads beside it, and tells dispatch only when something affects the next wave of trucks, with a one-line suggestion of which way to leave. It runs on its own, keeps quiet when the roads are clear, and can be paused, made to ask first, or changed in plain words. Think of it as a colleague in the control room whose only job is the roads.
This is for operations and dispatch leads at logistics, distribution, waste and field service companies with one or many depots. It covers the job you give the road watcher, the settings that keep it useful rather than noisy, a made-up first week at a depot near Rotterdam, the mistakes that make dispatch mute it, and how to run and adjust it day to day.
The job description
An AI employee in xMap Flows is a flow with a job: a role, what it works on, when it works and where it reports. For a road watcher, write the job down before you build it:
- What it watches: the depots, from a table in My data with a name and position for each.
- What counts: road closures and roadworks within, say, 5 km of each depot from Traffic incidents; and, if you want it, the speed and jam factor on the roads beside the depot from Traffic Flow.
- When it works: every hour, or every 15 minutes, only between the first and last departures.
- Who it tells: the dispatch group on WhatsApp or Slack, and a copy by email.
- When it stays quiet: when nothing new is near any depot.
Traffic incidents finds closures, roadworks and other incidents on online maps as they stand now, each with its kind, street and position, and gives each depot how many are nearby and the closest one. Traffic Flow reads live speeds and how jammed the roads are at the moment it runs. Neither counts vehicles.
Settings that keep it useful, not noisy
- Work only in operating hours. A Schedule of every 15 minutes between 05:00 and 21:00 on weekdays avoids a 03:00 message nobody can act on.
- Filter to what matters. A Filter keeps only depots with at least one incident nearby, so a clear morning sends nothing.
- Send only what is new. Only new stops the same roadworks from being announced every hour for a month.
- Write one line, not a report. xMap LLM writes, for each affected depot, one sentence on which way trucks should leave to avoid the incident.
- Choose how much it does alone. Fully on its own for messages to your own dispatch group; Ask me first while you are still trusting it.
A worked example: the first week at a depot near Rotterdam
This week is made up. A distributor runs a depot on the edge of Rotterdam's port area, with trucks leaving from 05:30. The operations lead sets up a road watcher from the template Road closures near my depots, every hour, changes it to every 15 minutes from 05:00 to 21:00, and sets it to ask first for the first three days.
On Monday at 05:15 it finds roadworks on the main access road 2 km from the gate and drafts: "Roadworks on the port access road north of the depot; leave by the southern ring road until further notice." The lead approves it and it goes to dispatch on WhatsApp. On Tuesday it finds nothing new and sends nothing. On Wednesday it reports a closure that turns out to be on a road the trucks never use, so the lead tells it, in the Team inbox, to ignore incidents east of the canal. By Thursday the lead switches it to act on its own and tell her, and it carries on.
The next Monday, its weekly report card in the Monday email shows how many runs it made and how many found something, so the lead can judge whether hourly checks would do.
Mistakes that get a road watcher muted
- Every incident in the city. A 15 km radius buries the one closure that matters among thirty that do not.
- The same incident every hour. Without Only new, a month of roadworks becomes a month of messages.
- Messages at night. Limit the hours to when someone can act.
- Speed alerts with no threshold. Live speeds always vary; alert only when the jam factor is high, for example 7 or more, at departure times.
- Expecting counts. It tells you a road is closed or slow, not how many vehicles are on it.
Running and changing it
The blocks, in order: Schedule, My data (your depots), Traffic incidents (closures and roadworks around each, 5 km), Filter (at least one nearby), xMap LLM (the routing line), then a WhatsApp or Slack message to dispatch, an Email and a map.
What lands is short: the depot, the incident, its street and distance, and the line on which way to leave, with a map link. When nothing is near, nothing arrives. Its daily note in the Team inbox says how many checks it ran and what it found, and you can reply there in plain words to change it: "add the Antwerp depot", "only roadworks, not other incidents", "pause until Monday". For the week as a whole, Weekly road disruption report writes a one-page summary for managers; Incidents near my drivers' zones does the same job for drivers out on their rounds.
Questions
How often should a road watcher check?
Every hour suits most depots; every 15 minutes during departures suits busy ones. Limit it to the hours when someone can act on a message.
Can it tell me how many trucks are on a road?
No. Traffic incidents gives closures, roadworks and other incidents; Traffic Flow gives live speeds and the jam factor. Neither counts vehicles.
Will it send the same roadworks every hour?
Not with Only new in the flow: an incident is announced once, and the next message comes only when something new appears.
Can I check its messages before dispatch sees them?
Yes. Set it to Ask me first, or add an Approval block before the message, and switch to acting on its own once you trust it.
Templates that do this
Read next
More on ai employees and automation · Every article · Templates