Taxi Dispatch Software for UK Operators

The short answer

The cheapest option is not the one with the smallest headline price. It is the one whose cost stays flat as you grow. Most dispatch platforms price in one of three ways:

• Per vehicle, per month — your bill rises with every car you add
• Per job / commission — your bill rises with every fare you take
• Flat licence — the price stays the same however busy you get

Why per-job pricing is rarely cheap

A per-job fee looks small. At £0.30 a job it sounds like nothing.

Run the numbers for a small operator doing 40 jobs a day:

| Pricing model | Monthly cost at 40 jobs/day | | --- | --- | | £0.30 per job | ~£360 | | £2 per vehicle, 3 vehicles | £6 | | Flat licence | £17 |

The per-job model is roughly twenty times the flat licence at that volume — and the gap widens every time you get busier. That is the trap: the "cheap" option is cheap only while you are quiet.

What actually makes software expensive

• Per-job fees — scale against you
• Per-driver charges — punish you for growing the fleet
• Setup fees — a one-off sting that never buys anything again
• Locked contracts — paying for months you do not use
• Add-on modules — booking and dispatch sold separately

What a cheap option should include

A genuinely low-cost system still needs to do the job. At minimum:

• Instant online quotes calculated from your own rates
• A bookings screen where jobs are recorded and confirmed
• Payment handling, so money is tracked against the job
• Cloud access, so there is no server to maintain
• No per-job or per-driver caps

Our pricing

Our licences start at £17 per month and are flat — no per-job fee and no charge per driver, so the price you pay does not change as your workload grows. There is also a one-time purchase option if you would rather not pay monthly.

See pricing for the current tiers, or try the demo to see the system working before you decide.

The honest summary

If you do very few jobs, a per-job model may cost less in month one. If you intend to grow, a flat licence is almost always cheaper within a few months — and you avoid the situation where being successful makes your software unaffordable.

In one sentence

Taxi dispatch software decides which driver does which job, and tracks that job from the moment it is booked until it is completed.

What it actually does

Strip away the marketing and dispatch software handles four things:

1. Records the job — who, where, when, how many passengers, what price
2. Assigns it — either manually by a controller, or automatically to the nearest available driver
3. Tracks progress — scheduled, en route, on the ride, completed
4. Keeps the history — so you can look back at what was done, by whom, and what was paid

How it differs from booking software

These get sold as if they were the same thing. They are not.

| | Booking software | Dispatch software | | --- | --- | --- | | Takes the request | Yes | No | | Prices the fare | Yes | No | | Takes payment | Yes | No | | Assigns a driver | No | Yes | | Tracks the job | No | Yes |

An operator needs both. Buying them as two separate products is how businesses end up with two job lists that disagree with each other — which is why this system keeps them on one record.

What to look for

• Automatic pricing — fares worked out from distance and your rates, not typed in by hand
• A clear job status — so nothing is forgotten in a busy period
• Cloud access — no office server, and the same job list visible to everyone
• Driver assignment — manual is fine for a small fleet; automatic matters as you grow
• No per-job fees — so growth does not penalise you

Related reading

• How to choose the best taxi dispatch software
• Taxi booking and dispatch software: why you need both
• Cloud based taxi dispatch software explained

Or see the dispatch and booking system working on the live demo.

What automated dispatching means

Automated dispatching removes the human decision from job allocation. Instead of a controller looking at a screen and choosing a driver, software applies a rule and assigns the job itself.

How the decision is made

An automated system typically considers some combination of:

• Proximity — which driver is closest to the pickup
• Availability — who is currently free rather than on a job
• Vehicle suitability — does the car seat the party and carry the luggage
• Fairness — rotation, so the same drivers are not favoured
• Priority — airport runs or account customers taking precedence
• Shift position — drivers nearing the end of a shift getting fewer jobs

The rules are configurable. Most systems let you weight these differently depending on whether you value speed, fairness or cost.

Where it clearly wins

• Peak volume — the moment it gets too busy for one controller to keep up
• Out of hours — jobs assigned at 3am with nobody in the office
• Consistency — every job allocated by the same logic, so no accusations of favouritism
• Speed — seconds rather than minutes between booking and assignment

Where a human still wins

• Awkward jobs — the airport run with six bags and a wheelchair
• Local knowledge — the driver who knows the road is closed
• Difficult customers — where a judgement call is needed
• Genuine exceptions — anything the rules did not anticipate

The practical answer for most small operators is automatic assignment with manual override — the software does the routine 90%, and a controller can take over when the job is unusual.

The honest limitation

Automated dispatching depends on knowing where your drivers are. That means it only works properly once you have live driver location, which usually means a driver app.

Without that, "automated" dispatch is really just rule-based assignment based on static information. It is still useful — but it is not the same as real-time proximity allocation, and you should ask a supplier which one they actually mean.

What this system does today

Booking, pricing and job records are complete and in production. Driver assignment, live tracking and the driver app are on the same job record and are being built next — so the data model is already in place rather than being retrofitted.

See the booking and job records working on the live demo, or read what taxi dispatch software does.

The short answer for cloud software

With a cloud based system there is nothing to install on your own computers. No server in the office, no disc, no IT visit. You log in through a web browser.

That removes the part most operators dread. What is left is configuration.

What you actually need to set up

1. Your fare structure (the biggest job, roughly an hour)

• Base fare per vehicle type
• Price per mile bands
• Stop charges
• Return trip discount
• Any extras — meet and greet, baby seats, airport fees

Get this right first. Everything else depends on it, and it is what makes quotes accurate.

2. Your vehicle types

List the classes you run — saloon, estate, eight-seater — with seat and luggage capacity, so the calculator only offers what can take the job.

3. Your service area and routes

Which towns you cover, and the key routes you price regularly.

4. Payment settings

Connect your card provider if you want to take payment online at the time of booking. Cash bookings need no setup.

5. Staff accounts

Who can see what. A controller needs the bookings screen; they do not need access to pricing.

6. Add the booking form to your website

If you already have a site, the form and quote calculator are embedded into it. If you do not, we build the front end.

How long it takes

| Step | Typical time | | --- | --- | | Fare structure | 1–2 hours | | Vehicle types and service area | 30 minutes | | Payments | 30 minutes | | Staff accounts | 15 minutes | | Website integration | Hours, if you need the form adding |

Realistically: an afternoon of configuration, not a week-long IT project.

What you do not need to do

• Buy a server
• Install anything on office PCs
• Assign an IT contractor
• Take the system offline during setup

Before you start

Have these to hand:

• Your current price list, including any rates that are not written down
• A list of your vehicle classes
• Which members of staff need access, and to what

The one caveat

If you use a self-hosted or on-premise dispatch system, this does not apply — those genuinely do require installation, a server, backups monitoring and someone to maintain it. That is the trade-off you accept in exchange for keeping data entirely in-house.

Cloud based systems avoid that work. If you are weighing the two, see cloud based taxi dispatch software explained.

Ready to see it? Open the live demo — it is the real system, already configured. Or get in touch and we can walk through your fare structure together.