A guest message needs an owner, not just an answer

First decide whether the message needs an action#

“Where is the spare blanket?” and “Can we check out later?” can arrive in the same inbox. They should not follow the same process. The first may have a factual answer in the property guide. The second asks you to change the stay and may affect the next arrival or the cleaning schedule.

Before writing templates or introducing automation, sort the recurring questions by what must happen behind the reply. The useful distinction is whether you are sharing checked information, verifying something that may have changed, or asking a person to make a decision.

Leave a handover that the next person can use#

A reply saying “we will check” is a promise to do more work. Record who will check, what they are checking and when the guest should hear back. Choose a response time your team can meet; do not turn a convenient template into a commitment nobody owns.

• The guest’s request, in plain language.
• The relevant property and stay reference in your authorised workspace.
• What has already been checked or promised.
• The next action and the person responsible.
• When the guest should receive an update, even if the decision is still pending.

Keep this record inside the tools your team uses for the stay. When discussing an example outside that workspace, remove guest names, contact details, access information and booking references.

Make a pending reply useful#

This tells the guest why the answer is pending, avoids an accidental approval and sets a specific next step. If you cannot give a reliable update time, say how you will follow up instead of inventing one.

Use a troubleshooting template only where the instructions are appropriate for that appliance and situation. A message that needs a person to attend the property is not complete just because you sent a guide link.

Choose an automation boundary you can explain#

If you use an AI assistant, start with a narrow review: which answers depend only on checked property information, and which depend on permission, current availability or an unresolved problem? Write down the boundary before relying on the assistant.

• Try routine questions and compare the answers with your current guide.
• Try a request that should need approval, then inspect the actual behaviour. Do not assume an assistant has a particular escalation or approval feature.
• Check that guests can still find your human contact route.
• Review unanswered and repeated questions to identify missing information.

Close the loop with the guest#

When the check is complete, give the decision and the practical next step. If a late checkout is agreed, state the time and any applicable conditions clearly. If it cannot be offered, say that plainly and confirm the original checkout arrangement.

Only mark the work complete when the promised action has happened or the responsible person has accepted it. A handover that stops at “message sent” can leave a guest waiting while everyone thinks someone else is handling it.