840
passengers
One manifest, in the format you actually receive
The manifest becomes the plan, and the plan watches the sky.
Upload the air manifest once. It becomes live Flight Tracking, an Airport check-off page, and, on Growth, a transfer plan that builds itself and re-plans when flights move.
840
passengers on one uploaded manifest
63
inbound flights watched by webhook
26
coach runs clustered from them
1
afternoon it all has to work
One manifest upload resolves the same afternoon three different ways.
The spreadsheet a client sends you is a list of people. What you need is a list of coaches. Everything between those two facts (parsing, matching, watching, clustering against your own vehicle capacities) is the module.
63
inbound flights
Parsed, matched and watched live by webhook
26
transfer runs
Clustered by airport, window, hotel and capacity
01Flight Tracking
Every arrival watched continuously, not refreshed by hand.
The manifest is parsed by AI into passengers and flights, then watched live: delays, gate changes, diversions and cancellations arrive by webhook push, with a polling fallback underneath.
- Manifest upload in the formats you actually receive
- Card and table views; passenger list download
- A realtime airport check-off page on a token link: search, tick, done
- Arrival progress feeds the home board and the Client Cockpit
Six minutes, no phone calls
One flight moves and the plan follows it.
This is the whole argument for one system instead of five. In a stack of separate tools every line beside this is a person remembering to do something on the worst morning of the program.
Arrival-to-Ground, in depth- 11:47QY 208 slips 40 minutesWebhook push, not a refresh
- 11:47Run B1 flagged for reviewNever silently reshuffled
- 11:52Pickup moves 12:10 → 12:50Approved by you
- 11:53Driver acknowledges on his linkNo app, no account
- 11:53Day sheet and cockpit followOne record, downstream
02Arrival-to-Ground
The single most stressful moment, orchestrated.
“The flight's late: who do I call?” becomes a flagged run with a proposed fix. Clustered runs, approved by you, dispatched to your own drivers, re-optimized when reality moves.
- Runs clustered by airport, window, hotel and vehicle capacity
- Suggest → approve → dispatch: you stay in control of every run
- Re-optimization proposes; VIP-flagged guests are never auto-moved
- Every change posts to program chat: the timeline is the record
26 coaches, one afternoon, one dispatch record.
Drivers are vendors in your own network, and each one gets their run on a link: passenger names, meet point, timing. Dispatched and acknowledged are states you can see, not calls you have to make.
Everything in flights & ground
Flight TrackingThe program's air manifest, watched live.Airport check-offA realtime arrivals page for the airport team: search, tick, done.Growth and upArrival-to-GroundThe flight manifest becomes clustered, approvable transfer runs that re-optimize when flights move.Growth and upDriver dispatchDispatched runs land on the driver's phone: names, meet point, timing.
Flights & ground questions
Where does the flight data come from?
A webhook-capable live flight data layer. FlightAware AeroAPI and AviationStack are both implemented behind one provider interface: with webhook push for status changes and a polling fallback so a missed webhook never means a missed delay.
How do transfers get planned from the manifest?
Arrivals are clustered into runs by airport, arrival window and destination hotel, within the vehicle capacities of your own vendor fleet. The clustering is explainable: you see why each guest is on each run, and you approve every run before anything is dispatched.
What happens when a flight is delayed?
The affected run is flagged, “A flight changed, review this transfer.”, and re-optimized: the pickup shifts, the run can split or merge, and the updated time is pushed to the driver, who acknowledges it. Nothing is silently reshuffled, and VIP-flagged guests are never auto-moved.
Do drivers need the app?
No. Drivers are vendors in your network and get each run on a magic link: passenger names, meet point, timing. Dispatched and acknowledged states are visible to the ops team, and updates reach the same link.
Bring a manifest to the demo.
We'll load it live: watch it become tracked flights, clustered runs and a driver dispatch, then move a flight and watch the plan follow.