Azur Transfers

The 2AM Problem

Every delayed red-eye meant a dispatcher awake at 2am re-shuffling drivers by phone. Bookings arrived by email, Instagram DM, hotel concierges and two OTA channels, and none of them talked to each other. Drivers found out about changes when they called in. By August, no-show pickups peaked at 9% and the refunds were eating the margin the season was supposed to build.

A Booking Engine That Quotes Instantly

We built a guest-facing booking flow embedded on their site: pick a zone, a vehicle class and enter a flight number, and get a fixed price immediately. The flight number is the important part — it ties the reservation to live flight data from the moment it is made. Payment, multilingual confirmations and deep links for hotel partners are all part of the same flow.

The Dispatch Board

The heart of the ERP is a live dispatch board: every ride for the next 24 hours in a single column view, colour-coded by status. Dispatchers drag rides onto drivers, and conflicts — overlapping jobs, wrong vehicle class, a driver out of hours — are blocked before they can happen. When a flight slips, the system reads the carrier feed and moves the pickup itself, notifying the driver and the guest without a phone call.

Dispatch Features

• 01

  Live flight tracking shifts pickups on delay or early arrival.

• 02

  Drag-and-drop driver assignment with conflict prevention.

• 03

  Driver app with day sheet, navigation handoff and one-tap status updates.

• 04

  Automated WhatsApp messages carrying driver name, plate and live pickup time.

The Impact

Azur ran the following high season with the same dispatch team and 30% more rides. Missed pickups fell below 1%, and the owner stopped sleeping with the phone on loud.