Your operation's data stays yours
Dispatch holds your customers’ addresses, your drivers’ details and your delivery history. Here is how it’s looked after.
Each organisation kept apart
Every record belongs to one organisation, and the database itself refuses to show or link it to another — not just the screens.
Roles decide what people can do
Dispatchers, managers, fleet admins and requesters each get only the pages and actions their role needs. Access can be suspended at once.
Sign in with Requester
There are no Dispatch passwords to leak or reuse. People sign in with their Requester account, using a standard, verified sign-in flow.
A record of every change
Who confirmed, rescheduled, cancelled or edited what, and when, is kept against each request, job and trip.
Private files
Document scans are stored privately and can only be opened by people in the same organisation.
Locked-down browser
Every page is sent over HTTPS with a strict content security policy, so the browser only runs Dispatch’s own code.
Only what the delivery needs
Dispatch sees the requests that reach the Dispatch step of your Requester workflow, and sends back decisions and status updates. Every message from Requester is signed, and Dispatch checks the signature before acting on it.
Only a Requester workspace Owner or Admin can install Dispatch, and they choose which Dispatch organisation the workspace feeds.
If Requester can’t be reached, Dispatch holds your updates and keeps trying until they’re delivered.
Run tomorrow’s deliveries from one screen.
Connect your Requester workspace and Dispatch is ready for your first request. Your team signs in with the Requester accounts they already have.