Guest Messaging
Key takeaways
- Classify messages by situation so an emergency never waits behind a booking question.
- Staff arrival and departure peaks, including the person who can approve a move.
- Send a first reply that confirms ownership and names the next update.
- Review misses weekly and fix one cause at a time.
Operating data
Playbook
Define the target by message type
A single response target for every guest message hides the difference between a question and an emergency. A booking inquiry can wait for a considered answer, while a message about a gas smell or a locked door needs a reply within minutes. Write two or three message classes, then attach a target to each class. The class should describe the situation rather than the guest's tone, so the team applies the same rule every time. A clear class also tells a new coordinator which messages to open first when the inbox is full.
Most portfolios need a first-response target for active stays, a longer target for pre-booking questions, and an immediate path for safety reports. Record the target in the property playbook and in the channel settings so it appears where the work happens. A target that lives only in a training slide will not survive a busy Saturday. Review the classes when a new channel or a new property type joins the portfolio, because an old target may no longer fit the volume. The goal is a rule the team can explain in one sentence and a guest can feel in the reply.
Staff the weekend, not only the weekday
Response targets fail when the schedule assumes a Monday-to-Friday office. Guests travel on weekends, and a check-in problem at eight on Sunday evening needs the same attention as a Tuesday morning. Build coverage around arrival and departure peaks rather than around a standard work week. Name who answers, who backs them up, and when the handoff happens. Holiday weekends deserve their own line because the volume and the staffing rarely match a normal week.
A small team can cover a weekend with a shared rotation and a written escalation list. The rotation should include the person who can approve a relocation or a maintenance call, not only the person who reads messages. If the approver is asleep, the target is a wish. Test the rotation once a quarter with a practice message that requires a real decision. Record how long the test took, who answered first, and which step caused the delay.
Write the first reply before the full answer
A fast first reply does not need to solve the problem. It needs to confirm that a person has the message, restate the issue in one line, and give a time for the next update. That structure keeps the guest from sending the same question through three channels. It also gives the coordinator room to check the reservation before promising a fix. The guest learns that someone is working, even when the answer is not ready.
Use plain language and avoid a template that sounds like a case number. A guest who is locked out wants to know when someone will arrive, not which department owns the ticket. Include a direct number when the situation is urgent, and say what the guest should do while waiting. A short, specific reply reduces the number of follow-up messages. It also creates a record that the next shift can read without guessing what was promised.
Hand off without resetting the clock
When a message moves from one shift to another, the response clock should not start over. Pass the original timestamp, the guest's last message, and the next promised update in the handoff note. The receiving person should reply from the same thread rather than opening a new one. A guest who has to repeat the story has been failed twice. Close the handoff note with the name of the person who now owns the reply.
Name one owner for each active conversation even when several people contribute. The owner confirms that the issue is closed and that the guest has the final answer. If the owner goes off shift, the handoff note names the replacement before the shift ends. Shared ownership without a named owner is how a thread goes quiet for a day. A short ownership line is enough to prevent that silence.
Review misses without blaming the shift
Review response times weekly and separate the process miss from the individual mistake. A late reply caused by a broken notification is a different problem from a late reply caused by an unstaffed hour. Record the cause beside the timestamp so the pattern is visible across properties. The review should produce one change, not a general reminder to try harder. A single fix, such as a weekend alert, is easier to verify next week.
Share the result with the people who answer the messages, because they see the failure before the report does. Ask which messages arrive with too little information and which ones need a decision the shift cannot make. Those answers often improve the target more than a new tool. Keep the review short enough to repeat every week and specific enough to change one behavior. The team should leave with a next step, not a score.
Keep the target honest as the portfolio grows
A response target that worked for three units may fail at thirty. The volume grows faster than the number of people who can answer, and the first sign is usually a weekend thread that nobody owns. Review the target against the actual arrival calendar each season. If the team cannot meet the target with the current coverage, change the target or change the coverage rather than pretending.
Write the target in a place the guest can see, such as the listing or the arrival message. A guest who knows a reply usually arrives within an hour will wait instead of sending a second message through another channel. The published target should match the one the team is measured against. A public promise that the operation cannot keep is worse than no promise at all.
## Related services - Guest communication - Reservation coordination - Owner reporting
## Sources - SBA guidance on managing a business
FAQ
When should a leader delegate this workflow?
Delegate it when repeated coordination, routing, or follow-up is taking time away from decisions that only the leader can make.
What should the assistant own first?
Start with intake rules, status visibility, and escalation timing so the assistant can act consistently before the workflow expands.
