Reducing No-Shows and Managing Dispatch for Transfer Companies
The vehicle already drove there. That single fact changes everything about how you handle this.
A tour no-show leaves an empty seat on a departure that was going anyway. A transfer no-show means you sent a vehicle and a driver across a city specifically for one passenger who is not there — and by the time you know, the money is already spent.
That makes the arithmetic worse than most operators realise, and it makes the fixes different. It also turns out that a large share of what gets recorded as a no-show is not one.
What a no-show actually costs
Operators think of a no-show as a lost fare. In vehicle time it is considerably more, and putting numbers on it changes how seriously the problem gets treated.
Take a job of forty minutes with the driver, plus thirty minutes repositioning to get there and back — seventy minutes of vehicle time. An eight-hour driving day holds about six of those.
Now a passenger does not appear and the driver waits forty-five minutes. That is thirty minutes of repositioning already spent plus the wait — seventy-five minutes of vehicle time gone for nothing, which is more than a whole completed job. Not a lost fare; a lost fare plus a job you could have run instead.
Scale that modestly — one per vehicle per week across a twenty-one-week season — and each vehicle loses roughly twenty-three jobs' worth of capacity. None of it appears in your accounts, because nothing was invoiced.
Most are meeting failures
Here is the part worth investigating before spending anything on prevention: a substantial share of transfer no-shows are two people in the same building unable to find each other.
The guest waited at the wrong exit. The driver was in the car park because vehicles cannot stop at the door. The guest saw no one, assumed the transfer had not come, and took a taxi. All of those get recorded identically to a passenger who simply never travelled — and all of them are your operational failure rather than the customer's.
They are also the ones that generate complaints and refund demands, because from the guest's side they did turn up and paid twice. Transfers have this worse than the tour equivalent: no group standing together to spot, no guide with a sign at a familiar square, and a guest who has usually just got off a plane.
The airport problem
Airport pickups concentrate every failure mode at once — an exhausted traveller, an unfamiliar building with several exits, no local phone credit, and a driver who may not be permitted to enter the arrivals hall.
- Say precisely where the driver stands, in the confirmation and again on the morning. "Arrivals" is not an instruction at an airport with four of them.
- Send a photograph of the meeting spot, taken from the direction the guest walks in from. This one change removes more airport failures than anything else on the list.
- Name the sign. If the driver holds a board, say what is written on it — your company name, or the guest's.
- Give a messaging-app contact, not just a phone number. A guest who has landed has wifi and no local credit, so a call from an unknown number goes unanswered while a message is read.
- Tell them what to do if they cannot see the driver — the one instruction that converts a lost guest into a two-minute phone call rather than a taxi and a complaint.
- Where vehicles cannot wait at the terminal, say so at booking. A guest expecting a driver at the door and finding a car park meeting point is an argument you scheduled in advance.
And the timing point that underlies all of it: work from the actual landing time rather than the booked one. Capturing the flight number at booking is what makes that possible, and it is the field most worth making mandatory — covered in the transfer software guide.
The waiting decision
Given what waiting costs, this deserves a policy rather than a judgement call made by whoever is standing there.
Set it in advance, publish it, and vary it by pickup type — a hotel lobby and an international arrivals hall do not warrant the same window. Measure airport waits from the landing time, or the policy punishes guests for a delay they did not cause.
What the driver does during that window matters more than its length:
- Contact immediately on arrival, not at the end of the wait. "I am here, at the blue pillar by exit 3" while the guest is still walking prevents the failure entirely.
- Escalate to the office rather than waiting silently. Somebody not in a vehicle can check the flight, call the hotel, or reach the booking agent.
- Record what happened before leaving — a photograph of the meeting point at the time is a complete answer to a later dispute.
- Give the driver authority to leave at the stated limit without ringing for permission, because the next job is already at risk.
Then decide what happens to the rest of the day. If a driver is now running late, somebody has to know before the next guest does.
Prepayment and reminders
The case for taking payment at booking is stronger for transfers than for anything else in travel, precisely because of the sunk cost. An unpaid transfer is a vehicle dispatched on trust.
It also removes a bad moment. A driver negotiating payment at the kerb with somebody who has just landed is a poor first impression, and it is where cash-handling disputes start.
On reminders, two, doing different jobs:
- The day before — confirming the booking exists, the pickup time and place, and asking the guest to tell you if their flight has changed. This is where cancellations surface while they are still cheap.
- On the day, close to pickup — the driver's name, vehicle, contact and exact meeting point. Short, and readable on a phone by somebody walking through a terminal.
Send them through a channel that works on a foreign handset. Email at six in the morning is not read; a message is. The guest communication guide covers the channel question in more depth.
Running a day that changes
Transfer days move. Flights slip, jobs cancel, somebody calls wanting a pickup in ninety minutes. The problem is rarely the change itself — it is people acting on different versions of the plan.
- One current version of the day, in one place, that everybody reads from. Not a morning message that has since been superseded three times.
- Name who reassigns. One person with authority to move work between vehicles, so two people do not solve the same problem differently.
- Push changes to drivers rather than expecting them to check. A driver mid-journey is not refreshing anything.
- Assigned is not accepted — especially with subcontracted drivers. A job sent and unacknowledged is not covered, and at 05:30 that distinction is expensive.
- Keep slack in the schedule. Vehicles booked back to back with no buffer turn one delay into four late pickups, which is how a single problem becomes a bad day.
That last point links back to the arithmetic above: slack looks like wasted capacity until the morning it absorbs a forty-five minute wait.
Measuring it properly
You cannot fix this on impressions, and the segmentation is what tells you where the problem actually is.
- Record a reason every time, chosen from a short list the driver can tap: could not find each other, flight changed, guest cancelled at the door, genuine absence. Six months of that data is worth more than any advice.
- By pickup type. Airport, hotel, private address, port. If one dominates, you have found a fixable instruction rather than a customer problem.
- By source. Bookings taken with no payment will show a markedly worse rate, which is the argument for prepayment made with your own numbers.
- By time of day. Very early pickups have their own pattern and their own fix.
Most operators who do this for a season find the same thing: the largest category is people who could not find the driver — solved by rewriting a paragraph and taking a photograph.
How Travelity helps
The parts of this that are software-shaped: taking payment at the time of booking through the booking widget or payment gateways, confirmations and reminders that send automatically against the booking rather than when somebody remembers, and a day view holding each job with the guest's details and contact number attached.
To be clear about what we are not: this is not real-time fleet dispatch with live vehicle tracking and automatic reassignment. If you are moving work between twenty vehicles during a shift, that is a dedicated category of software and you should buy it alongside.
Frequently asked questions
Why do transfer no-shows cost more than tour no-shows?
Because the cost is already spent. A tour no-show leaves an empty seat on a departure that was running anyway, while a transfer no-show means a vehicle and driver were sent specifically for that job. Counting the repositioning and a typical wait, a single no-show consumes more vehicle time than an entire completed job.
How long should a driver wait at an airport pickup?
Decide it in advance, publish it, and measure it from the actual landing time rather than the booked time. Airport arrivals need considerably longer than a hotel pickup because of immigration and baggage, and the driver should be calling and messaging throughout that window rather than waiting silently.
How can transfer companies reduce airport pickup failures?
Tell the guest exactly where the driver stands, with a photograph of the spot, and give them a way to message that works on a foreign phone with no local credit. Most airport no-shows are two people in the same building unable to find each other, which is a communication problem rather than a customer failing to appear.
Should transfer companies take payment in advance?
Wherever possible, and more insistently than a tour operator would. Your cost is incurred before you know whether the passenger will appear, so an unpaid booking is a vehicle dispatched on trust. Prepayment also removes the awkward roadside conversation about money that damages an otherwise good first impression of a destination.
How do you manage a transfer schedule that changes during the day?
Decide in advance who has authority to reassign work, keep one place where the current state of the day lives, and make sure drivers get changes pushed to them rather than having to check. The failure is not that days change — it is that different people end up acting on different versions of the plan.
Bottom line
Price the problem properly first: one no-show with a forty-five minute wait costs more vehicle time than a completed job, and a weekly occurrence takes around twenty-three jobs a season out of every vehicle.
Then treat it as a meeting problem rather than a customer problem. A photograph of the pickup spot, a messaging contact that works on a foreign phone, a driver who makes contact on arrival rather than at the end of the wait, and payment taken at booking will remove most of it — and recording a reason each time will tell you which of those to do first.
Related guides
See Travelity in action. Book a Personalized Demo.
30 minutes that can completely change the way you run your travel business. See how Travelity can help you work smarter, sell more, and operate with less stress.