The Question Was Answered. The Guest Was Not.
The call goes out from the desk to a suite: what time would the guest like housekeeping service. A routine call, made for the operation’s benefit. The guest thanks the caller, then explains she cannot give a time — her husband is on a business call and she does not know when it ends. She asks whether more luggage racks are available. The answer takes thirty seconds. The racks are already there, and the staff member walks her through where each one sits in the suite. By now the original question, the reason the call was placed, has gone unanswered. She stays on the line anyway. The whole exchange runs two and a half minutes, and almost none of it is about housekeeping.
Anyone who has worked a floor long enough knows this call. The guest is not confused about luggage racks. She is alone in a suite while someone else works, and a voice has just arrived on the line. The staff member who answers has two options. Close the request, as the operation asks. Or stay on the line, which the operation has no way to see and no way to count.
Another instance: upon departure, a guest asks the concierge what time the car is required. The concierge performs the usual — confirms the time, arranges the car, and closes the request. The transaction is faultless. The concierge does not ask whether the guest is heading straight to the airport or spending the afternoon in the city first, or whether a restaurant recommendation would change the shape of that afternoon. Not because the concierge is careless. Because the question was answered, and the operation considers an answered question complete.
Hotels have built their service systems around the stated request. The operation measures response time, resolution, and accuracy. A guest asks, the staff answers, the sequence closes. The protocol in the operation points to the question — not to the need underneath it.
The two are often the same. A guest who calls for a wake-up call wants a wake-up call. But often enough, they are not the same, and when they diverge, the operation has nothing. So whether anyone reads past the request depends entirely on the individual present in that moment — their attention, their workload, and their day. And anything that depends entirely on individual discretion is one of the first things to disappear when the floor gets busy.
Here is what makes this harder than it sounds. The read extends in both directions. The guest on the phone wanted the conversation to continue. The guest down the hall wants thirty seconds and nothing more. A property that responds to this by instructing staff to engage more warmly, ask more questions, and build more rapport is misreading the situation as badly as one that drills its staff on call-handling time.
What is required here is not more contact. It is knowing which guest is in front of you. This ability currently has no home in the operation or its structure. Nobody requests it at hiring, no standard describes it, and nothing carries it forward when the shift changes.
The industry has spent years on programs meant to make its properties warmer, more intuitive, more attuned. Some of it works. But it treats the read as a personality trait of individuals, then returns them to an operation that still measures only the closed request. The staff member who spends two and a half minutes on a thirty-second call has, by every number the property keeps, performed worse than the one who hung up. The operation will never know it got the better employee.
Walk into any property and listen to the requests coming in: what time, where is, can you send. Each one gets answered promptly and efficiently by staff who are good at their jobs. The question will be answered. Whether the guest was — nothing in the operation is built to notice.
The post The Question Was Answered. The Guest Was Not. appeared first on Hotel Speak.