A failed transfer is rarely about the vehicle. It comes down to missing information: an outdated flight number, a vague meeting point, a driver the front desk can't identify. So compare the methods on this point: where is the right version of the information, and who can read it?
What each method does well, and where it breaks down
| Criterion | Spreadsheet | Dedicated platform | |
|---|---|---|---|
| Getting started | Immediate, everyone knows the tool | Quick, you define the columns yourself | Requires onboarding and the agreement of your transport companies |
| Overview of the day | Weak: you have to scroll back through conversations | Good if the file is up to date | To check: all requests must be visible at once |
| Last-minute change | Fast, but buried in the thread | Depends on who opens the file and when | Depends on how the change is passed on to everyone |
| Teamwork (front desk, concierge) | Fragile: the history belongs to one phone | Risk of competing versions | To check: rights, sharing, roles |
| Record in case of dispute | Screenshots, often incomplete | No reliable history without discipline | To check: request, assignment and steps are kept |
| Guest data confidentiality | Numbers and names in groups with changing members | File copied, sent, sometimes forgotten on a computer | To check: who sees what depending on their role |
Real situations in the trade where the method fails
- The transport company's WhatsApp group includes a former driver. He can still read guests' names and times.
- A guest changes flights the day before. The morning front desk updates the spreadsheet, while the evening one has already confirmed the old time by message.
- A driver writes "I'm outside." The front desk doesn't know which guest he means, because the original request is three days up in the conversation.
- A guest complains about a wait. Nobody can find the exact time of the request or who assigned the vehicle.
How to decide: the five-step method
- List your most recent problematic transfers and note the cause: missing information, time error, unidentified driver, double entry.
- Count who handles transfers in a typical week: front desk, concierge, management, night duty.
- Count your transport companies. Each additional contact multiplies the conversation threads.
- Test the handover: ask a colleague who was absent the day before to find tomorrow's transfer on their own. If they can't do it within a few minutes, your method depends on one person.
- Choose the simplest method that passes this test, and set a date to reassess it.
For a broader framework on organization at the property level, also read How a hotel can better organize its guests' transfers.
If you stay on WhatsApp or a spreadsheet: the minimum rules
Many hotels work this way and manage fine, provided they set rules.
- One group per transport company, with a member list reviewed regularly.
- A request message always built the same way (template below).
- A spreadsheet with a single reference version, with a "last modified" column and the author's name.
- One person responsible for the previous-day check, replaceable by another.
- No copy of the file sent by personal e-mail.
Request message template to reuse
For a riad, ask the riad to confirm the drop-off location and copy it into the request exactly as given.
When a platform becomes relevant
It is justified when the problem is no longer the messaging tool, but the fragmentation of the file. If your lost time comes from re-entering data, competing versions and follow-ups to identify the driver, look for a solution where the request, the assignment and the history stay in a single file. The traveler should also be able to receive the information without installing yet another tool.
Ask any provider about the protection of guest data and about the rights of each party. Our page Safety, privacy and trust details this approach. For the hotel context, see guest transfer management for hotels, riads and concierge services.
Tool selection checklist
- Does a request contain flight, time, travelers, luggage and meeting point?
- Can your whole team follow the same request?
- Do you always know which driver and which vehicle are assigned?
- Is access limited according to each person's role?
- Can you retrieve the history of a trip afterwards?
- Do your transport companies agree to work this way?
- Is the pricing model clearly written before you commit?
Common mistakes when changing methods
- Switching everything at once, in the middle of high season. Test on a few transfers first.
- Keeping two systems in parallel with no rule: nobody knows which one is authoritative.
- Forgetting to tell transport companies and drivers what changes for them.
- Not appointing an internal contact person for the team's questions.
- Choosing based on the demo rather than on your own problem cases.
To understand how a transfer journey works in general, see the How it works page.
With WAYLISS
- The property enters a structured request: flight, time, travelers, luggage and meeting point.
- The transport company assigns the driver and vehicle; the property sees the driver’s first name, the vehicle and the plate.
- Each ride keeps a viewable history: request, assignment and steps.
- Several team members (front desk, concierge) can follow the same requests.
Learn more: Safety, privacy and trust
Frequently asked questions
Is WhatsApp enough for a small hotel?
Often yes, if one or two people handle the transfers and messages follow a fixed template. The risk appears when the team grows or when the lead person is absent.
Does a shared spreadsheet solve the version problem?
It reduces it, but it doesn't notify anyone of a change. You need a review discipline and someone responsible for the previous-day check.
What should I ask a transport company before changing methods?
Ask how they receive requests, who assigns the driver and vehicle, and how they pass that information on to you. Agree together on what changes for their teams.
How do I protect guest data whatever the tool?
Limit access to the people who need it, remove former members from groups and avoid file copies. Check your data protection obligations with your legal adviser or the competent authority.
When should we reassess our method?
After each significant incident and at the end of each season. Repeat the handover test with a colleague who was absent the day before.
