Case study · London · UK

How Ascot Cars cut Heathrow no-shows 41% and migrated 84 drivers off iCabbi in 8 days.

84 drivers · 91 vehicles · migrated from iCabbi in 8 working days · live since 2025-09.

Ascot Cars is an 84-driver Heathrow + executive operator in west London running TaxiCloud since September 2025. They migrated off iCabbi in 8 working days, cut Heathrow T5 no-shows 41% in the first quarter on TaxiCloud, and lifted meet-and-greet revenue 22% by closing a billing leak that iCabbi's flat workflow had hidden for three years.

  • −41%

    Heathrow T5 no-shows

    FlightAware live ingest reshuffles ETAs automatically.

  • +22%

    Meet-and-greet revenue

    M&G now bills as first-class Stripe line item.

  • −18%

    Dispatcher overhead

    AI Copilot drafts flight-slip SMS and reroutes.

The migration

How Ascot Cars migrated off iCabbi.

Ascot Cars runs out of Hounslow with a fleet that splits roughly two-thirds Heathrow + Gatwick airport transfers and one-third executive corporate accounts. The fleet sat on iCabbi for six years before the migration. Their dispatch lead Sarah Patel describes the breaking point as a 2025 May incident where eight Heathrow T5 pickups were missed in a single afternoon during a BA flight reshuffle — iCabbi had no flight-ingest awareness and the dispatcher manually re-keyed every ETA.

TaxiCloud migration started on a Tuesday, finished cutover the following Wednesday — eight working days. Driver records (84 active, 19 inactive), vehicle records (91), customer accounts (4,200), pricing rules (37 airport tariffs across LHR, LGW, STN, LCY), and historic bookings (180-day window) all imported. Driver app rolled out terminal-by-terminal: LHR drivers first day, then LGW, then PHV daily contracts. Sarah's team kept iCabbi live for the first 4 days as a safety net; the safety net was not needed.

First quarter on TaxiCloud: 41% reduction in Heathrow T5 no-shows (FlightAware live ingest reshuffles ETAs automatically when flights slip), 22% lift in meet-and-greet revenue (every M&G now bills as a first-class line item via Stripe — previously dispatchers were forgetting to add it), and 18% reduction in dispatcher overhead (AI Copilot now drafts the BA124-slipped-40-min SMS automatically). Sarah's team has scaled from 4 dispatchers to 3 with no service degradation.

We spent six years on iCabbi. Eight days on TaxiCloud and the dispatch board paid for itself in recovered meet-and-greet billing alone. The flight-ingest is the difference between an ops floor that fights fires and one that prevents them.

Sarah Patel

Dispatch Lead, Ascot Cars

Frequently asked

Questions about the Ascot Cars migration.

  • How long did the iCabbi → TaxiCloud migration take Ascot Cars?

    Eight working days from migration kickoff to full cutover. Drivers, vehicles, customers, pricing rules, and a 180-day historic booking window were imported. Ascot kept iCabbi running in parallel for the first four days as a safety net, but did not need to fall back.

  • What measurable results has Ascot Cars seen?

    First quarter on TaxiCloud: Heathrow T5 no-shows down 41%, meet-and-greet revenue up 22%, dispatcher overhead down 18%. The fleet has scaled from 4 dispatchers to 3 without service degradation.

  • Did Ascot Cars need to retrain drivers on the new system?

    Driver app onboarding took roughly 15 minutes per driver. The migration team rolled out terminal-by-terminal: LHR drivers first day, LGW drivers second day, daily PHV contracts third day. No driver attrition was attributed to the migration.

  • How does TaxiCloud's flight ingest work for an LHR fleet?

    FlightAware data feeds every airport-tagged booking. When a flight slips, the dispatch board reshuffles ETAs automatically, AI Copilot drafts an SMS to the passenger in their booking language, and the driver's terminal-queue position updates. Dispatchers are alerted only when a manual override is needed.

Ready when you are

Dispatch on autopilot.

14-day free trial. No card. Cancel anytime.

47 fleets joined this month · Talk to sales