Skip to content
Talk to Us

Solutions

Taxi and private hire dispatch software for the UK

UK taxi and private hire operators need dispatch software that carries account customers, booking records and phone bookings across in planned steps. eCabs Technologies gives you corporate accounts and invoicing, a keyboard-first call-centre screen, your own branded passenger app and a staged migration planned around your operation.

What UK operators need

  • Account customers. Corporate accounts with their own prices, travel policies, live ride tracking and consolidated invoicing.
  • Phone bookings. A keyboard-first call-centre screen where agents book in under 15 seconds, in the same dispatch as app and web orders.
  • Your own brand. A white-label passenger app and web booking in your name.
  • Records. Every trip, with route, price, driver and vehicle, is recorded and exportable.

Switching from another UK system

Whether you are on Autocab, iCabbi, Cab9, Cordic, Sherlock or an older server-based system, the switch follows a staged model built around your operation: discovery, setup, training, a pilot with a small driver group, then expansion in batches, with your current system live until the agreed cutover. Volt in Sofia, Bulgaria, migrated from Sherlock to eCabs Technologies.

In the UK

eCabs Technologies launched in Bristol in 2025 with the local ride-hailing service Like a Ride.

Your migration blueprint

Every stage is a decision, not a date.

Shaped by our own migration at eCabs Malta between 2017 and 2019: an adaptable framework, set out in a blueprint built around your operation. Our team leads the work, each stage ends with a joint review, and dates are agreed after discovery.

  1. 01UnderstandYour operation, in detail
  2. 02Launch-critical gapsScope what launch needs
  3. 03ConfigureSet up and test
  4. 04OnboardDispatchers and drivers, in phases
  5. 05Test in parallelA pilot, side by side where appropriate
  6. 06Rider appReleased in phases
  7. 07Go liveAn agreed cutover
  8. 08HypercareSupport and stabilise

Throughout: where it is appropriate, your current system keeps running as the fallback until the agreed cutover.

See the Migration Framework

FAQ

Questions operators ask

Can we switch from Autocab, iCabbi, Cab9 or Cordic?

Yes. Whatever UK system you run today, the switch follows the same staged model: discovery, setup, training, a pilot with a small driver group, then expansion in batches, with your current system live until you decide to cut over.

Can we switch dispatch systems without disrupting our operation?

That is what the plan is built around. Your current system keeps running underneath every stage until you decide to cut over, so phones, bookings and drivers always have a working system.

Will we lose phone calls on the day we switch?

No. Phone numbers and call handling are planned as their own step, and your current system keeps taking calls until the agreed cutover. Phone bookings then run in the same dispatch as app and web orders.

How do we avoid double bookings while two systems run?

Before the pilot, we agree exactly which bookings and which drivers each system handles, how availability is shared, and what the fallback and escalation steps are at each stage.

Next step

Talk to us about your operation

Bring us your operation, your rules and your requirements, and we’ll work through how to deliver the solution with you: what is available today, what we configure and what we build before your launch. No technical background needed, and no commitment.

  • A plan built around how you work, not a one-size-fits-all package
  • Your current way of working keeps running while each step is tested
  • Honest answers, including what we need to find out first
Add details (optional)

Diese Seite gibt es auch auf Deutsch

This site is also available in German.

Möchten Sie zur deutschen Startseite wechseln?
Would you like to go to the German homepage?

Auf Deutsch wechseln