Hospitality

Describing a meeting point your guest will actually find: the method for hotels

A well-described meeting point fits in one sentence a guest can follow alone. Here is the formula, the landmarks to choose, the test to run before sending and reusable messages.

4x4 crossing a ford in a green Atlas valley

Many transfers get off to a bad start for a simple reason: the guest and the driver are both "at the meeting point", but not in the same spot. The text entered by the hotel was too short, too internal or ambiguous. This article focuses on a single task: writing the description. For the rest of the organization, see the pillar page

For the general framework of the organization, read How it works. Here, we only deal with writing the meeting point.

Why "Arrivals hall" is not enough

A general place name designates an area, not a spot. Within that area, several drivers are waiting, several exits exist, and the guest doesn't know where to look. The problem arises everywhere: airport, train station, port, hotel car park, square in front of a riad.

Three mistakes come up again and again in practice:

  • Internal vocabulary: "we meet at the shuttle", "in front of the staff entrance". The guest doesn't know these terms.
  • A place without a landmark: the text names a location but indicates nothing visible once on site.
  • Different text depending on who reads it: the guest reads one version, the driver another, and nobody notices before the day itself.

The four-element formula

A good description answers four questions, in this order. Each element fits in one short sentence.

  1. The precise place: the exact name as it is written on site (terminal, exit, side of the station, car park name, street name).
  2. The visible landmark: what the guest sees on arrival. A sign, a counter, a numbered pillar, a shop, a door. Choose a fixed landmark, not something that moves.
  3. The action instruction: what the guest does next. Stay put, wait for the driver with a sign, head toward a landmark.
  4. The backup contact: who the guest calls or writes to if they can't find the spot, and who, on the driver's side, tries to reach them.

Before / after: rewriting a vague description

The examples below are writing templates. Replace the items in square brackets with what you have checked yourself on site.

Vague descriptions and usable descriptions
Vague descriptionProblemUsable description
Arrivals hallArea too wide, no landmarkAt exit [exit name], near [fixed landmark]. Stay at this spot: the driver will join you there with a sign bearing your name.
In front of the hotelSeveral sides possible, several entrancesIn front of the main entrance of [hotel name], on the [street or square] side, under the [description] sign.
At the car parkSeveral car parks or levelsCar park [exact name], level [as indicated on site], near [landmark]. The driver is waiting for you there.
Near the stationThe station has several access pointsExit [name or side of the station], in front of [landmark]. The driver is standing next to their vehicle.
Contact the driverThe guest doesn't know who or howIf you have any difficulty, write to [property contact]. The driver, [first name], will also contact you.

How to write it, step by step

  1. Go to the spot, or ask someone who knows the place and has been there recently. A description written from memory goes out of date quickly.
  2. Note the exact name of the place as it is displayed, not as you call it.
  3. Choose a single visible, stable landmark. Two competing landmarks create doubt.
  4. Write the action instruction in the imperative, in short sentences.
  5. Add the backup contact, on the property's side and on the driver's side.
  6. Have a colleague who doesn't know the place read it. If they hesitate, rewrite.
  7. Enter the same description in the request, so that the guest and the driver read the same text.

The property's structured request brings together the flight, the time, the travelers, the luggage and the meeting point. The traveler then receives the meeting point, followed by the driver's first name, the vehicle and its plate once the assignment is made. What you write in the meeting point field is therefore what the guest will read: take care over it.

The reader test

Give the text to someone who doesn't know the place. Ask them a single question: "Where will you stand, and what do you see around you?" If they hesitate, name a different spot or ask "but where exactly is it?", the description isn't ready.

This test takes little time and saves a phone call, a wait and a worried guest. Do it especially for points you rarely use or have just changed.

The message to send to the guest

A template to adapt. Keep it short: the guest often reads it on a phone, after a journey.

Depending on the property's organization, this message can be shared with the traveler by WhatsApp or by email. Specify this in your internal procedure, so that reception knows which channel to use and the guest receives a single reference message.

The instruction to the driver

The driver must read the same description as the guest, not a summarized version. Add only what relates to their job: where they stand, how they make themselves recognizable, and who they notify if they can't see the guest.

To see what the driver does at each step of a ride, read a driver's day, step by step.

When the meeting point changes

A closure, roadworks, a different terminal: the point sometimes changes on the same day. In that case, don't just correct it verbally.

  • Rewrite the complete description, with all four elements, not just the word that changes.
  • Send it to the guest and to the transport company at the same time.
  • Ask the driver for written confirmation.
  • Keep a record of who changed what, and when.

The tracking method is detailed in keeping track of a ride's changes. Each ride also keeps a viewable history: request, assignment and steps.

Checklist before sending

  • The name of the place is the one displayed on site.
  • A visible, stable landmark is given.
  • The action instruction is clear: stay, wait, head toward.
  • The backup contact is written down, on the property's side and on the driver's side.
  • The last stretch (riad, medina, narrow street) has been confirmed by the property concerned.
  • An outside reader understood where to stand.
  • The guest and the driver received the same text.
  • The language of the message matches the guest's language.

For the organization side at the property, see the page on guest transfer management for hotels, riads and concierge services. On the ground side, the drivers page presents their point of view.

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: How WAYLISS works

Frequently asked questions

Should I include a photo of the meeting point?

A photo can help if it is recent and legible, but it doesn't replace the text. It goes out of date quickly if the place changes. If you attach one, check that it matches the landmark described.

How many landmarks should I give?

A single, well-chosen one is better than several. Two landmarks can point to two different places in the guest's eyes. Add a second landmark only if it removes a real doubt, and test it with a reader.

The guest speaks another language: what should I do?

Write the description in the guest's language, in short sentences, and keep place names as they are displayed on site. Have a colleague who speaks that language read it if you have any doubt.

Who confirms the drop-off spot in front of a riad?

The riad itself. Never deduce the drop-off spot from the type of vehicle or the reputation of the neighborhood. Ask the property for confirmation and copy it into the description as is.

How often should usual meeting points be reviewed?

Agree on a rhythm with your team and your transport companies, and always review after field feedback reporting a difficulty. A frequently used point deserves a regular check.