Solutions

Operational problems that show up in a transfer business, what they cost, and how the platform answers each one.

When a flight is late, the whole schedule moves

A delayed arrival breaks every job behind it. What matters is whether the schedule adjusts on its own or a dispatcher rebuilds it by phone.

Fixed routes and agency rates should price themselves

A corridor with a known price should quote instantly, at the rate that partner agreed, without a callback from the office.

Hotels and agencies want one invoice, not forty

Partner business is billed per period, not per ride, and the paperwork should not be assembled by hand at month end.

Moving dispatch off WhatsApp and a spreadsheet

Group chats and a shared sheet work until two people are dispatching at once. After that, the gaps are what the passenger notices.

Two jobs, one car: how double-booking happens

Double-booking is not carelessness. It is what happens when availability is a question someone has to ask rather than something the system knows.

Your own booking portal against a marketplace listing

A marketplace brings volume you do not own. A branded portal brings customers who came back to you on purpose.

What a commission actually costs over a season

A percentage on every ride is a variable cost that grows with the business. A fixed platform fee does not.

When your dispatch software vendor stopped shipping

A system that has not changed in years is not stable — it is abandoned. What matters is whether a feature request becomes a feature, or just another support ticket nobody answers.

Scaling drivers and vehicles for peak season

Airport transfer operators can need three or four times their normal driver and vehicle capacity during holiday peaks, and a ski resort, a cruise port, or a summer schedule face the same seasonal demand. Finding, onboarding, and scheduling that much temporary driver capacity fast is a different problem from running a stable year-round roster.

Getting paid for waiting time and no-shows

A driver who waits past the free grace period, or shows up for a passenger who never comes, has done real work that a per-ride price does not cover. The software question is not how to get paid, but how a booking's waiting-time and no-show policy gets applied the same way every time, instead of depending on a dispatcher to notice and write it up by hand.

When the booking goes to someone else's driver

Passing an overflow booking to a subcontractor or partner fleet solves the capacity problem. It creates a tracking problem: who actually drove it, at what rate, and whether the payout ever got reconciled.

One invoice, split the way finance actually reads it

A corporate account does not pay per ride. It pays per period, and the invoice has to arrive already split by department or cost centre, or it sits on a desk until someone rebuilds it by hand.

Booking a vehicle that actually fits the group

A booking says four passengers and two suitcases. The vehicle that shows up seats four and has a trunk for two. On paper that's a match, until someone mentions the extra bag, the fifth passenger who joined last minute, or the wheelchair nobody flagged when the guest called it in.