A review reply isn't read only by its author. It's read by dozens of future guests who are deciding, right now, whether to book with you or not. So a reply to a review isn't a conversation with one person — it's a public performance in front of everyone who's still on the fence. Almost everything else follows from that: tone, structure, speed, and what should never make it into the reply.
Three principles everything else follows from
- You're writing for the reader, not the author. The author of a negative review may never come back to you. But the reader on the fence will draw a conclusion either way: "they know how to admit mistakes and fix them" — or "they argue with guests here." The second conclusion costs more than any single review.
- Calm is a strategy. The core of handling a complaint is: listen, acknowledge, apologize, resolve, follow up. A public reply is the same chain, just written and in full view of everyone. Irritation shows up in text instantly, and it always loses.
- Specifics beat politeness. "Thank you for your feedback, we're so sorry" is an empty formula. "You're right, the AC on the fourth floor was noisy — we replaced two units last week" is a reply that sells the hotel better than any ad.
Structure of a reply to a negative review
A five-step working framework:
- Thank them and use their name. No sarcasm, no corporate-speak: "Maria, thank you for sharing your experience."
- Name the problem in your own words. Not "we apologize for any inconvenience caused," but something specific: "A forty-minute wait to check in really is too long." Restating the problem shows the review was actually read, not processed by template.
- Apologize once, and mean it. One honest apology works; three ritual ones read as a brush-off.
- Say what you did or will do. The most important part for the future reader: "We reviewed the situation with the front-desk team and changed our process for peak check-in hours." If the investigation is still ongoing, say so — that's fine.
- Invite them to continue in a private channel — for details, compensation, and anything not meant for the public: "Please write to us at … — we'd like to sort out the details and make it right."
Step five matters for another reason too: negotiating compensation in a public thread sets a precedent of "write a bad review, get a bonus." Compensation stays in the private channel only.
Template framework: cleanliness complaint
Hello {name}! Thank you for telling us — what you described about the cleaning doesn't meet our standard, and we're sorry it happened. We reviewed this with our housekeeping team: {what changed — inspection of this area added to the checklist / a conversation held with the staff member}. We'd appreciate it if you could write to us at {contact} — we'd like to apologize personally and make sure everything is as it should be on your next visit.
Template framework: noise complaint
{Name}, hello, and thank you for the honest review. We agree: getting a good night's sleep is the basic reason people go to a hotel, and the noise {source, if named} got in the way of that. What we did: {specifics — spoke with neighboring rooms on the floor / changed the schedule for overnight work / now offer rooms further from the elevator at booking}. If you're planning to stay with us again, write to me directly at {contact} — I'll personally find you a quiet room.
Notice that both frameworks require you to fill in specifics. A template you could send without reading the review is exactly the kind of brush-off that wasn't worth sitting down at the keyboard for.
Replying to positive reviews
Glowing reviews deserve a reply too — a short, human one. Three rules:
- Keep it short. Two or three sentences. A long reply to praise reads as self-promotion.
- Latch onto a detail. A guest praised breakfast — pass the compliment along to the chef by name; they mentioned the view from the room — share in the moment. A detail turns a formality into a dialogue.
- Don't turn it into an ad. "By the way, we also have a spa and airport transfer!" tacked onto a thank-you reads like trying to sell something to someone who already bought everything.
{Name}, thank you for the kind words! We passed your compliment along to {detail — the breakfast team / the floor attendant}. We'd love to have you back.
Speed and who owns it
- Respond to negative reviews fast — ideally within a day: a fresh reply is seen both by the author and by everyone reading the "hot" page. But not instantly, on emotion: if a review stings, draft it right away, then send it after rereading with a clear head.
- One voice. One or two people who own the brand's tone reply — not "whoever's free." Inconsistent styles are noticeable from the outside.
- A review becomes a work ticket, not just a reply. Every complaint is a request for a fix: a leaking faucet mentioned in a review needs to reach maintenance's task list, not just get a nice reply. It helps to keep a review log organized by topic: when reviews from different channels land in one place — in Cenaly they flow into a shared feed together with tasks — recurring themes become visible a month before they turn into "reputation."
What to never do
- Argue or catch them out. Even if the guest is factually wrong, a public argument is lost before it starts. At most, calmly offer your own account: "Our records show … — but we're sorry the impression stuck, and here's what we're offering."
- Disclose guest data. Room number, stay dates, payment details, the circumstances of a conflict — nothing personal belongs in a public reply, even in your own defense.
- Blame staff. "That attendant no longer works here" reads to the reader not as a solution but as an employer throwing its own people under the bus. The hotel answers — not names.
- Copy-paste the same text across every review. Identical replies are obvious at a glance and cancel out the value of each one.
- Explain yourself with a list of excuses. "We were fully booked, had a new employee, had a system outage" — the reader doesn't care why; they care what you're doing about it.
Key takeaways
- A review reply is a public performance for future guests, not a conversation with the author.
- Framework for negative reviews: name → problem in your own words → one honest apology → what you fixed → a private channel for details.
- Specifics ("replaced the AC units") persuade the reader far more than any polite formula.
- For praise: keep it short, reference a detail from the review, skip the ad.
- Never: arguing, guest data, blaming staff, copy-pasting, negotiating compensation in public.