Airport work. The flight moves the pickup, and the driver knows.
Kairo watches every arrival with a flight number, moves the pickup to the live landing time plus ten minutes, and tells the driver. Departures are watched and never moved.
The flight rules, as coded.
Every number below comes from the sweep that runs every 15 minutes. None of them is a setting yet, so what you read here is what every operator gets.
Checked every 15 minutes
Every 15 minutes Kairo sweeps the jobs with a flight number, a pickup in the next 24 hours, a confirmed time and a status other than completed or cancelled.
Closer flights are polled more often
A flight is looked up on every sweep once the pickup is within three hours or the aircraft is airborne. Further out, it is checked at most every 55 minutes. Once it has landed and the arrival time is stored, the checks stop.
Live arrival plus ten minutes
The new pickup is the live arrival time plus 10 minutes. Live means actual if known, else estimated, never the published schedule. It is never set earlier than two minutes from now, and nothing moves unless the change is 15 minutes or more.
Up to six hours later, or 30 minutes earlier
A move of up to six hours later or 30 minutes earlier on the same calendar day at the airport is applied on its own. Anything bigger is written to the job as an advisory for review and the pickup is left alone.
The driver is told. The passenger is not.
When the pickup moves, the assigned driver gets a push and the job-updated message, and the activity feed records the change for the office. The passenger receives no message. Their tracking page shows the new time.
Cancelled or diverted flights are flagged, never moved
A cancelled or diverted flight is written to the job and left for a person to decide. Its live arrival is for the wrong airport, so it is never used to move the pickup.
Departures are watched, not moved
For a drop-off at the airport, Kairo watches the outbound flight for the 12 hours before pickup. A cancellation logs contact customer before dispatch. A delay of 60 minutes or more logs an advisory, repeated only when it crosses another whole hour. Check-in times do not move with a delayed flight, so the pickup does not either.
A drop-off pickup is suggested at departure minus two hours
When you enter an outbound flight on a drop-off, Kairo suggests leaving so the passenger reaches the terminal two hours before departure, less the drive time, or three hours before departure when the drive time is unknown, rounded down to five minutes. You apply it or not.
The wrong flight number is caught
An outbound flight number entered on an airport pickup is detected. Kairo tries the paired inbound number and tracks that if it matches with high confidence. Otherwise it writes an advisory and changes nothing.
A time you set stays set
If you move a pickup back after Kairo adjusted it, the same landing time is not applied again. Only a new arrival estimate lifts that. The original time is kept on the job and every move is logged.
The booking form suggests the landing time
While you type a booking, the form looks up the flight and offers the landing time when it differs from the pickup you entered by 5 minutes or more. The suggestion is the landing time itself, without the 10 minute buffer the sweep adds.
Two data providers
Flight data comes from AeroDataBox by default, with AviationStack as the fallback when the key is missing or the quota runs out. Lookups are cached for five minutes and spaced 1.1 seconds apart.
One board for the day's arrivals.
The airports board lists today's flights against their pickups and refreshes itself every five minutes, so the office sees a delay without opening each job.
The Driver App shows the live flight on the job, and the iOS Lock Screen activity updates when the status or terminal changes.
- Board refreshes every five minutes
- Flight status, terminal and airline written to the job
- Original pickup time kept beside the moved one
What the legacy tools do instead.
Our comparison research recorded how each system is sold and priced. It did not test how any of them handles a flight delay, so this page makes no claim about that.
Each line below is taken from the comparison page it links to, where the vendor's own pages are listed as sources. Those pages also say what each system does well.
- iCabbiComparison row: Per-mile + per-minute tariff engine. Research checked 6 September 2026.
Not described as per-mile plus per-minute chauffeur pricing. Their pricing model is built in taxi terms: fixed rates, zone surcharges, council-regulated time changes and fixed-fare airport runs.
Read the full comparison - DeverResearch checked 6 September 2026.
Dever Software sells DISPATCH, a generalist ground-transport platform that covers chauffeur and limousine work alongside private hire, airport, cruise and ferry transfers and courier work. It has been trading since 2013, leads on breadth and simplicity rather than any single technology story, and promises no contracts and no limits on drivers, vehicles, customers or bookings, at a monthly price it does not publish. It is a genuinely deep, mature system for an operator who wants one tool across several kinds of ground transport work, not chauffeur alone.
Read the full comparison
What to know before you rely on it
Flight tracking is on every plan, Starter included. The same-day check assumes UK airports, and there is no per-terminal buffer: the 10 minutes is fixed and is not a setting.
Put a real flight number on a booking.
The trial tracks flights from the first booking you enter.
Start free trial