This article does not repeat the hotel's overall organizational method, covered in our guide to better organizing guest transfers. It focuses on one specific moment: the conversation with the customer, before the request goes to the transport company. This is where most misunderstandings happen.
Why ask the questions beforehand, not on the day
Missing information doesn't disappear: it shifts to the driver, on the curb, in front of a tired customer. A vehicle that is too small, a flight entered incorrectly or an unreachable number are hard to fix at that point.
The transport company can only respond to what you send it. If your request is vague, its answer will be too, and it is the hotel that bears the consequences with the customer.
The questions to ask, in order
This order follows the logic of a conversation. First you frame the service, then the journey, then the people, then how to meet up.
- **Which service?** A one-way trip, a round trip, or a vehicle kept for a period of time? If the customer mentions a full day, review the difference between transfer, vehicle hire and excursion before ordering.
- **Which journey, which day?** Date, direction of travel, pickup location and arrival location. For a place other than the hotel, ask for the full address.
- **Which flight, or what departure time?** On arrival: flight number, airline, airport and scheduled arrival time. On departure: flight time, or the time the customer needs to be on site.
- **How many travelers?** Adults and children. For children, ask whether a suitable seat is needed. Also ask whether anyone needs help getting in or out of the vehicle.
- **What luggage?** Number of suitcases, carry-on bags, and any bulky item: stroller, sports equipment, musical instrument.
- **Who to contact, and how?** Name of the lead traveler, a number reachable on the day of the transfer, and the language in which they prefer to be contacted.
- **Which booking?** The name under which the stay is booked and the reference, to link the transfer to the right file.
What each answer changes, and what to do if the customer doesn't know
| Information | Why it matters | If the customer doesn't know |
|---|---|---|
| Flight number | It lets the transport company place the arrival and prepare the welcome. | Ask for the airline and the time shown on the booking. Note that the flight remains to be confirmed and set a follow-up date. |
| Number of travelers | It determines the capacity needed. | Ask for the makeup of the group rather than an approximate total. If doubt remains, flag it to the transport company. |
| Luggage | It determines the volume needed, often more than the seats. | Ask for the number of suitcases per person. An honest order of magnitude is better than "a few". |
| Contact on the day | It avoids a pointless wait if the customer can't be found. | Ask for a second means of contact, or a contact on site. Agree the procedure to follow with the transport company. |
| Customer's language | It guides the confirmation message and the welcome. | Offer the languages you know you can handle and note the answer. |
| Booking reference | It avoids duplicates and mix-ups between two similar customers. | Find it in your own file, without asking for it a second time. |
To choose the vehicle category from these answers, rely on the sedan, van and minibus vocabulary. For the request itself, structured entry lets you bring together flight, time, travelers, luggage and meeting point in one place.
What not to ask the customer
- **The meeting point.** It is up to the hotel to define it with the transport company, then announce it to the customer.
- **The drop-off location for a riad.** Don't infer it from the type of vehicle or the location. Only the riad confirms where drop-off is possible. The approach is detailed in the article on drop-off with the riad (link below).
- **Unnecessary data.** Collect only what is useful for the transfer. If a point seems sensitive to you, check your own internal policy before asking for it.
To frame the drop-off location, read how to agree the drop-off point with the riad.
When to verify, and what
Information collected once can change. Plan two checkpoints, and don't leave them to chance.
- **When taking the request:** read back aloud to the customer what you have noted. Flight entry errors are caught at this stage.
- **Before the day:** on a date you set with the transport company, reconfirm the time, the number of travelers and the contact. The exact lead time depends on your agreement with them.
- **At every change:** go back over the whole file, not just the modified line. A change of time can lead to a change of vehicle.
Template message to send to the customer
This message fits in a few lines. Adapt it to your tone and to the customer's language.
Once the assignment is made, the customer expects only one thing: to know where and with whom they will meet. A link shared by WhatsApp or by email can carry this information, in the customer's language.
Common mistakes
- Accepting "there will be four or five of us" without asking about the makeup of the group.
- Noting the arrival time without the flight number.
- Forgetting to ask about luggage when the vehicle is chosen based on the number of seats.
- Collecting only one phone number, that of a person traveling separately.
- Promising a meeting point before the transport company has confirmed.
- Not linking the transfer to the booking, which complicates the handling of any complaint.
If the customer is absent at the meeting point despite everything, the protocol is prepared in advance: see the waiting protocol between hotel and transport company.
Checklist before sending the request to the transport company
- Service named: transfer, round trip or vehicle hire.
- Date, direction, pickup location and arrival location filled in.
- Flight number, airline and time noted, or departure time confirmed.
- Group makeup and special needs noted.
- Luggage described, bulky items flagged.
- Contact reachable on the day, plus a second one if possible.
- Customer's language noted.
- Booking reference attached to the request.
- Meeting point defined by the hotel, never by the customer.
- Read-back done with the customer, reconfirmation date set.
Want to understand how this information flows between the hotel, the transport company and the traveler? See the how-it-works page.
With WAYLISS
- The property enters a structured request: flight, time, travelers, luggage and meeting point.
- The link shows the meeting point, then the driver’s first name, the vehicle and its plate once assigned.
- The property shares the link with the traveler by WhatsApp or email.
- Each ride keeps a viewable history: request, assignment and steps.
Learn more: Guest transfer management for hotels, riads and concierge services
Frequently asked questions
What should I do if the customer doesn't have their flight number yet?
Note the approximate date and time, flag it to the transport company as provisional and set a follow-up date with the customer. Don't block the request, but don't present it as final.
Should I ask for the children's ages?
Ask if a suitable seat may be needed. State in your request what the customer needs, and let the transport company confirm what it can provide.
Can the customer choose their own meeting point?
No. The hotel defines it with the transport company, then announces it to the customer. For a riad, only the riad confirms the drop-off location.
What should I do when the customer changes the time after confirmation?
Go back over the whole file: time, vehicle, contact, meeting point. Then pass the change on to the transport company and wait for its confirmation before reassuring the customer.
Where should the collected information be kept?
In a single file that your team consults. Avoid scattered notes across messaging apps, notebooks and spreadsheets, which produce contradictory versions.
