Watch the work move on a map, run it on a board
A dispatcher's screen that shows the truth at a glance: every order, every vehicle, every technician, the route each one is on and the customer watching their own technician arrive.
The dispatcher's screen
Dispatch is two questions asked all day: what is happening right now, and who should take the next one. Both should be answerable without opening four things.
-
A live fleet map
Orders, technicians, vehicles, routes, service areas and geofences on one map, updating as the day moves rather than when someone refreshes.
-
An order board
Every order as a card, every stage as a column. Drag a card to move it and the record moves with it.
-
Geofences that notice
Draw an arrival zone and the platform marks the order on site when the technician crosses it, so nobody has to tap a button in a driveway.
-
Arrival estimates
Remaining distance and the technician's recent pace produce a window, labelled as an estimate and updated as the day changes.
-
Vehicles and fleets
Track trucks and trailers as assets with their own status, capacity, assigned driver and service history, not just as a name in a spreadsheet.
-
Customer tracking
Send a link that shows one order's live status, and only that order. It expires when the work is done.
A card is the whole order, not a summary of one
Opening a card on the board gives you everything the order carries, and moving it is a real transition the server validates.
- Unassigned 07:10
- Assigned 07:22
- En route 07:41
- On site 08:03
- Complete 08:48
Columns come from your own order configuration, so the board matches how your business actually works rather than how someone else's does.
The board cannot invent a state
A board that lets anyone drag a card anywhere is a board that quietly corrupts the record. Here, the server decides what is legal and the board only offers what it is told.
Every order type has a defined set of stages and a defined set of moves between them. When a card is dropped, the change is sent to the server as a transition. If it is allowed, it is applied and written to the order's history. If it is not, it is refused with the moves that are actually available, and the card returns to where it was.
That is what makes the board trustworthy rather than decorative. The same discipline that governs the technicians' status changes governs the dispatcher's screen, so a card that says complete really is complete, with the proof attached and the invoice following.
Every move is recorded with who did it, whether that was a person or an agent, and when. The order's history is not reconstructed later from memory. It was written down as it happened.
-
Your stages, not ours
Define the order types you actually run and the stages each one passes through, with the fields each stage requires.
-
Rules attached to stages
A stage can require a photo, a signature, a part or a note before the order is allowed to leave it.
-
History as it happened
Every transition is appended with actor, time and position, giving the timeline and the audit trail from the same records.
-
Automation on top
Transitions can trigger the next thing: notify the customer, raise the invoice, order the part, or ask a person to look.
What is on the map
Layers can be turned on and off so a dispatcher sees the district, not the world.
For operations that run trucks, not just technicians
The same records serve a plumbing company with four vans and a fleet operation with trailers and depots.
-
Trailers and equipment
Towed and portable assets tracked in their own right, with connections to vehicles that change over time rather than being overwritten.
-
Maintenance schedules
Service intervals by vehicle or by hours, work orders, parts used and warranty records, so maintenance is planned rather than reactive.
-
Fuel and cost per mile
Fuel records and running costs per vehicle, so the cost of a route is a number rather than an intuition.
-
Telematics
Connect a telematics provider and vehicle positions and sensor data arrive without anyone's phone being involved.
-
Manifests
Group orders onto a manifest for a run, so a multi stop delivery or a bulk collection is one object rather than twenty.
-
Operations reporting
On time percentage, jobs per technician, distance and utilisation, out of the records the dispatcher is already using.
A dispatcher should be able to answer what happened today without asking anyone.
Fleet and dispatch by plan
| Growth | Scale | White label | |
|---|---|---|---|
| Order board | Yes | Yes | Yes |
| Custom order types and stages | Yes | Yes | Yes |
| Live map | Basic | Yes | Yes |
| Geofences and arrival detection | Not included | Yes | Yes |
| Arrival estimates | Not included | Yes | Yes |
| Vehicles and trailers | Not included | Yes | Yes |
| Telematics connections | Not included | Yes | Yes |
| Customer tracking links | Not included | Yes | Yes |
| Unlimited everything | Not included | Not included | Yes |
Questions people ask before signing up
How often do positions update?
Positions are reported by the technician's device as they move, and the dispatcher's map updates without a refresh. The interface shows how fresh each position is, because a map that hides a ten minute old position is worse than one that admits it.
Can I use my own map provider?
The map is served through the platform, and no third party script runs in your browser or tracks your customers. Where a commercial basemap is preferred it can be configured, and the customer tracking page continues to render through the platform.
Do I need telematics hardware?
No. Positions come from the technicians' devices by default, which works on day one with no hardware. Telematics is for operations that want vehicle data without depending on a phone, and it can be added later.
Can a customer see where the technician is without seeing anything else?
Yes. A tracking link is scoped to one order and shows only that order's status and arrival window. It carries no customer data, it cannot be used to browse anything else, and it expires when the work is complete.
Does the board work for a company with several districts?
Yes, and the districts are enforced rather than filtered. A dispatcher scoped to one district sees that district's board and map, and the restriction is applied in the query rather than by hiding things on screen.
Start on the free plan
Twenty customers, one location, every core module, free permanently. Move up when the work outgrows it.