The Guest Decides: When to Offer a Person

A guest should not have to earn the right to speak to a person. If they already asked for someone at the hotel, the offer is late. AI takes the repetitive work and, when the case stops being that, says so early and passes it on. Speaking to someone is not a prize. It is part of the service.

A lot of hotels hide the person behind a menu. Options first, then “otherwise, ask for reception.” Someone in a hurry, or already annoyed, reads that as a wall. Someone who only wanted the breakfast hour does not need anyone. A fixed button cannot guess that difference. You offer it when you hear it, and you offer it before the guest has to fight for it.

When you do offer

There are moments when offering a person is hospitality, not giving up. When the guest asks. When the question is no longer a fact: it is an exception, a complaint, something that changes with the day. When the AI does not have the answer and would be inventing certainty. In those cases the line is short: if you want, I’ll pass you to someone at the hotel.

Offering is not forcing. Some people would rather finish on their own. Pushing the handoff wastes their time. The offer is said once, clearly, and a no is respected. If they say yes, there are no more filter questions. They already decided.

When you do not offer

You do not offer a person for the hour, the directions, a simple availability check, or confirming a fact you already have. Sending that to the desk hands the team back the repetitive work. The human touch is not answering what can be said well without taking anyone’s time.

You also do not offer it as an exit at the first stumble. “I didn’t catch that, do you want to speak to someone?” on the first miss is quitting. Try the simple question first. If it is still unclear the second time, then offer. Looping again and again so you do not bother the team does the opposite: it bothers the guest.

How it is said

The line is not “I can’t help you.” It is “someone here should look at this.” The first sounds like a system limit. The second sounds like a hotel. You do not need to apologize for passing it on. You need to say what happens next: someone at the hotel takes the case with what was already said.

If nobody is there at that moment, do not promise they will answer now. Say the truth: nobody is at the desk right now, and this is written down for when they come in. Inventing that a person is free when they are not breaks more trust than a short wait. The offer has to be real.

What the person receives

When the guest chose to talk, the person does not start from zero. They get what was asked, what was already answered, and why it was passed. If the guest has to repeat that they already asked for someone, the hotel threw the decision away. Choosing a person, and having that person not know they were chosen, is worse than never offering.

The person does not justify the handoff either. They do not ask why the system did not close it. They ask what is needed now. The guest already did their part. The team does theirs by taking the case.

The offer is not an endless menu

A long path with “speak to reception” at the end trains the guest to skip everything, or to give up first. The offer works when it shows up in the moment, not as a hidden last option. If almost everyone ends up asking for a person, either the agent is jamming the simple stuff, or it is hiding the human part. Look at both. Do not cover them with more options.

There is no need for a speech about artificial intelligence. The guest does not care what the tool is called. They care whether the simple thing gets done without a line, and whether, when they want someone, someone shows up. Explaining the system in the middle of the call is another filter.

This week, check when a person is offered

Sit with whoever answered yesterday. Ask for three real conversations: one that should have stayed with the AI, one that should have gone to a person, and one where the guest asked for someone and it took too long. Do not look for a percentage. Look for the sentence that was said.

1. The one that should have stayed: was a person offered for no reason?
2. The one that should have moved: did it keep trying to close itself?
3. The one where the guest asked: were there more questions after “I want to speak to someone”?

Fix only the third. From tomorrow, when the guest asks for a person, the next line is the handoff, not another filter. The guest decides. The hotel does not make them repeat the decision.

If you see the team cannot take that handoff because they are buried in simple questions, that is another week: what should not be reaching the desk. This week the change is one. Whoever asks for someone at the hotel gets them without an exam.

Do not measure whether they spoke to people more or less. Measure whether, when they asked, they did not have to fight for it. The repetitive work stays where it can be handled without taking the team. What the guest chose to put in someone’s hands arrives in those hands.

If you cannot listen to three conversations, one is enough. The one where the guest said they wanted a person. Note how many loops came after. Do not publish that number or turn it into a target. It shows whether the decision was respected. If it took more than one loop, the menu is still in charge, not the guest.