Training a dispatcher in one afternoon: what to show, and in what order
5. 8. 2026
"Our lady on the desk is wonderful, but she does not really get on with computers." I hear that regularly, and behind it sits a fear that moving to an application will end in tears. It almost never does — as long as the training is not a lecture about every feature, but five tasks that cover ninety per cent of the day.
Take the fear away first
Before you show a single button, say two sentences:
"You cannot break anything." Nothing can be deleted irreversibly by clicking next to something. A ride is cancelled, not deleted, and stays in the history. A customer is deactivated, not deleted.
"Everything can be put right." A ride assigned to the wrong driver is reassigned, a wrong price overwritten, a wrong state reverted. Every change carries a name and a time in the history — not for supervision, but so that anybody can trace what happened.
Without those two sentences people are afraid to click and the training takes three times as long.
Five tasks that are enough for day one
Practise them in the demo — it holds fictional data and resets itself every hour, so you can click without any hesitation.
- Find a customer. Type part of a name or a phone number. That is it.
- Create a ride. Customer → from → to → time → number of passengers. Addresses that repeat are picked from a list, not typed.
- Assign a driver. The Assign button on the ride; each driver shows how much work they already have.
- Cancel a ride. The red button; the note is optional.
- Look at today. Coloured labels: blue is new, yellow assigned, green completed, grey cancelled.
Nothing more on day one. The map, the statistics, the reports and the phone system can wait — the dispatcher will not need them for a week and right now they would only overwhelm.
The questions people ask most
"Where do I see who I gave the ride to?" In the Driver column, in the overview. And when the driver confirms it on their phone, the label changes by itself.
"What if the customer does not answer?" Cancel the ride and write three words in the note. After a month those three words add up to a picture of where the money goes.
"Do I have to remember all this?" No. There is Help in the menu, with a picture of every screen. It is written for people, not for IT staff.
Day two: live, with paper at hand
Let the dispatcher spend the first live day entering rides into the application and into the notebook. It sounds redundant, but it is the cheapest insurance: whatever happens, the operation keeps running and in the evening you can check the numbers match.
By day three nobody usually reaches for the notebook.
One thing not to underestimate
Train two people, not one. Not for capacity, but for illness and holidays. A one-person dispatch desk is an operational risk, not a saving — and accounts are free and unlimited, so there is no reason for only one person to know how to use the application.
You can rehearse all five tasks in the demo without registering — choose the dispatcher's view on the landing page.
Running a taxi or senior transport service? Send us a no-obligation enquiry or try the demo.