Start with responsibilities
List who answers new enquiries, who resolves booking changes and who handles questions for today’s departures. Build queues around these responsibilities. Too many labels can slow a small team down; too few can hide urgent requests among general questions.
Make ownership visible
Agree when a conversation is assigned and what completion means. A drafted answer is not a sent reply. A message passed to another team is not necessarily resolved. Have one owner remain accountable until the next person accepts a handoff.
Write internal notes for the next person
Capture the guest’s purpose, the relevant booking and what has been agreed. Avoid long transcripts where a short summary will do. Keep internal comments separate from guest-facing messages and verify what a guide, reservations agent and supervisor can each access.
Review the queue, not just response speed
Look at unanswered messages, conversations waiting on another team and issues that reopen. Fast first replies can conceal slow resolution. Use a short daily review for departure-sensitive work and a weekly review for repeated questions that better website content could prevent.
A concrete example
A guest asks for a pickup change. Reservations passes it to operations, but nobody accepts it. A queue rule that keeps ownership until handover is accepted makes the unfinished work visible.
Put it to work this week
Review five reopened conversations and identify whether the delay came from missing information, unclear ownership or an unavailable action.