A family at arrivals and no car
The outbound trip went perfectly. The car arrived on time, the family got to the airport, and the office booked the return for two weeks later. The return flight was written as 'Tuesday evening, from Tenerife' because the customer did not have the flight number to hand.
Two weeks later, the family land on Wednesday morning because the airline changed the flight, and they told the airline but not the taxi firm. Or the office entered the return for the wrong month. Or the return was put in the diary but not in the dispatch system. Whichever it is, a tired family with a lot of luggage is standing at arrivals ringing the office.
Why returns are the weak point
The outbound journey is fresh and confirmed. The return is weeks away, often uncertain, and nobody looks at it again until the day.
| What goes wrong | Why |
|---|---|
| Wrong date or month | Return date given verbally and misheard or mistyped |
| Flight changed | Airline moved it, customer did not tell you |
| Flight number missing | Customer did not have it when booking |
| Return not in dispatch | Written in a diary or notes field, not entered as a job |
| Different terminal or airport | Return flight lands somewhere different from where they left |
| Contact number wrong | Mobile given for the outbound driver, not working abroad |
None of these are hard to catch. They are simply not checked, because the office is busy with today's work.
The cost of a missed return
A missed return is one of the worst experiences you can give a customer. They are tired, often with children, and a long way from home. It is also costly: the replacement car usually has to be found at short notice, and the customer is unlikely to book with you again or recommend you.
Returns are often paid in advance with the outbound trip, so a missed return can also mean a refund. And the customer who booked a return with you was loyal enough to trust you with both legs, which makes losing them hurt more.
Tracking the return from the day it is booked
What we build treats the return leg as its own job that needs confirming, not an afterthought on the outbound booking.
- At booking, every return is created as a separate job in your dispatch system, linked to the outbound, never only as a note.
- If the return flight number is known, it is checked against the airline schedule for that date and airport. If not, the booking is marked as needing a flight number.
- Customers without a flight number get a friendly text or email asking for it once they have their details, with a simple link to add it.
- A few days before the return, the customer is asked to confirm the date, flight and pickup point, with an easy way to tell you about changes.
- On the day, the flight is followed through a flight data service and the pickup time moved when the landing time changes, using your own rules for time after landing.
- Any return that is unconfirmed, has no flight number or has a flight that no longer exists goes on a list for the office to chase, with enough time to reach the customer.
This works alongside flight tracking for all airport pickups, if you have that, so returns follow the same rules as every other arrival.
What changes for the office
The office stops relying on memory. A short list each day shows the returns that need a call, with the customer's details and what is missing, while there is still time to fix it.
Customers get a message from you while they are away, which reassures them the car will be there. Changed flights are picked up days in advance rather than at arrivals.
Returns become one of the most reliable parts of your airport work, and a reason for customers to book both legs with you next time.
Does this happen to your firm?
- Return flights are booked without a flight number.
- Returns are written in a diary or notes field.
- Customers change flights and do not tell you.
- Nobody checks returns until the day.
- You have had a family stranded at arrivals.