plan the work
Dispatch that adapts as fast as your day changes.
Etaprise’s AI matches every job to the right technician automatically, then keeps re-optimising as the day unfolds.
what it does
What AI Scheduling & Dispatch does
Manual dispatch means a coordinator juggling skills, locations, traffic and availability by hand, and redoing it every time a job runs long or a technician calls in sick.
Etaprise’s scheduling engine factors all of that in continuously, so dispatchers spend their time on the exceptions that actually need a human judgement call, not on rebuilding the board from scratch.
Every reschedule ripples through the rest of the day. When a job overruns or a customer cancels, Etaprise recalculates the affected routes and offers in seconds: instead of a dispatcher manually re-shuffling every technician downstream of the change.
- Matches technicians to jobs by skill, certification and proximity
- Re-optimises routes automatically as jobs change through the day
- Flags scheduling conflicts before they reach the technician
- Works across every team, region and time zone in one view
how it works
Four steps, and none of them are magic.
-
read
It starts from constraints, not preferences
Skill and certification required by the job, parts needed, site access windows, contract response times, technician working hours, and where everyone actually is.
-
match
Candidates are ranked, not picked blind
For each job it works out who can legitimately do it, then orders them by travel, workload and the cost of moving other work. Anyone excluded shows why: usually a missing qualification.
-
commit
Dispatch approves the plan
The engine proposes. A dispatcher accepts the day, adjusts it, or pins jobs that must not move. Nothing is dispatched to a technician without a human accepting it, unless you explicitly turn that on.
-
re-plan
The day survives contact with reality
A job overruns, a van breaks down, an emergency lands. It re-cuts the remaining schedule and shows what changed and who is affected, rather than silently reshuffling.
data and integration
What it reads, what it writes, what it sits beside.
Nothing here is a separate database. AI Scheduling & Dispatch works off the same work order, customer and asset records as everything else, which is the whole reason the modules are worth running together.
reads
Work orders, technician skills and licences, fleet positions, contract SLAs, parts availability.
writes
Assignments and time windows to the Dispatch Board and the technician's app; changed appointment times to the customer.
alongside
Your HR system for working hours and leave, telematics for vehicle position.
questions we actually get
Before you ask us on the call.
By default, no. It proposes and a dispatcher commits. Full auto-assign exists and some customers use it for high-volume routine work, but it is a decision you make deliberately.
Always, and overriding is not treated as an error. If you pin a technician to a job the engine plans around that.
It uses actual recorded travel between your sites where that history exists, and falls back to routing estimates where it does not. Early on it will be approximate; it improves as jobs close.
No, but it is only as good as what it knows. Skills and certifications matter most. Without those it optimises travel and produces plans that are efficient and occasionally illegal.
elsewhere in the platform
Other capabilities
further reading