Taxi dispatch software
Dispatch software is the system that takes a booking from wherever it arrived — your website, a phone call, WhatsApp, a marketplace partner — and gets it to a driver with everything they need to complete it. Everything else a platform sells you is downstream of doing that reliably.
That sounds simple until you run it. The hard parts are the ones nobody demos: what happens when a driver declines at 23:40, how a price gets checked before it becomes a promise, whether the customer is told the same thing your driver was told, and whether you can answer "who paid what" three months later without opening a spreadsheet.
What dispatch software actually replaces
Most operators do not start with software. They start with a phone, a WhatsApp group and a notebook, and that combination works remarkably well up to roughly the point where one person can hold the whole day in their head. The failure mode is not dramatic — it is a slow increase in the number of things only one person knows.
Dispatch software replaces the notebook first: one record per job, with the pickup, the passenger, the price and the driver all attached to it. It replaces the WhatsApp group second, by giving each driver their own view of only their own jobs. Everything after that — invoicing, reminders, reporting — exists because the job records are now structured enough to build on.
This is why "we already use WhatsApp" is a real answer for a two-car operation and a bad one for a twelve-car operation. The question is not whether the tool is capable, it is whether the knowledge lives in a system or in a person.
The job, as your dispatcher sees it
One record holds the passenger, the route, the flight, the assigned driver and the money — so nothing about the ride lives in somebody’s phone.
Airport transfer · today
M. Weber · 2 pax
Frankfurt Airport (FRA) · T1
Hotel Jumeirah, Thurn-und-Taxis-Platz
Thomas S.
Accepted · 4 min ago
Every way work reaches you
Website, widget, WhatsApp, Instagram and Messenger, Telegram, live chat, email, phone and marketplace partners — all landing in the same place.
The capabilities that change a working day
Every vendor lists these. The difference is in the detail, so here is what each one means when it is done properly.
A booking state machine, not a status field
A job should move through defined states — pending, approved, driver assigned, confirmed, completed — with rules about which transitions are allowed. The valuable constraint is requiring a driver to actually confirm rather than assuming they saw the message. A status somebody types in is a note; a status the system enforces is a guarantee.
Server-side pricing you can audit
The price should be calculated from your own rate card on the server, not accepted from whatever the website posted. That means distance and hourly rates per vehicle class, fixed prices for named routes, and surcharges for short notice or specific dates — all recomputed and checked before a booking is accepted.
A driver view that needs no app store
Drivers churn, and a per-driver login is administrative overhead you will feel. A private link per driver that opens their jobs on any phone removes onboarding entirely — no passwords to reset, no app to install, no version to chase. It should still let them confirm, decline, and see the passenger and flight details.
Live flight status on airport jobs
Airport work is the segment where dispatch software earns its money, because the pickup time is a guess until the flight lands. A system that tracks the flight number and shows the actual landing time — with terminal and gate where the data source provides them — stops your driver waiting two hours for a diverted flight.
Payment attached to the booking
A hosted payment page per job, card and bank and wallet, with the booking summary on it so the customer can pay without hunting for the email. The important part is that settling a payment updates the booking, so "is this paid?" has one answer rather than one per system.
Invoices that survive an audit
Consecutive numbering that never rewinds, the seller and buyer identities on the document, VAT shown correctly, and a void path rather than a delete path. In Germany this is a legal requirement under §14 UStG; everywhere else it is what your accountant will ask for anyway.
The messages the job generates
Confirmations, driver details, payment links, reminders and review requests, in the customer's language, from your address rather than the vendor's. Every one of those is a message somebody currently types by hand.
Outsourcing as a first-class flow
Nobody covers every job with their own cars. Forwarding a booking to a partner at an agreed margin — and tracking what you owe them — is a normal part of the work, and it should be in the system rather than in a side conversation.
Priced by your rate card, on the server
The route is measured once and every vehicle class is priced from your own rates, so no channel can quietly undercut you.
Priced live from your own rate card · fixed, no surprises
A payment page per booking
Your own Stripe, PayPal or SumUp account, the full booking summary on the page, and a compliant invoice behind it.
How a booking should move
A concrete walkthrough, because "workflow automation" means nothing until you see the sequence.
- 1
The request arrives and is priced
A customer completes the form on your site. The server measures the route once, prices every vehicle class from your rate card, applies any surcharge or early-booking discount, validates a voucher if one was used, and stores the result. The price the customer sees is the price the system will honour.
- 2
It is checked before it is accepted
The booking is recomputed against the stored quote. If the figures agree, the pickup is inside your service area and it is far enough ahead, it can approve itself. If any check fails it stays pending with the reason attached — a failed check should never reject a customer, it should ask a human.
- 3
A driver is assigned and confirms
You assign a driver or forward the job to a partner. The driver gets a link, opens their jobs, and confirms. Until they do, the booking is not confirmed — which is the whole point, because an unread message is not a commitment.
- 4
The customer is told, once
One confirmation with the driver, the vehicle and the pickup. If you take payment by link, it goes with it. If you take cash, the customer can confirm by signing on a page instead. Either way the customer hears one version of events.
- 5
It completes and settles
The ride finishes, the invoice carries a real number, the payment is recorded against the booking, and the cash a driver is holding shows on their balance until it is settled. Three months later the record still answers the question.
Rentals, with the paperwork attached
Day rates and duration discounts, included kilometres, condition at handover and return, and an agreement the customer signs.
4 d
Period
€ 149/d
Rate
−10%
Long-stay
Your brand, your domain
Your colours, your logo and your sending address, on a hostname you own. Customers never learn what software you run.
Booking page, panel & emails — 100% your brand, none of ours
What to check before you commit
Ask these in the demo. The answers separate systems that were designed for this work from systems that were adapted to it.
Can you leave, and take your data with you?
Ask specifically how you export bookings, customers and invoices, in what format, and whether you can do it yourself without asking support. A vendor who has thought about this will answer immediately.
Whose brand is on the customer emails?
If the confirmation says the vendor's name, every ride you sell is marketing for them. Check whether emails send from your own domain with your own logo, and what that costs.
What happens when a price is wrong?
A system that accepts whatever the website sent will happily book a €12 airport transfer. Ask whether prices are recomputed server-side and what the system does when the figures disagree.
Is the driver experience an app?
App installs are a real cost when drivers turn over. Ask what a new driver has to do before their first job, and time it.
How does it handle the jobs you send out?
If subcontracting is not modelled, you will track margins in a spreadsheet forever. Ask to see a job forwarded to a partner and the resulting ledger.
What is the real price at your size?
Per-vehicle pricing and per-booking pricing behave very differently as you grow. Work out the cost at your current volume and at double it before you sign.
How a booking moves
Arrive, get priced, get a driver, get confirmed, get paid — the same path whichever channel it came from.
Sign up & make it yours
Create your organization, set your rate card, connect your domain and drop in your logo and colour.
Take bookings everywhere
Point your website at RideDesk, plug in the API, forward marketplace jobs, or add them by hand.
Dispatch & get paid
Approve, assign a driver or partner, send the pay link, and let the automations handle the rest.
What comes with it
The capabilities that turn a booking list into a business you can run from one screen.
Built-in CRM
Every booker becomes a customer record — history, documents, billing details, lifetime value.
Two-way inbox & WhatsApp
Reply to customers by email or WhatsApp from inside each booking. No separate app.
Live flight status
Airport pickups track the flight automatically — delays surface before the driver leaves.
Bookable by AI agents
A per-tenant MCP endpoint lets AI assistants get a quote and book — priced by your rules, never theirs.
Quote-to-booking analytics
See what visitors entered, which class they picked, and where they dropped off the funnel.
Automations & reminders
Confirmations, driver reminders, payment chasers and a morning digest — on autopilot.
The feature list is not the product
Two systems can both claim dispatch, invoicing and a driver app, and be completely different to run. What separates them is whether the parts know about each other — whether marking a payment updates the booking, whether cancelling refunds the card, whether the invoice number came from the same sequence as last month. Judge the seams, not the list.
Frequently asked questions
What is taxi dispatch software?
It is the system that receives bookings from every channel you sell through, prices them, assigns them to a driver or a partner, tells the customer what is happening, takes payment and keeps the record. Older systems focused mainly on radio-style allocation of immediate jobs; modern ones cover the whole lifecycle of a pre-booked ride, which is where most chauffeur and transfer work sits.
How is it different from a booking system?
A booking system faces the customer and captures the job. Dispatch faces your operation and gets it delivered. Most platforms now do both, but they usually started at one end, and it shows — a booking-first product tends to have thin driver tooling, and a dispatch-first product tends to have an ugly booking form.
Do I need it if I only have three cars?
Probably not for allocation — you can hold three cars in your head. You might still want it for everything around the ride: quotes that do not need writing, confirmations that send themselves, invoices that are numbered correctly, and payment links. Most small operators adopt software for the paperwork long before they need it for dispatch.
Does it replace a phone system?
No. It replaces the notebook next to the phone. Calls still come in; the difference is that the job gets recorded once and everything downstream reads from that record.
Can it handle pre-bookings and airport transfers rather than street work?
That depends heavily on the product. Systems built for hailing and immediate dispatch treat a booking three weeks out as an edge case. If most of your work is pre-booked airport and corporate transfers, check that flight tracking, meet-and-greet handling, return journeys and quote validity are properly modelled rather than bolted on.
How long does it take to move over?
The software side is usually days, not weeks. The real work is your rate card — deciding your per-kilometre and hourly rates by vehicle class, any fixed route prices, and your surcharge and cancellation rules. Operators who already know those numbers move quickly; operators who have been quoting by feel find that this is the part that takes the time.
What does it cost?
Pricing models vary too much for a useful single number: per vehicle, per user, per booking, or a flat monthly fee, sometimes with setup and payment-processing charges on top. The two things worth doing are calculating the total at double your current volume, and asking what is included versus sold as an add-on.
Will it work with the website I already have?
It should. Look for embeddable booking forms that drop into an existing site, and a documented API if your site is custom-built. Being forced onto the vendor's website template is a warning sign — it usually means the booking flow cannot be separated from their hosting.
What about marketplace jobs from partners like Uber or Blacklane?
Those are dispatch jobs, not customer relationships — the marketplace owns the passenger, bills them and settles with you separately. A system that understands the difference will let you allocate and track the ride without generating customer emails, payment demands or invoices against a passenger who is not yours.
Is my data safe if the vendor is small?
Ask where data is hosted, whether there is a data processing agreement, how backups work and how you get an export. Under GDPR you need a DPA with any processor handling your passengers' data, and a vendor who cannot produce one on request has not done the work.