The Dispatch Platform Question: What to Actually Think About Before You Switch

Your dispatch platform touches everything. How drivers interact with jobs, how call handlers process bookings, how customers experience your service, how you report on performance, and ultimately, how much money you make per booking. It's the most consequential technology decision most operators will make.

I've worked across every major dispatch platform in the UK — Cab9, iCabbi, Autocab, and others — at various scales. This isn't a product review. It's what I'd want someone to tell me before making the decision.

The wrong question

Most operators start by asking "which platform is best?" That's the wrong question. The right question is "which platform is best for my operation, at my current scale, with my current team, and where I'm trying to get to?"

A platform that's perfect for a 200-car city operation might be completely wrong for a 2,000-car regional group. A system that works beautifully for airport transfers might be terrible for high-volume street work. There's no universal answer — only the right fit for your situation.

The things that actually matter

When I'm evaluating a platform, these are the areas I focus on — roughly in order of how much damage they do when they're wrong.

Your frontline comes first

This is the big one. Your drivers and call handlers are the people who live inside this system every day. If you make their jobs harder, you lose.

Drivers are your product. If the driver app is clunky, unreliable, or confusing, drivers leave. In a market where retention is already a battle, a bad app is an unforced error. Test the driver app yourself — drive with it for a day. See how it handles in areas with poor signal. See what happens when a driver needs to modify a booking or flag an issue. If it's frustrating for you after a day, imagine using it for a year.

Call handlers convert bookings into revenue. How many clicks does it take to create a booking? How easy is it to modify? Can handlers see driver locations in real time and communicate with drivers without leaving the system? Seconds matter at scale — three extra clicks per booking costs real money when you're processing thousands a day. A good system should make the job feel intuitive, not like an obstacle course.

That said, there's a balance. No system is perfect on day one. Staff adapt, muscle memory builds, and a slightly steeper learning curve can be worth it if the platform gives your team genuinely better tools to work with once they're up to speed.

Auto-dispatch intelligence

The auto-dispatch algorithm is the brain of your operation. How well does it allocate jobs? Does it handle zoning properly? Can it factor in driver preferences, vehicle types, account requirements? The difference between good and bad auto-dispatch can be thousands of pounds per week in a mid-size operation — through reduced dead mileage, better job allocation, and fewer manual interventions.

This is hard to evaluate from a demo. Ask operators already on the platform how much manual intervention their controllers are doing. If the answer is "a lot," the algorithm isn't doing its job.

Reporting and visibility

You can't manage what you can't measure. Can you see booking-level profitability? Driver performance? Account-level reporting? Customer satisfaction metrics? The best operators I know live in their data. A platform that doesn't give you visibility is a platform that's hiding your problems from you.

But don't confuse volume of data with quality of insight. Some platforms will bury you in dashboards that look impressive but don't actually help you make decisions. What matters is whether the reporting answers the questions you're actually asking about your business.

Integration and scalability

Does the platform have a proper API? Can it talk to your accounting system, your compliance platform, your corporate booking portals? A dispatch system that can't integrate with other software isn't modern infrastructure — it's an island.

Scalability is where a lot of operators get caught out. They choose a platform that works perfectly at 150 cars, then hit a wall at 400. Or they buy an enterprise system when they're running 80 vehicles and spend years paying for capability they don't use. Be honest about where you are and where you're realistically going in the next three years.

Choosing a provider, not just a product

The platform is only half the decision. The provider behind it matters just as much.

Look for providers who are still investing. The ones running customer workshops, shipping genuine new features, engaging with their operator base, and actively developing their product. You can tell the difference between a provider that's building and one that's coasting — the coasting ones tend to announce a lot of smoke-and-mirror releases that don't actually change anything on the ground.

Check the forums. Talk to operators. Not the references the vendor gives you — operators you find yourself. Ask them what breaks. Ask about support response times. Ask what they'd change if they could. The vendor demo is the highlight reel. The day-to-day is what matters.

Be wary of lengthy lock-ins. I'm not a fan. If a provider is confident in their product, they shouldn't need to trap you in a multi-year contract to keep you. Some lock-ins are standard in the industry, but if a provider won't let you leave without a fight, ask yourself what that tells you about how they expect the relationship to go.

The migration question

If you're already on a platform and considering switching, the migration decision is ten times harder than the initial choice. You're not just selecting software — you're asking every driver, every call handler, and every account customer to change their habits at once.

Don't migrate unless the current platform is actively losing you money or preventing growth. "The new one is slightly better" is not a good enough reason. The disruption cost — measured in lost drivers, confused customers, and stressed staff — is almost always higher than people estimate.

When we migrated Associated Taxis in Bishop Stortford from Cab9 to iCabbi as part of rolling them into the Take Me group, it went well. Cab9 is a fantastic system — solid team, good innovation — but the move to iCabbi made sense for the group. iCabbi has its quirks, like any platform does. But with the right planning, driver days in the lead-up, and constant communication, the business didn't just survive the migration — it continued to grow.

The lesson from that one: the tools matter, but how you use them matters more. A well-managed migration onto a good-enough platform will outperform a badly managed migration onto the "best" platform every time.

If you do migrate, plan properly. Over-communicate with drivers. Accept that the first month will likely be rougher than what you had before, even if the new system is objectively better. And invest in your frontline — driver days, training sessions, a direct line for issues. The people who have to use the system every day will determine whether the migration succeeds or fails.

The build vs. buy question

Some larger operators consider building their own dispatch technology. I've been involved in build decisions and I'll be direct: unless you have a genuine technical team and a unique operational requirement that no existing platform can serve, don't build.

The maintenance burden alone will consume you. Dispatch technology requires constant updates — new regulations, new integrations, OS updates for driver apps, payment processing changes. Commercial platforms spread that cost across hundreds of operators. You'd be bearing it alone.

The exception is at massive scale with a genuinely different operational model. But even then, think hard about whether a custom configuration of an existing platform gets you 80% of the way there. That last 20% of bespoke capability is rarely worth the cost of owning the whole stack.

The bottom line

Every platform migration will involve pain. Even well-planned ones. The question isn't how to avoid the pain — it's whether the move is worth it.

Pick a platform that makes your frontline's life easier, not harder. Pick a provider that's still building, not coasting. Talk to real operators, not just salespeople. And if you're going to move, commit to it properly — half-hearted migrations fail every time.

The best dispatch platform is the one your drivers actually want to use, your staff can work quickly in, and your provider is still actively making better. Everything else is detail.