Hotel operations

Parking, airports and the last mile: the questions asked from a taxi

Getting to the hotel and parking at it generate more pre-arrival messages than anything except check-in times, and they are asked at the worst moment - from a taxi, from a station, with luggage and no local language. The answers are fixed, specific and mostly already known to the night porter: whether parking exists, what it costs, whether it can be reserved, which exit of the station to use. Publishing them precisely is the cheapest guest-experience improvement a hotel can make.

Parking has four facts and most hotels publish one

Whether there is parking at all, how many spaces, the price per night, whether it can be reserved in advance or is first-come, the height restriction, and what the nearest paid alternative is when it is full. "Parking available" answers none of that, and a guest who arrives to a full garage at midnight with a car they cannot leave anywhere writes the review that costs more than the space did.

Never promise a space the hotel cannot hold

If parking cannot be reserved, saying "there should be space" is an invention that will be discovered at midnight. The honest answer names the constraint - how many spaces for how many rooms, and what the guest should do if it is full - which lets them decide to book the public garage instead. A guest who parked elsewhere on honest advice is not unhappy; one who was reassured is.

Directions are specific or they are useless

"Ten minutes from the station" helps nobody with a suitcase. Which exit, which side of the road, whether there are stairs, which bus number and where it stops, what the taxi fare should be roughly, and what the hotel is next to that a driver will recognise. The last detail matters more than the rest: an address a local driver does not know is the commonest arrival failure, and the hotel knows what to say instead.

Answer in the language the question arrived in

Arrival logistics are precisely where a guest is least able to work in a second language - under time pressure, with luggage, possibly lost. This is the traffic where multilingual answering pays most, and where a mistranslated street name does real harm. Keep place names and station exits in the local script alongside the translation, so the guest can show a phone screen to a driver.

Frequently asked questions

What should a hotel publish about parking?
Whether it exists, how many spaces, price per night, whether it can be reserved or is first-come, the height restriction, and the nearest paid alternative when full. "Parking available" answers none of those.
Can an assistant say a space will be free?
Only if parking can actually be reserved. Otherwise name the constraint - how many spaces for how many rooms - and say what to do if it is full. A guest who parked elsewhere on honest advice is not unhappy; one who was reassured and found it full is.
What makes directions actually useful?
Specificity: which station exit, which side of the road, whether there are stairs, the bus number and its stop, the rough taxi fare, and what the hotel is next to that a driver will recognise. An address a local driver does not know is the commonest arrival failure.
Why does language matter more for this traffic?
Because arrival is when a guest is least able to work in a second language - time pressure, luggage, possibly lost. Keep place names and station exits in the local script beside the translation so the guest can show a screen to a driver.
Is this worth automating at all?
It is among the highest-volume pre-stay questions and the answers never change, which is the best possible case for it. The measure is whether arrival-time phone calls to reception fall, not how many messages were answered.

Get in touch

Leave your details and we will reply. You do not need a sales call to get an answer.