How to Respond to Negative Reviews: Templates and Guide

Write for the guest deciding whether to book

When you respond to negative reviews, write for the next guest, not to win an argument. Acknowledging disappointment does not mean accepting every allegation.

Choose according to the evidence. Adapt these short public replies only when the facts support them:

• Confirmed failure: “We are sorry about [problem]. We fell short by [verified failure].”
• Disputed fact: “We are sorry about the difficulty with [problem]. We can confirm [verified fact], although that does not explain the whole experience.”
• Mixed feedback: “We are glad you enjoyed [positive aspect]. We are sorry that [problem] affected your stay.”

If the evidence is incomplete, do not pick whichever version sounds best. Decide what is established and what remains unclear.

Illustrative example: less defence, more clarity

A guest could not get inside. In this example, messages confirm an incorrect code and subsequent help from reception.

Defensive reply: “You got inside eventually. That rating is unfair.”

Useful reply: “We are sorry about the difficulty on arrival. We sent you an incorrect code, and reception then helped you get inside.”

The reply acknowledges the failure without inventing a permanent fix to the access system.

Tip: Investigate thoroughly in private; keep the public reply brief.

Aim for a calm, specific, credible response. A better rating or another booking is not something your reply can guarantee.

Check the facts before drafting

Separate the guest’s account from what you can establish before replying. Focus your initial check on the central complaint rather than reconstructing the entire stay. You need to know what you can state and what remains uncertain.

1. Check the complaint in four steps

First, save the review text, channel and date detected in a private record with restricted access.

1. Separate individual claims. In the illustrative example “Nobody replied and I could not get in,” there are two issues: answering the message and accessing the property. Evidence about one does not settle the other.
2. Check relevant records. Review messages, arrival instructions and records for the service in question. Look for evidence that challenges your first impression, without collecting unnecessary personal information.
3. Confirm with the responsible staff member. Ask the receptionist on duty or housekeeping lead what happened and what supports their account. A recollection is not the same as a documented record.
4. Classify the evidence. Mark each claim as confirmed, contradicted by evidence or insufficient information. Assign someone to check the draft against those findings.

2. Decide whether to reply or escalate

Does the evidence support the sentence you want to publish? If not, remove it or acknowledge the uncertainty. Missing records do not prove that the guest is lying.

For an active safety concern, prioritize safety: consult the property’s current emergency procedure and guidance from the relevant alcaldía, the local mayor’s office, to identify local authorities and contact channels.

Check the platform’s current official help centre for response windows and reporting rules. A low score or disagreement alone does not establish that a review qualifies for removal.

Tip: A sent message does not prove that the guest read it or gained access. Reply to the verified fact, not the conclusion you would prefer.

Build a short reply around verified facts

A credible reply separates confirmed facts, planned work and what remains unknown. Your investigation may be detailed; your public response does not need to be. Include only what helps the next guest understand the concern and how you are handling it.

1. Build the reply in parts

1. Acknowledge the specific concern. Name the cleaning, access or noise issue. Recognizing a disappointing experience does not mean accepting every allegation in the review.
2. Own the verified failure or clarify one point. If you confirmed a mistake, acknowledge it without excuses. If a clarification is necessary, stay within the supporting evidence. Do not turn operational records into a public defence.
3. Describe the remedy’s actual status. A completed correction requires a checked result. Assigned work is still pending. An investigation does not yet establish what happened or prove that the issue is resolved.
4. Offer a private channel only when it helps. Explain its purpose, such as reviewing an arrival difficulty that remains unclear. Do not request personal details publicly or add “contact us” out of habit.

Tip: Check the status before choosing the verb. “We corrected,” “we plan to” and “we are reviewing” make different claims.

Short notes to adapt

Fill the placeholders with supported information and choose the version that matches the actual status. Mention an ongoing review only if it has started.

Verified correction:

We are sorry about the failure in [service area]. We confirmed that [verified failure]. We have now [completed correction] and checked [specific result].

Agreed action, not yet completed:

We are sorry that [confirmed problem] affected your stay. We plan to [specific next step] to address this issue.

Facts not yet established:

We are sorry your experience with [reported concern] was disappointing. We are reviewing [specific point] to understand what happened.

If you cannot establish the facts or offer a useful next step, end after acknowledging the concern. Do not fill the gap with promises.

Thank the guest when it feels appropriate, not because every reply needs the same opening. Skip an invitation to return if it distracts from an unresolved failure or sounds automatic.

Prepublication checklist

• Every factual claim has support, and you accept only verified responsibility.
• Completed corrections, planned actions and investigations are clearly distinguished.
• Internal identifiers, staff notes and personal, travel or payment details are excluded.
• You removed sarcasm, accusations, staff blame and promises you cannot guarantee.
• The language sounds natural, and a future guest can understand what matters.
• Any private channel offered has a specific purpose.
• The responsible person checked the wording and obtained any necessary approval before publication through an authorized channel.

Fair criticism: own the failure without excuses

When you confirm a cleaning failure, take responsibility for the service you delivered, rather than explaining away the mistake. A specific apology is more useful than an account of a difficult shift. Keep the investigation details within your team.

Illustrative example: a missed cleaning check

This scenario is fictional. A guest in unit 402 writes: “We found hair in the bathroom and dust on the table. We expected a clean apartment when we arrived.”

During the internal review, the housekeeping lead confirms that the final check was missed. For this first version, assume that the apartment was also cleaned again and a subsequent inspection confirmed the result. The unit number and staff-specific findings stay out of the public reply.

An unhelpful draft: “Our cleaner was very busy, and other guests rarely complain. You should have told us sooner.”

This blames the team and challenges the guest. A lack of complaints from other guests does not invalidate a confirmed failure. You do not need to defend your entire operation to acknowledge a specific problem.

A better public reply:

“We’re sorry the apartment was not clean when you arrived. We should have prepared it properly for your stay. It has since been cleaned again, and we checked the result.”

Each sentence has a job:

1. “We’re sorry the apartment was not clean when you arrived” acknowledges the specific experience without questioning the complaint.
2. “We should have prepared it properly for your stay” accepts responsibility without singling out an employee.
3. “It has since been cleaned again, and we checked the result” reports a verified correction rather than promising perfection.

Template: cleaning completed and checked

Use this version only when you can support both the corrective work and its verification. Replace the placeholders with specific facts.

We’re sorry you found [confirmed problem] when you arrived. We did not prepare the apartment as we should have. We have completed [specific corrective cleaning] and verified [confirmed result].

Template: correction pending, support confirmed

In this illustrative variation, the guest is still staying with you and the team has confirmed that another clean can be arranged through the reservation’s private messaging channel. Offer this option only if it is actually available.

We’re sorry you found [confirmed problem]. The apartment did not meet the cleaning standard it should have. We can arrange [confirmed cleaning service] with you through [private reservation channel].

Tip: Acknowledge the failure without excuses and offer only a solution you can deliver. Do not promise that it can never happen again.

If compensation may be appropriate, discuss it through a suitable private channel, separately from any conversation about the rating. Never make support conditional on deleting, improving or changing the review. Service recovery is not a purchase of a favourable opinion.

Disputed claims: clarify without accusing

Correct the fact you can establish, not the motive you assign to the guest. Clarification is not accusation. You can acknowledge a difficult arrival without agreeing that nobody replied.

Illustrative example: “Nobody answered when we arrived”

A guest writes: “We messaged on arrival and nobody answered. We were left without help.” The night receptionist finds a reply in the booking channel. That confirms a message was sent. It does not establish that the guest read it, understood the instructions or got inside.

Decide whether mentioning the reply helps. If it clarifies an important factual point, state only that narrow fact. Do not use it to dismiss the guest’s lack of assistance:

“We are sorry you had difficulty on arrival. We found a reply to your message in the booking channel, but that does not confirm you received the help you needed.”

If mentioning the message would only sound defensive, use an acknowledgment-only reply:

“We are sorry you had difficulty getting help during your arrival.”

You can add an invitation to continue privately if someone is responsible for handling that channel. Avoid “That is false; you should have checked your messages.” Do not publish screenshots or access instructions.

Private follow-up template

This template is for private messaging only. Its investigation questions do not belong in a public review response. Adapt it only if you verified that a reply was sent:

Subject: Communication during your arrival

Hello [name],
We found a reply in [booking channel] and would like to understand what happened next. Were you able to see the message? Did the instructions help you get inside, or did you need further assistance?
Please reply through [approved private channel]. You do not need to send passwords or personal documents.
[Responsible person or team]

Public example: an amenity the listing did not offer

In this fictional variation, the review says the listing promised a pool. You retained the listing version associated with the booking and verified that it did not offer one. The current listing alone is not enough to establish what was advertised when the guest booked.

With that evidence, the public reply could be:

“We understand your disappointment about the absence of a pool. The listing associated with your booking did not include a pool among the amenities offered.”

Do not add that the guest failed to read. Clarify the advertised amenity, not their intentions.

If the arrival communication evidence is inconclusive, use a different version:

“We are sorry you had difficulty on arrival. The available information does not allow us to confirm how communication was handled.”

Mention an ongoing investigation only if one exists.

Tip: A sent message is not the same as help received. Missing records do not prove that a guest is dishonest either.

1. Decide whether to report the review

1. Check the platform’s current policies and official help centre. Can you identify a specific possible violation? Disagreement or a low score alone does not establish eligibility for removal.
2. Preserve the review and relevant evidence privately, with restricted access.
3. Use the official reporting tools. Explain the possible violation and submit only relevant evidence.
4. If removal is refused, check whether an official review route exists. Keep the public response brief and factual. Do not start a chain of rebuttals or promise removal.

Mixed reviews: do not bury the problem under praise

Acknowledge what worked and address the discomfort just as clearly. Praise does not cancel out the problem. If you mention only the location and helpful reception team, a prospective guest cannot tell whether you took the noise complaint seriously.

Worked example: helpful reception, disrupted sleep

Illustrative review: “Excellent location and really helpful reception staff, but the street noise kept us from sleeping properly.”

Before drafting, check how the listing describes the surroundings. Inspect windows and seals, and confirm any alternative before offering it. You control maintenance and the information you publish, not activity in the street.

This short model acknowledges both points without inventing a solution:

“Thank you for highlighting the location and our reception team. We are sorry that street noise affected your rest.”

To adapt it, replace the location, reception service and noise with the specific points in the review. Give the problem its own sentence rather than introducing it with “but”.

Optional sentence for a verified measure only: in this fictional example, if you have already corrected a listing that promised peace and quiet, you could add:

“We have corrected the listing description to explain the exposure to street noise more clearly.”

That sentence describes an information update. It does not mean you have eliminated the noise.

Tip: If no measure is confirmed, stop after acknowledging the problem. Do not promise silence just to give the reply a reassuring ending.

Illustrative variation: a mattress that feels too firm

Check its condition first. Firmness may be a preference; deterioration requires a response about the fault, not personal taste. If the inspection is inconclusive, do not assume there is no defect.

In this fictional example, you have confirmed that the mattress is in good condition. A complete reply would be:

“Thank you for highlighting our reception team's service. We are sorry that the mattress felt too firm for you and affected your rest.”

You do not need to defend the mattress or explain that other guests sleep well.

Decide where the change belongs

Does the listing create the wrong expectation? Correct it. Could noise affect someone's booking decision? Explain it before booking. Use prearrival messages to describe verified, available ways to reduce disturbance, not to reveal an important limitation for the first time.

When useful information is missing, improving the listing does more than making the public reply longer.

What never to publish and how to fix a bad draft

Address the problem without exposing the guest. A profile name, public post or detail mentioned in the review is not an invitation to repeat it. Future guests need to understand how you handle a service failure, not learn about another person's stay.

Use this table to edit your draft. All wording is illustrative and contains no real guest data. Alternatives that acknowledge a failure or describe an action apply only when you have evidence to support them.

Cut the exposure, not the substance

Remove payment history, travel dates, companion details and booking identifiers. Publicly visible does not mean necessary to repeat. Do not paste staff notes into the reply. Turn a verified finding into a service-level explanation without naming who failed or describing internal records.

For personal-data handling in Colombia, check current guidance from the Superintendencia de Industria y Comercio and the privacy procedures applicable to your operation. Do not assume that responding publicly gives you permission to disclose booking information.

Check meaning when switching languages

Use natural phrasing rather than translating word for word. Compare the versions: has an investigation become a completed fix? Has the translation added an admission or promise? Does a polite expression now sound sarcastic? Correct those differences before using the text. The language can change; the facts and the scope of your commitments should not.

Decide who checks, approves and replies

Give every review one accountable owner, even when several people help check it. Shared access without clear ownership can produce duplicate replies, conflicting explanations or an approved draft that nobody publishes.

Choose a tool your team can keep current. A notebook can support a reliable workflow. Software still needs clear responsibilities and manual checks.

1. Assign an owner and a backup

1. Choose who tracks the review from receipt through confirmation that the reply is live. This might be a receptionist or manager.
2. Name a backup for absences and shift changes. Record the handover before the backup continues.
3. Separate fact-checking from publishing access. The housekeeping lead can verify a cleaning issue without needing permission to post replies.

2. Set the approval path

1. Write down which replies the owner can approve and which need the manager's review.
2. Escalate drafts involving disputed facts, possible personal information or serious allegations. Keep publication on hold until that review is complete.
3. Label the approved version and identify who can publish it. Give publishing access only to people who need it.

Tip: Check the original channel immediately before posting. A tracker marked “pending” does not prove that a colleague has not already replied.

3. Hand over the case, not just the draft

Every handover should identify the owner, current status, approved or working version, and next step. An illustrative handover note might say: “Awaiting manager approval; do not publish yet.”

Manually compare the live reply with the approved text and update the record. If the tool fails, keep one working version and check the channel before retrying. An unchecked retry can create a duplicate reply.

What to do when the reply makes things worse

If your published reply contains an error, exposes personal information or triggers another allegation, pause further replies. A rushed response can spread the problem. Regaining control does not mean getting the last word.

1. Stop the exchange and notify the manager

1. Stop repetitive public replies and notify the responsible manager. Establish who can approve the next intervention.
2. Preserve the review, your reply and related messages in a restricted-access record. Do not circulate screenshots in broad staff groups.
3. Identify the problem: an inaccurate statement, exposed personal information, a hostile comment or a possible safety concern. If several apply, address any active danger first.

2. Choose the route that matches the harm

Is there an active safety concern? Prioritize the property's emergency procedure and the appropriate local authorities. Do not wait for the platform to decide on a report before addressing possible danger. Public communication is not a substitute for guest support.

Did you publish personal information? Check the platform's official tools for editing or removing your reply. Do not repeat the information while explaining the mistake. Consult current incident guidance from Colombia's Superintendencia de Industria y Comercio and your applicable privacy procedures to determine the appropriate next steps.

Is a factual statement wrong? Verify the underlying fact before correcting it. For example, if you said a repair was complete when it was only scheduled, remove that claim and communicate only the confirmed status.

Has another hostile comment appeared? Avoid answering every accusation. Decide whether it raises a new issue requiring attention or warrants a report under the current rules in the platform's official help centre. Disagreement alone does not guarantee removal.

3. Keep three separate tracks

Handle private guest support, platform reporting and public correction separately. Check editing or removal options before adding another public reply. Neither removal nor resolution is guaranteed.

Tip: Correct the verifiable fact rather than trying to win the argument. Never publish private screenshots to prove your point.

Common mistakes include deleting internal evidence, blaming the receptionist and describing unfinished work as complete. A correction should narrow the uncertainty, not introduce a new unsupported claim.

Track causes and measure what you can improve

A published reply is not a resolved problem. Track two separate states: what happened to the response and what happened to the underlying failure. Otherwise, a cleanliness complaint can appear closed simply because someone answered the review.

A tracking sheet you can copy

Use this table as a restricted-access template. All three sample rows are fictional, not actions completed at your property. Replace them with verified information and keep items pending when evidence is missing.

Choose internal references that only authorized staff can connect to a reservation. Keep guest names, phone numbers, payment information and full conversations out of broadly shared sheets. Store supporting records separately with limited access. When evidence is missing, write unverified, not “false.”

Tip: Close an action when someone checks the result, not when someone says they have dealt with it.

Four measures to review with your team

Define the reporting period and use consistent rules when comparing results:

1. Share of eligible reviews answered: eligible reviews with a published reply ÷ all eligible reviews detected during the period × 100. Define which reviews allow a response and record exclusions. Do not adjust the denominator to make the result look better.
2. Time to publication: for each reply, subtract the detection date and time from the publication date and time. For an average, divide the sum of those elapsed times by the number of published replies measured. Show pending replies separately, because excluding them can hide a backlog.
3. Verified action closure: actions with a checked result ÷ all actions in the group you are tracking × 100. Identify that group and the reporting cutoff. “Assigned” and “verified” are different states.
4. Repeat issues by cause: count reports of each cause during the period. A count needs no denominator. When comparing periods with different review volumes, also show reports of that cause ÷ all reviews examined.

Use these measures to decide where to investigate and improve. If replies are published but checks remain pending, the communication work is ahead of the operational work. The figures do not establish that replies caused changes in bookings, revenue or ratings.

Finish with a credible reply and a verified next step

Take the review waiting for your response and separate two jobs: preparing a credible public reply and assigning follow-up on the underlying problem.

1. Move the review from pending to ready

1. Classify the review: fair criticism, a disputed claim or mixed feedback. If it raises an active safety concern or exposes personal information, address that situation before continuing with the usual reply process.
2. Check the central claim against available records and with the responsible team member. If the evidence is incomplete, keep that uncertainty in your wording.
3. Choose the relevant template and adapt it. Remove automatic thanks and any statement about action you cannot yet confirm.
4. Strip out private details, internal references and staff commentary. Ask the responsible manager to review disputed facts or sensitive issues before publication.
5. Publish through an authorized channel after any required approval. Assign a follow-up owner and define what evidence will confirm that the corrective action is complete.

Tip: If you cannot verify completion, do not call the issue resolved. Distinguish a pending correction from an ongoing investigation, and mention an investigation only if it has actually started.

2. Run the final check

Copy this checklist into your working record:

• Is every factual claim supported?
• Does the reply accept only responsibility that has been verified?
• Have I distinguished completed work from plans and investigations?
• Would a future guest understand the concern and what I can reliably say about it?
• Is the reply free of private details and internal notes?
• Has someone checked the underlying issue and taken ownership of the next step?

If any answer is no, fix that point before publishing. The reply is ready when its wording is trustworthy. The case is closed only when you have also verified the follow-up.