A driver waits 40 minutes at the arrivals hall, the passenger never shows up and doesn't answer the phone, and when they finally call two hours later they ask not to be charged because "the flight was delayed and nobody told me." Without a no-show policy that's written down and accepted before the booking, that argument has no winner: it's the driver's word against the passenger's, and the business loses money and time either way it goes.
A cancellation and a no-show are not the same thing
A cancellation is a decision the passenger communicates before the ride, whether inside or outside whatever window you've set. A no-show is the passenger's absence at the pickup point, with no prior notice, once the driver is already there and has waited the agreed time. Treating the two the same, for example charging the same amount for both, is the first mistake, because the cost each one generates is different: a cancellation with 24 hours' notice lets you reassign the vehicle to another job; a no-show at the pickup point doesn't.
Why the distinction matters for pricing
If your policy charges the same for a cancellation made a week out as for a no-show at the airport, you're subsidizing the second with the margin from the first. The policy needs to reflect that the real cost of a no-show is nearly the full cost of the ride: vehicle, driver and deadhead miles already spent.
How long to wait, and why that number isn't arbitrary
A reasonable wait time depends on the type of pickup point:
- Airports: 45 to 60 minutes from the confirmed landing time, not the scheduled time, to cover customs, baggage and the walk to the meeting point.
- Train stations: 15 to 20 minutes from arrival time, since disembarking is far faster.
- Private or business addresses: 10 to 15 minutes from the agreed time, with a mandatory attempt to reach the passenger by phone before counting it as a no-show.
Once that time has passed, and only after trying to reach the passenger through at least two channels (a call and a message), the ride gets logged as a no-show and billed according to the policy.
How to document it so it isn't one person's word against the other's
- The driver's arrival time at the pickup point, with geolocation if the system supports it.
- Contact attempts: time of the call, time of the message, and whether there was a response.
- The time the no-show is declared, always after the agreed wait time has elapsed.
- A record of the prior agreement where the passenger accepted the policy: the confirmation email or booking screen itself.
Without these four pieces, every complaint turns into a case-by-case negotiation, and case-by-case negotiations are exactly what erodes margin and the morale of whoever handles customer service.
Why it has to be written and accepted before booking, not after
A no-show policy that only exists in the operations team's head protects nobody, not the business and not the passenger: by the time the conflict happens, it's too late to set the rules. The policy needs to show up at the moment of booking, with an explicit checkbox or confirmation, for two practical reasons:
- It cuts down the volume of disputes, because the passenger already knew the terms when they booked.
- It gives you a defensible position in a card chargeback, because you can show the customer accepted the policy before the charge, not after the dispute started.
Summary table: which policy applies to which case
| Situation | Wait time | Charge |
|---|---|---|
| Cancellation more than 24h out | Not applicable | No charge, or a token fee depending on the rate |
| Cancellation between 24h and 2h out | Not applicable | 50% of the fare |
| Cancellation less than 2h out | Not applicable | 100% of the fare |
| No-show at airport or station | 45-60 min / 15-20 min | 100% of the fare |
| No-show at a private address | 10-15 min | 100% of the fare |
These percentages are a reasonable starting point, not a fixed rule: adjust them to your operation's real margin (see the full per-ride cost breakdown in how to price an airport transfer without losing money), and publish them with the same clarity across every booking channel.
Training drivers to follow the policy consistently
A written policy only works if every driver applies it the same way. Without a shared standard, one driver waits the full 60 minutes and calls twice, while another leaves after 20 minutes with a single unanswered text, and the passenger's experience of "the policy" ends up depending on who happened to be driving that day. Two things fix this: a single source of truth the driver checks before declaring a no-show (not their own judgment on the spot), and a required log entry at the moment it happens, not reconstructed from memory at the end of the shift. Consistency is what makes the policy defensible later; an inconsistently applied rule is barely better than no rule at all.
What to do next
Check whether your no-show policy exists anywhere today that a passenger actually sees and accepts before paying. If it only lives in the head of whoever dispatches rides, write it down this week with these four elements (wait time by pickup type, mandatory contact attempts, the moment a no-show gets declared, and the resulting charge), and put it in front of the passenger at the booking confirmation step. TransfersManager includes this acceptance as part of the booking flow and keeps the timestamped record of attempts you'd need if a dispute comes up.
