A guest issue response playbook for small teams
You do not need a 24/7 desk to handle guest issues well. You need a predictable loop that every team member follows, so a guest who reports a problem at 7 PM gets the same experience as one who reports it at 10 AM. This is the loop we see work for teams of two to twenty people.
Acknowledge in minutes, fix within a window
Guests tolerate problems. They do not tolerate silence. Separate the two commitments: acknowledge every report quickly — even ‘We’ve seen this and someone is on it’ — and then give an honest window for the fix.
A guest who knows the technician comes at 9 AM sleeps better than one who was promised ‘as soon as possible’ and heard nothing more. Set a team target for acknowledgement during service hours (fifteen minutes is realistic for most teams) and a clear message for what happens overnight.
Triage by impact, not by order of arrival
Not every report is equal, and treating them equally means urgent ones wait behind cosmetic ones. Define three tiers once and let the team apply them without discussion.
- Urgent: no water, no access, a safety concern, no heating in winter. Interrupts whatever is happening.
- High: no air conditioning in summer, no hot water, broken Wi-Fi for a working guest. Handled today.
- Normal: a cosmetic defect, a missing item, a question. Handled on the next round.
Keep the guest in the loop without a conversation
Status updates beat chat. Each change of state — received, looking into it, in progress, resolved — should be visible to the guest without them asking. Add a one-line human note when the status changes: ‘Technician booked for 9 AM’, ‘Part ordered, arrives tomorrow’.
This replaces the ten messages a WhatsApp thread would generate, and it means any colleague can pick the issue up at shift change and see exactly where it stands.
Give every issue one owner
Issues that belong to everyone belong to no one. Assign each report to a named person the moment it is acknowledged — the on-duty colleague, the technician, the housekeeping lead — and make reassignment explicit at shift change rather than assumed.
An owner is not necessarily the person who does the work; it is the person who makes sure the guest hears back. On small teams that is often the same person, which is fine. What matters is that when a guest asks ‘who is handling this?’, the answer is a name and not a shrug.
Resolved means the guest says so
The most common failure in issue handling is this: the team marks the issue done and the guest disagrees. Close the loop by asking the guest to confirm. If they reopen it, it goes back to the top of the list.
That is mildly annoying for the team and far better than a review that reads ‘they said it was fixed and it wasn’t’. Over time, the reopen rate becomes one of your most honest quality metrics.
Decide the recovery in advance
For High and Urgent issues, decide now what you offer: a late checkout, a bottle of wine, a partial refund above a certain duration. Decisions made calmly in advance are fairer to guests, cheaper for you and easier for staff to apply without escalating.
Write them down where the team can see them. A recovery gesture offered within the hour is remembered; the same gesture offered after a complaint is merely expected.
Review the pattern every week
Spend fifteen minutes each week looking at issues by category and by unit. Three Wi-Fi reports in building B is a router, not three difficult guests. Two hot-water complaints in the same apartment is a boiler.
Recurring problems are where your maintenance budget should go first. They are also the cheapest reviews you will ever prevent.