Choosing dispatch software is the most expensive decision a small transport operator makes, and the one they research least. A website can be replaced in a fortnight. A dispatch system holds your bookings, your customer list, your driver records and your invoicing history — and once it does, moving is painful enough that most operators simply stop trying.
So it is worth an afternoon of thought. This guide is the questions we would ask if we were buying, in the order they actually matter. If you are new enough to the trade that “dispatch” itself is fuzzy, start with how taxi dispatch actually works — the buying questions below assume you know what the job is.
First, be honest about which business you run
Almost every bad software purchase in this industry traces back to one mistake: buying a tool built for a different kind of work.
There are two fundamentally different operations hiding behind the word “taxi”.
Instant-hail work. Someone wants a car now. The software’s job is to find the nearest free driver and assign the job in seconds. Success is measured in dispatch latency and driver utilisation. Volume is high, margin per job is thin, jobs are interchangeable.
Pre-booked work. Someone books a car for Thursday at 04:30 to catch a flight, or a chauffeur for a full day of client meetings. The software’s job is to hold that commitment reliably for days or weeks, price it correctly, brief the right driver, and never, ever lose it. Volume is lower, margin per job is much higher, and a single failure loses a corporate account.
Systems built for the first case dispatch by proximity and treat a booking as a short-lived event. Systems built for the second treat a booking as a record that lives for weeks, carries a quote, an account, a flight number and a set of instructions. You can force either tool to do the other job, and it will be miserable.
If most of your revenue is airport transfers, corporate accounts, weddings or hourly chauffeur hire, you are in the second category — and most of the “taxi dispatch software” marketed at you was designed for the first.
The seven jobs the software actually has to do
Strip away the feature lists and any system is judged on seven things.
- Capture the booking — from your website, phone, email and WhatsApp, without anything falling through a gap.
- Price it — consistently, including waiting time, extras and account rates.
- Get it to a driver — with the details they need, confirmed, on their phone.
- Keep the customer informed — confirmation, reminder, changes.
- Take the money — card, link, invoice, account, cash.
- Keep the records — because your licence requires it (more on this below).
- Tell you what happened — revenue, routes, which marketing worked.
A system that does five of these brilliantly and two not at all will still cost you the two, every day, forever. Score candidates on all seven.
The questions that separate good from bad
“Where do bookings actually arrive?”
Most operators lose more jobs to fragmentation than to competition. Enquiries arrive by web form, phone, email, WhatsApp and a partner’s forwarded message — and end up in five places. The single biggest operational upgrade available to most firms is not faster dispatch; it is one board where every request lands.
Ask specifically: does the customer’s email thread live inside the booking, or in your inbox? When a customer replies “can we make it 5am instead”, where does that message go, and who sees it?
“What do drivers have to install?”
Driver apps are where adoption goes to die. Every extra step — an app store download, an account, a password, a company email — loses you a driver, and you will re-run that process for every subcontractor and every new starter.
The lowest-friction model is a private link per driver that opens their jobs in any browser, with push notifications, and can be added to the home screen if they want it. No store, no password, no onboarding call. Ask what happens when you take on a driver for one weekend.
“How does pricing scale as I grow?”
UK vendors typically price per vehicle per month, per driver per week, or a flat monthly tier. Entry prices are commonly advertised in the low tens of pounds per vehicle per month, but the number on the pricing page is rarely the number you pay.
Ask about: setup and onboarding fees, minimum contract length, the cost of adding a seasonal driver, per-SMS or per-notification charges, payment processing fees on top of your card rates, and what happens to the price at renewal. A cheap per-vehicle rate with a twelve-month lock-in is more expensive than a higher monthly rate you can leave.
“Whose Stripe account is it?”
If customer payments flow through the vendor’s merchant account and are paid out to you, the vendor controls your cash flow and your chargebacks. If the system connects to your own payment account, you are paid directly and you keep the relationship with your processor. This matters enormously the first time there is a dispute, and it is easy to check before you sign.
“Can I get my data out?”
Ask for an export of bookings, customers and invoices — as a file, on demand, without asking support. If the honest answer is “contact us and we’ll arrange it”, you are not renting software, you are depositing your business with someone. Test the export during the trial, not during the exit.
“What happens when the trip is over?”
The work after the job is where small operators quietly lose money: chasing unpaid invoices, forgetting to ask for reviews, never closing off completed trips. Look for automation that runs without you — a reminder before pickup, a payment nudge on an unpaid invoice, a review request after a completed trip. These are not luxuries; they are the difference between a business that compounds and one that treadmills.
The compliance question most demos skip
If you hold a private hire operator licence in England and Wales, keeping records of your bookings is not an optional feature. Licence conditions issued by your council typically require you to record every booking — including the date and time it was made, the passenger’s name, the pick-up and drop-off points, and the driver allocated — and to keep those records available for inspection by an authorised officer, the police or VOSA, often without notice.
Retention periods vary: many councils require at least twelve months from the last entry, and some require two years or longer. Several councils also specify that records be kept on an approved computerised system, and an operator found keeping poor paper records may be required to move to one.
Two practical consequences:
- Requirements vary by council. There is no single national rule. Check your own licensing authority’s published operator conditions — and if you operate across borough boundaries, check each one.
- Your dispatch system is your compliance system whether you planned it that way or not. A tool that records every booking with a timestamp, the parties, the route and the allocated driver produces your inspection record as a by-product. A WhatsApp group does not.
Ask any vendor directly: can I produce, on demand, a complete record of every booking in a given month with the driver allocated? If the demo cannot do it in under a minute, that is your answer.
Red flags
- A demo that only shows the map. Live vehicle tracking is the easiest thing to make look impressive and among the least important for pre-booked work.
- No written pricing. If you cannot find the price without a sales call, the price depends on what they think you can pay.
- Per-seat pricing for office staff. Your dispatcher, your bookkeeper and you should not each cost extra to look at the same board.
- “Migration is included” with no detail. Ask exactly what gets migrated: bookings, customers, invoices, or just a customer list.
- A roadmap answer to a today question. “That’s coming in Q4” means it does not exist. Buy what is shipped.
How to run the trial properly
Two weeks of poking at a sandbox tells you nothing. Instead:
- Run one real day end to end. Take a genuine booking, price it, assign a real driver, send the confirmation, take payment, close it off.
- Break it on purpose. Change the pickup time by two hours. Cancel and rebook. Reassign the driver an hour before pickup. The gap between systems shows up in changes, not in happy paths.
- Put your least technical driver on it. If they can accept a job without ringing you, it works. If they ring you, it does not.
- Export your data. On day one, not day ninety.
- Count the clicks from “enquiry arrives” to “customer has a confirmation”. That number, multiplied by your monthly job count, is the real cost of the software.
Migrating without losing a week
- Move customers and future bookings first; historical jobs can follow.
- Run both systems in parallel for two weeks, with new bookings only in the new one.
- Keep your old system readable (not necessarily writable) for as long as your licence retention period requires.
- Tell drivers a fortnight ahead, and move them in one batch, not a trickle.
- Do it in your quietest month. Not December.
Our own bias, stated plainly
We build RideDesk, so treat what follows as an interested party’s disclosure rather than a recommendation.
It is built for the second kind of operator in this article — chauffeur, limousine and airport-transfer firms running pre-booked work. That focus shows up in specific choices: every booking, email and WhatsApp message on one board; a driver portal that is a private link with nothing to install; invoicing through your own Stripe account; and a complete, timestamped record of every booking with its allocated driver. It also lets you forward a job you cannot cover to a partner at an agreed cost, with the margin tracked rather than lost in a chat thread.
It is the wrong tool for a 200-car radio circuit doing instant hail, and we would rather say so now than after you have migrated. Unlike the unpublished-quote suppliers above, the pricing is public — a free plan up to 10 transfers a month, then $99 and $199 monthly (USD, as of August 2026, current comparison) — so you can run this article’s own benchmarking advice on us without signing an NDA. If you want to see it against your own workflow instead of a canned demo, get in touch, or read how FrankfurtRide runs on it.
Whichever way you go, judge it against your own seven jobs rather than a feature grid, and be honest about which of the two businesses you actually run — that answer decides more than any comparison table will. And if the real reason the bookings are thin is that nobody is finding you, dispatch is the wrong thing to fix first: start with the website, which is usually the cheaper problem. Before you sign anything, work out what it will actually cost you at your size — we compared the published UK prices, and the gap between suppliers is wider than most operators expect.
