Solution 02 urban night
Every unit, every route, every delivery: visible
GPS tracking, dispatch and real-time follow-up, with agents that notify before the client asks.
The underlying problem
The operation lives on the phone: the coordinator calls every driver to know where they are, the customer calls to ask about their delivery, and the route sheet — printed in the morning — no longer matches the street by noon.
Follow-up is stitched by hand: WhatsApp screenshots, loose sheets, a trip log filled from memory at the end of the shift. When something runs late, the operation doesn’t know in time — the customer finds out first, and finds out complaining.
The cost is double: hours on the phone coordinating what the system could report on its own, and customers losing trust because the answer to “where is my order?” takes hours.
How it works
- 01
Units on the map
Real-time GPS and telemetry: position, route, stops and ETA for every unit, visible to operations — and to the customer, without calling.
- 02
Digital dispatch and trip log
Trip assignment, departure checklist and paperless trip log: every event records itself, with time and location.
- 03
Notices that send themselves
Customer ETA, delays and arrivals: agents notify by WhatsApp or email before anyone has to dial.
- 04
Exceptions coordinated
Delay, detour or breakdown: the agent detects it, notifies those affected and proposes the reassignment — the exception is handled before it becomes a complaint.
- 05
Measure and optimize
With every trip measured, AI finds the patterns: routes that always run late, extra kilometers, units heading for the workshop.
By industry
Headway · min between units
9 minAgents at work · live
- per-stop ETA published · route 4
- depot departure validated · unit 23
- headway regulated · route 7 · −3 min wait
- passenger count consolidated
Site map · Route 4 — depot to terminal
Live readings
Trips · demo · synthetic data
| time | record | area | status |
|---|---|---|---|
| 05:40 | depot departure · unit 23 | dispatch | auto |
| 05:41 | unit 23 checklist | operations | ok |
| 06:01 | downtown stop pass · route 4 | routes | auto |
| 06:10 | passenger count · unit 15 | fares | auto |
| 06:18 | minor incident reported | operations | created |
Events flow in on their own — GPS, the driver app and messages. The log fills itself with time and location.
Connected sites · country
Reports of the day · built by agents
Nobody built these reports: the agent assembles them from trips already measured and sends them to the decision maker.
Agent roster · today
Typical areas
- Routes
- Units
- Frequencies
- Fares
Every unit visible on its route with estimated arrival per stop; frequency gaps are detected and a backup unit dispatched before the stop fills up — like the system built for Analibus.
Typical areas
- Dispatch
- Delivery
- Support
- Returns
Shipments with live tracking and automatic notices to the recipient; “where is my order?” is answered by a bot with the real location, and delays notify on their own.
Typical areas
- Logistics
- Maintenance
- Safety
- Fuel
Telemetry for every unit, geofences and driving or detour alerts; maintenance is scheduled by real mileage and fuel is reconciled against the route.
Typical AI agents
ETA to 14 customers · sent
23 tasks todaytrip 118 → U-07
14 tasks todayU-12 delay · reassigning stops
9 tasks today“where is my order?” · tracking 8841
141 tasks todaytrip 117 · closed with evidence
3 tasks todaysouth route · −12 km
11 tasks todayMade to measure
Demos use synthetic data. Every system is configured to each client’s process and integrates with the tools you already use.
