Skip to main content
AI Agents & Automation

DispatchAutomation

Let new jobs find the right rider or technician automatically, with live status updates and dispatchers stepping in only when something goes off plan.

Dispatch Automation: what the work involves

A dispatcher's day is a stream of phone calls. A new job arrives, they scan a spreadsheet or group chat to see who is free, call a rider, wait for a reply, then call another if the first declines. Customers ring to ask where their driver is, and nobody has a trustworthy picture of the fleet. At busy hours, jobs wait unassigned simply because the dispatcher has run out of hands.

DevKey builds an assignment engine that receives jobs from your order system, website or call desk and picks the best available worker using rules you define: distance, current load, skills, shift, vehicle and customer priority. The offer is pushed to the worker's phone with a time limit, and the next candidate is tried automatically if it is declined. Customers receive live tracking links, and a dispatcher console highlights late, rejected or stuck jobs so attention goes where it is needed.

What we build

Core features

01

Automatic job assignment

Candidates are ranked by proximity, availability, skills and workload, and the top choice receives the job offer immediately.

02

Offer, accept and fallback flow

Workers have a short window to accept, and declined or ignored offers cascade to the next candidate without dispatcher effort.

03

Live location and ETA

Worker positions update on a map, and customers get a tracking link with an estimated arrival that adjusts to progress.

04

Priority and SLA rules

Urgent or premium jobs jump the queue, and approaching service-level deadlines raise alerts and trigger reassignment.

05

Exception console

Dispatchers view only the jobs needing attention, such as unassigned, delayed or disputed, and can override any decision.

06

Customer notifications

Messages go out on assignment, departure and arrival through WhatsApp, SMS or push notifications, reducing where-is-my-order calls.

Planned for

What we get right before launch

Fairness and worker acceptance

Workers resist systems that feel arbitrary. We make allocation rules transparent, balance earnings opportunities where it matters, and collect worker feedback before tuning the rules.

Location privacy and battery

Constant tracking drains phones and raises privacy concerns. We track only during shifts, tell workers what is collected, and balance update frequency against battery life and data costs.

Failure modes at peak load

When many jobs arrive at once or the network drops, assignment can stall. We design queues, timeouts and a manual mode, and rehearse outages so the desk can continue to operate.

Stack

Tools and technology

  • Python
  • Node.js
  • FastAPI
  • PostgreSQL with PostGIS
  • Redis
  • Google OR-Tools
  • Firebase Cloud Messaging
  • Flutter
  • WhatsApp Business API
Dispatch Automation FAQ

Common questions, answered

Is AI required for dispatching?

Much of dispatch is rules and optimisation rather than machine learning. We use AI where it helps, for example reading messy job descriptions or predicting service duration, and plain logic where that is more reliable.

Can it connect to our existing order system?

Yes, through APIs or webhooks, or by reading from a shared database. New jobs flow in automatically and statuses are written back, so your current system remains the record.

What if a worker rejects or does not respond?

The offer expires after the configured time and moves to the next suitable worker. Repeated declines raise an alert, so a dispatcher can intervene or adjust the pricing or area.

How is it different from route optimisation?

Route optimisation plans a batch of stops in advance. Dispatch assigns jobs as they arrive in real time. Many operations use both, with the planner for scheduled work and dispatch for on-demand tasks.

Ready to start your Dispatch Automation project?

Tell us what you need and we will come back with a clear scope, timeline and the questions worth answering before any build starts.