Airport taxi dispatch software
Airport work looks like the easiest job a fleet takes and behaves like the hardest. The pickup point is fixed, the route is familiar, the fare is predictable — and then the flight lands forty minutes early, or three hours late, or at a terminal nobody expected, and every assumption the booking was built on is wrong.
On this page
- Why the airport is a different dispatch problem
- Every way work reaches you
- What flight tracking has to do to be worth having
- Priced by your rate card, on the server
- The day, on one board
- A payment page per booking
- Where airport work differs from street work
- Rentals, with the paperwork attached
- What happens when the flight moves
- Your brand, your domain
- The parts either side of the flight
- How a booking moves
- Questions that separate airport-capable systems
- What comes with it
- What flight tracking does not do
- Frequently asked questions
That is the whole difference. Ordinary dispatch assigns a driver to a time. Airport dispatch assigns a driver to an event nobody controls, and the software's only real job is to notice that the event moved before your driver is standing in arrivals texting a passenger who landed at a different gate an hour ago.
Why the airport is a different dispatch problem
The scheduled time on an airport booking is not a fact, it is a forecast. A transfer booked for a 14:30 pickup because the flight is due at 14:00 is really a booking for "forty minutes after the wheels touch down", and those are the same thing only on the days when nothing happens. Any system that stores the first and not the second is storing the wrong number.
Three things move when the flight moves, and most products model only the first. The driver's departure time changes. The waiting time you are entitled to bill changes, because it runs from the actual landing rather than the timetable. And the customer's expectation changes — they are the one person who already knows the flight is late, and they are watching to see whether you know too.
The second structural difference is that airport work is pre-booked, often weeks ahead. Products built for street hailing treat a booking three weeks out as an edge case: the queue, the nearest-available-car allocation and the meter are all designed for a job that exists because somebody wants a car now. None of that machinery helps a transfer desk, and quite a lot of it gets in the way.
The third is that the passenger is frequently not the payer. Corporate accounts, hotels, tour operators and marketplaces all book on behalf of somebody else, which means the ride, the customer relationship and the invoice can point at three different parties. A system that assumes the person in the car is the person being billed will make you correct it by hand, on every job, forever.
Every way work reaches you
Website, widget, WhatsApp, Instagram and Messenger, Telegram, live chat, email, phone and marketplace partners — all landing in the same place.
What flight tracking has to do to be worth having
Every vendor lists flight tracking. The distance between a checkbox and something that changes your day is entirely in these details.
The scheduled time and the revised time, kept apart
The timetabled arrival is one field; the actual-or-estimated time is another. A system that overwrites the first with the second loses the ability to tell you how far the flight has moved, which is the number the decision actually turns on. Both are stored, local to the airport rather than to your office, and the difference is shown signed — negative when the flight is early, which is the case that catches drivers out.
Changes pushed to you, not polled for
Polling a flight every ten minutes is expensive and still late. RideDesk registers a webhook subscription per flight number it is holding a booking on, and the data provider posts the whole record the moment anything about that flight changes. The update arrives when the change happens rather than at the next poll — and holding a subscription costs nothing, so watching a flight is not something you have to ration.
Terminal, gate, belt and desk
Arrival terminal, gate, runway touchdown time and baggage belt where the feed provides them; check-in desk on departures. The baggage belt is the field drivers actually use, because it is the difference between meeting somebody and sending "I am here" four times from a car park.
Data you can tell apart from a guess
Not every flight has a live feed behind it. Each status carries its own quality marker — genuinely live, or timetable data only — so a dispatcher can see whether the time on screen is being reported or merely scheduled. The provider's experimental prediction field is shown as a hint and is never allowed to raise an alert. A system that presents all three identically is training you to trust the wrong one.
Alerts for disruption, not for noise
A delay, cancellation or diversion on one of today's bookings raises an alert by email and push notification to whoever on your desk is set to receive it. A flight sliding by four minutes does not. The suppression is deliberate and it is the point: an alert channel that fires on everything is one that people stop reading, usually a week before the job it existed for.
One lookup serves every booking on the flight
Flight data is cached against the flight number and date and shared across the whole platform, so twelve bookings on the same inbound cost one lookup rather than twelve. It is an unglamorous detail that decides whether tracking every job is something you do or something you budget for.
A board you can put on the office wall
The dispatch board runs fullscreen on a spare screen with the display kept awake, so the day's airport jobs and their current flight states are readable across the room without anybody refreshing anything. For a desk running twenty inbound flights a day, that is the difference between checking and knowing.
The driver gets what they need, without an app
Each driver opens a private link on any phone — no app store, no password, nothing to install when a driver changes handset. Their view carries the flight number, the passenger and the pickup. The live status and the disruption alerts sit with the dispatcher, deliberately: they are the person who can re-plan a day, and a driver who is already on the road is not.
Priced by your rate card, on the server
The route is measured once and every vehicle class is priced from your own rates, so no channel can quietly undercut you.
Priced live from your own rate card · fixed, no surprises
The day, on one board
Every job in one live view with its state, its driver and — on airport work — the flight it depends on. It is the screen a transfer desk actually lives in, and it is the reason the flight data is worth collecting: a status nobody can see at a glance may as well not have been fetched.
M. Weber · 2 pax
FRA T1 → HOTEL JUMEIRAH, FRANKFURT
LH 402 · on time · Business Van
THOMAS S. · Accepted · 4 min ago
€ 89.00
Paid
A payment page per booking
Your own Stripe, PayPal or SumUp account, the full booking summary on the page, and a compliant invoice behind it.
Where airport work differs from street work
If you are comparing a product built for hailing against one built for transfers, this is the axis that matters. Feature lists rarely show it.
| Street and immediate work | Airport and pre-booked work | |
|---|---|---|
| The pickup time | Now. The job exists because somebody wants a car in the next few minutes. | A derived time — an offset from an arrival that has not happened yet and will almost certainly move. |
| How a job is allocated | Nearest available car, decided by the system in seconds. | A named driver assigned days ahead, who has to confirm, and who may need replacing when the flight changes. |
| What the customer bought | A ride. | A guarantee that somebody will be waiting whenever they finally get through the terminal. |
| Where the price comes from | A meter, settled at the end. | A quote given weeks earlier that you are now held to — which is why it has to be computed and stored rather than estimated. |
| Who pays | The passenger, in the car. | Often not the passenger: a company account, a hotel, a tour operator or a marketplace, invoiced later. |
| The expensive failure | An empty car driving to a job that already cancelled. | A driver at the wrong terminal two hours after a diverted landing, and a passenger in somebody else's car. |
Rentals, with the paperwork attached
Day rates and duration discounts, included kilometres, condition at handover and return, and an agreement the customer signs.
What happens when the flight moves
The sequence end to end, because "flight tracking" describes a feature rather than a behaviour.
- 01
The booking is taken with a flight number
The number is normalised and validated as it is captured, whether it came from the booking form, a WhatsApp thread or a pasted email. A transfer without a flight number is just a timed job — everything below depends on this one field being present and correct, which is why it is checked at the door rather than discovered later.
- 02
A subscription opens as the date comes into range
Rather than polling, the system registers a watch on that flight number with the data provider. Subscriptions are free to hold and are closed again once the flight has been and gone, so you are never paying attention to a flight nobody is meeting.
- 03
The airline changes something
A new arrival time, a terminal change, a cancellation, a diversion. The provider posts the updated record, the shared cache is written, and every booking on that flight is now reading the new reality rather than the one that was true when the booking was taken.
- 04
The desk is told, once
If the change is real news rather than a four-minute drift, an alert goes out by email and push to the people routed to receive it. One alert, carrying the flight, the new time and the affected job — rather than a channel that cries wolf until somebody mutes it.
- 05
You re-plan, and everything downstream follows
Move the pickup, reassign the driver, or forward the job to a partner if your own car can no longer cover it. The customer is told from your own address rather than a vendor's, the driver's view updates, and if you bill for waiting time it is calculated from what actually happened rather than from the timetable.
Your brand, your domain
Your colours, your logo and your sending address, on a hostname you own. Customers never learn what software you run.
Booking page, panel & emails — 100% your brand, none of ours
The parts either side of the flight
Flight tracking is the piece that is specific to airport work, but it is not the piece you spend most of your day in. A transfer desk lives in quoting, confirming and invoicing, and airport work puts particular pressure on all three.
Quoting, because an airport transfer is usually priced long before it runs. Fixed prices for named routes are the natural fit — the run from the terminal to the city centre is the same journey every time and should not be re-measured and re-derived on every enquiry. Pricing zones cover the surrounding towns, distance and hourly rates by vehicle class cover everything else, and a quote holds its price for a defined window rather than drifting between the moment the customer looked and the moment they booked.
Confirming, because the price a customer was shown has to be the price the system honours. Every booking is recomputed on the server against the stored quote before it is accepted, so a figure posted by a browser can never become a promise. If the numbers disagree, the job waits for a human instead of being silently rejected or silently accepted.
Invoicing, because airport work is where the account customers are. Hotels, corporate travel bookers and tour operators want a monthly invoice addressed to a company rather than a card link per ride, with consecutive numbering that stands up to an audit and VAT shown properly. That is ordinary accounting rather than anything clever, and it is also the part that most often turns out to be the reason an operator changes system.
How a booking moves
Arrive, get priced, get a driver, get confirmed, get paid — the same path whichever channel it came from.
Create your organization, set your rate card, connect your domain and drop in your logo and colour.
Point your website at RideDesk, plug in the API, forward marketplace jobs, or add them by hand.
Approve, assign a driver or partner, send the pay link, and let the automations handle the rest.
Questions that separate airport-capable systems
Ask these in the demo, in this order. They are chosen because a product that merely ticks "flight tracking" struggles with all of them.
Ask to see a diverted flight, not a delayed one
Delays are the easy case — the time changes and everything else holds. A diversion changes the airport, which changes the route, the price and possibly whether you can cover the job at all. Ask what the system shows and what it does next. Most will show you a delay and move on.
Ask where the flight data comes from and how it refreshes
You want a named provider, not "our flight partner", and you want to know whether updates are pushed or polled. Then ask what happens when the data allowance runs out mid-month, because that answer tells you whether tracking is a feature or a cost they are quietly managing.
Ask how an early arrival is handled
Everybody builds for late. Early is where you lose the passenger, because they are through the terminal with their bags before anyone has been told the flight moved. If the system only alerts on positive delay, it covers half the problem.
Ask what the driver sees, and when
Time a new driver from "hired" to "looking at their first job". If the answer involves an app store, a password reset and a support ticket, multiply it by your annual driver turnover and decide whether you want to keep paying that.
Ask how waiting time is charged
A free waiting period followed by a rate is the standard, but the question is what it is measured from. Waiting time computed from the scheduled landing rather than the actual one is a bill your customer will dispute, and they will be right.
Ask what a moved flight does to the price
A three-hour delay can push a job into a night band or out of an early-booking discount. Ask whether the system re-derives the price, leaves it alone, or quietly does one of those without telling you. Any of the three can be the right answer; not knowing which is not.
Ask about the return leg
Outbound to the airport and inbound from it are one customer relationship and two completely different jobs — one is a departure time you control, the other is an arrival you do not. Check that a return is modelled as a real second journey rather than a note on the first.
Ask who the invoice can be addressed to
If the only billable party is the passenger, hotel and corporate work will be manual forever. Ask to see a booking for one person invoiced to a different company, and a marketplace job that generates no customer emails at all because the marketplace owns that relationship.
What comes with it
The capabilities that turn a booking list into a business you can run from one screen.
Built-in CRM
Every booker becomes a customer record — history, documents, billing details, lifetime value.
Two-way inbox & WhatsApp
Reply to customers by email or WhatsApp from inside each booking. No separate app.
Live flight status
Airport pickups track the flight automatically — delays surface before the driver leaves.
Bookable by AI agents
A per-tenant MCP endpoint lets AI assistants get a quote and book — priced by your rules, never theirs.
Quote-to-booking analytics
See what visitors entered, which class they picked, and where they dropped off the funnel.
Automations & reminders
Confirmations, driver reminders, payment chasers and a morning digest — on autopilot.
What flight tracking does not do
It does not stop the flight being late. It stops you finding out from the passenger. The alert lands with your desk rather than automatically with your customer, and that is on purpose — whether a delayed passenger should be messaged, and what you say to them, is an operational decision with a commercial edge to it, not something a webhook should be making on your behalf. Meet-and-greet, name boards and waiting-time bands work the same way: they are priced from your own add-on catalogue rather than being fixed behaviour, because no two transfer desks charge for them alike.
Frequently asked questions
What is airport taxi dispatch software?
It is dispatch software built around the fact that the pickup time on an airport job is derived from a flight rather than fixed. On top of the usual work — taking the booking, pricing it, assigning a driver, telling the customer, taking payment and invoicing — it tracks the flight the job depends on and tells your desk when that flight moves. Products built for street hailing can technically store an airport booking; they simply have nothing to say when the arrival time changes.
Which flight data source does RideDesk use?
AeroDataBox. It is named here rather than described vaguely because you should be asking every vendor the same question — a provider you cannot name is a provider whose coverage and refresh behaviour you cannot check. Live status is stored with its own quality marker, so a timetable-only flight is visibly different from one with a live feed behind it.
Does the system move the pickup time automatically when a flight is delayed?
No, and this is a deliberate choice rather than a gap. A three-hour delay might mean shifting the pickup, or reassigning the driver, or handing the job to a partner because your car is committed elsewhere by then — those are different decisions with different costs, and the right one depends on the rest of your day. The system's job is to put the change in front of the person who can decide, immediately and without them having to go looking. It does not guess.
Does the passenger get told about the delay automatically?
Not automatically. The disruption alert goes to your desk. Messaging the passenger is then one action, from your own address with your own branding, and you control the wording — which matters, because "we have seen your flight is delayed and your driver will be there" is a very different message from an automated one that arrives while they are still in the air and can only worry them.
What happens when a flight is cancelled or diverted?
It raises the same disruption alert as a delay, with the new status attached. What follows is yours to decide, because a diversion is genuinely ambiguous — a landing at a different airport may be a job you can still cover at a different price, a job to forward to a partner near that airport, or a cancellation under your own policy. All three paths exist in the system; which one applies is a judgement about your fleet that afternoon.
Can I charge for waiting time and meet-and-greet?
Yes, as priced items in your own add-on catalogue, resolved on the server so the amount always comes from that catalogue and never from whatever a browser submitted. They are catalogue entries rather than dedicated features on purpose: operators charge for airport waiting in genuinely different ways — a free period then a per-fifteen-minutes rate, a flat terminal fee, nothing at all for corporate accounts — and a fixed implementation would be wrong for most of them.
Do drivers need an app to see the flight?
No. Each driver gets a private link that opens their own jobs on any phone, with no password, no install and nothing to move when they change handset — a new driver is working in the time it takes to send them a message. Their view carries the flight number, the passenger and the pickup details. The live flight status and the disruption alerts sit with the dispatcher rather than the driver, because the dispatcher is the one who can actually re-plan.
Can it price a fixed rate for a named airport route?
Yes. Named routes carry a fixed price that overrides the calculated one, which is the right model for airport work because the run from the terminal to the city centre is the same journey every time and should not be re-derived on every enquiry. Pricing zones cover the surrounding area, and distance and hourly rates by vehicle class cover everything outside both. Night surcharges and early-booking discounts apply on top.
Does it handle hotels, tour operators and corporate accounts?
Yes — the passenger and the paying party are separate things in the data model. A booking can be for one person and invoiced to a company, on a monthly invoice with consecutive numbering and VAT handled properly. Marketplace jobs are treated differently again: the marketplace owns the passenger, so those rides are dispatched and tracked without generating customer emails, payment demands or invoices against somebody who is not your customer.
How many flights can I track?
Flight data is metered, so it is worth understanding rather than glossing over. Two things keep the ceiling high in practice: status is cached against the flight number and date and shared platform-wide, so many bookings on one inbound cost a single lookup, and changes are pushed by webhook instead of polled, so watching a flight closely does not cost more than watching it loosely. Subscriptions are also closed once a flight is finished, so nothing keeps consuming your allowance after the job is done.
How is this different from ordinary taxi dispatch software?
The core is the same system — bookings, drivers, pricing, payment, invoicing. Airport work adds the flight layer on top and changes the emphasis of everything underneath it: quotes that hold a price for weeks rather than minutes, named-route pricing rather than a meter, account billing rather than card-in-the-car, and a driver who has to be somewhere at a time that is still moving. The general guide on taxi dispatch software linked below covers the shared foundation.
Is it suitable if airport work is only part of what I do?
That is the normal case, and none of this is a separate product. Flight tracking activates on the bookings that carry a flight number and stays out of the way on the ones that do not, so a fleet doing school runs, corporate hires and airport transfers runs all three on the same board without the airport machinery cluttering the rest.
Related guides
See it with your own rides
Set up an account, load a handful of real bookings and see how they move through dispatch. No card needed to look around.