WayCab PlusWayCab Plus ENES Request Demo
Editorial illustration: Shuttle and Transfer Software for Tour Operators

Shuttle and Transfer Software for Tour Operators

How tour and transfer operators can take hotel, airport and excursion bookings under their own brand, and what to ask before choosing software.

· 6 min read

Tour and transfer work looks like taxi work from the outside, but it behaves completely differently. Almost nothing is booked for right now: the trip was sold last Tuesday for Saturday at five in the morning, by a hotel concierge or an agency, for four passengers with six suitcases. This guide is for the operator who owns the vans, not for the traveler. It covers what the software has to capture at booking time, how a transfer day is actually dispatched, how the two pricing models behave in a seasonal business, and what to ask a vendor before you commit.

What does a transfer operator need from booking software?

Three things, in this order: capture the reservation completely, show the whole day on one screen, and leave a record you can show a hotel or an agency afterwards. A transfer that was taken down incompletely is worse than one that was never sold, because the customer is already counting on it. Everything else is secondary to those three.

The pieces themselves are the same ones any passenger operation uses: a booking channel with your name on it, a dispatch panel for the office and an app for the driver. What is specific to transfers is how far ahead the booking happens and how many people touch it before the vehicle moves.

How far ahead are transfer bookings made, and why does that matter?

Most transfers are sold days or weeks before the trip, which changes the main risk of the business. An on-demand ride fails loudly and immediately; a reservation fails silently and you find out when the customer calls from the lobby. That is why the part of the software that handles scheduled trips, reminders and tomorrow's list matters more here than assignment speed.

  • A list of tomorrow's trips that the office can read before closing today
  • Scheduled and recurring trips, for hotels that send the same pickup every week
  • The return leg captured in the same reservation, because it is the easiest extra sale to lose
  • Passenger and luggage counts, so dispatch assigns a vehicle that actually fits
  • A booking confirmation the customer and the seller both receive

Who sells your transfers, and what each channel needs

Usually three channels, with different needs. Treating them as one is how operators end up with a day that cannot be dispatched.

  • Hotels and concierges: book on behalf of someone else, need speed and a confirmation they can hand over
  • Agencies and tour operators: send volume on their own terms and expect a monthly record of what was served
  • The traveler directly: finds you online, and this is the channel where your own brand actually earns the customer
  • Your own repeat clients: residents, corporate visits, recurring airport runs with addresses already on file

The direct channel is the one worth building, because it is the only one where the customer remembers your company rather than the intermediary that sold the trip. That is also the channel a branded booking app is for.

What has to be captured at booking time?

If any of these is missing, somebody in the office will spend the morning on the phone rebuilding it. Capture them when the booking is created, not the night before the trip.

  • Date, time and direction of travel, including whether it is a pickup or a drop-off
  • Flight number and arrival or departure time as the customer gave it to you
  • Exact pickup point: hotel, address, terminal or meeting point agreed with the customer
  • Number of passengers, plus luggage, child seats, wheelchairs or anything that changes the vehicle
  • Who sold the trip, so you can report back to that channel
  • Who to call if nobody appears at the meeting point

Pickup arrangements inside an airport are set by the airport itself and they change. Confirm the current rules with the airport and put the resulting instruction into the confirmation your customer receives, rather than assuming any platform knows it.

How should dispatch handle a transfer day?

A transfer day is planned the evening before and defended in the morning. The office assigns vehicles and drivers to tomorrow's reservations, checks the vehicle sizes against the passenger counts, and leaves one unit uncommitted for the thing that will go wrong. During the day, dispatch is mostly reassignment: a delayed arrival, a group that grew, a driver stuck in traffic.

The practical requirement is that the reassignment happens in the system and reaches the driver app, not through a chain of phone calls. When changes travel by voice, nobody can reconstruct the day afterwards, and reconstructing the day is exactly what the hotel will ask you to do when a guest complains.

Monthly fee or commission in a seasonal business?

Be honest about the trade-off. A percentage per trip costs you nothing in a dead month and takes a cut of every trip in high season, which is when you make the year. A fixed monthly fee is a cost you pay in the low season too, but it leaves the peak intact and makes your numbers predictable. For most seasonal operators the question is what happens over twelve months, not what happens in February.

WayCab Plus works on a monthly fee with no percentage per ride and unlimited drivers, with technical support included 24/7. Setup and any custom development are quoted separately, and the amount depends on configuration and volume, so it comes out of a conversation. If your business has a strong season, bring your real monthly trip counts to that conversation.

Where WayCab Plus fits

WayCab Plus develops, configures and maintains the rider app, the driver app and the dispatch panel that a transportation company runs under its own brand, which is what lets a transfer operator sell directly instead of only through intermediaries. For the airport side of the same problem, read Taxi Booking Software for Airport Shuttle Services.

Frequently asked questions

Is transfer software different from taxi dispatch software?

The pieces are the same, but the weight shifts. A taxi operation lives or dies on how fast a trip gets assigned; a transfer operation lives on whether a reservation taken eleven days ago is complete, assigned and remembered. When you evaluate a platform for transfers, test the scheduled-trip screens hardest and the live map second.

Can I keep selling through hotels and agencies and still have my own app?

Yes, and most operators run both for a long time. The agencies bring volume you did not have to find; your own branded channel brings customers who come back and whose history stays with you. The important part is that both end up in the same system, so your day can actually be dispatched from one screen.

Does the software track flights automatically?

Do not assume it does. Ask the vendor directly whether flight data is something configured, something developed, or something your office enters by hand, and get the answer in writing before you build your operation around it. What is standard in any serious platform is capturing the flight number and time the customer gave you, and showing it to the driver.

What should I bring to a demo?

Bring one real peak day: every reservation, with passenger counts, luggage, meeting points and the channel that sold each one. Ask the vendor to load that day and show you the dispatch screen at six in the morning. Twenty minutes of your own worst day tells you more than any feature list.