The notification arrives while you're arranging a cleaner, finding a spare key and trying to remember whether the plumber actually went round. Three stars. The guest says check-in was confusing, the flat was cold and nobody helped.
You remember answering six messages. You also have a fairly strong first draft of your reply. Leave that draft where it is for a moment.
Knowing how to respond to a bad Airbnb review means doing two jobs: dealing fairly with what happened and showing the next guest how you handle a problem. A public argument rarely helps with either. A short, specific answer, followed by an actual operational fix, usually gives you something more useful to work with.
The quick version
- Read the review and the complete message history before replying.
- Separate a genuine service failure, a misunderstanding and a possible policy violation.
- Address the main issue without publishing private guest information.
- Describe improvements only when they have happened or have a definite plan.
- Request removal through Airbnb if you believe the review breaks its Reviews Policy.
- Give any practical fix an owner, a deadline and a place in the property notes.
Airbnb's own guidance recommends a short, friendly public response and specific details about improvements. It also distinguishes responding to feedback from requesting removal of a review that may breach its policy. (Airbnb)
Write the reply for the next person deciding whether to book. They need to see that you understand the problem and can deal with it.
First, work out what actually happened
A guest's review is one account of the stay. Your memory is another. Before composing a public answer, bring the useful evidence together.
Read the conversation in order. Check the arrival instructions they received, not the improved version you uploaded yesterday. Look at the housekeeping handover, maintenance notes and any promises made by another member of the team.
The difference matters. You may have an excellent parking photo now, but the guest might have been sent a blurry image of the wrong gate. An accurate explanation of today's setup does not resolve yesterday's experience.
Ask four questions:
- What was the guest expecting? Check the listing and information sent before arrival.
- What happened during the stay? Use messages, timestamps and relevant records.
- What did the team promise? A promised callback that never happened may matter more than the original fault.
- What is still unresolved? Separate an open service issue from a disagreement about the rating.
Keep this fact-finding proportionate. You don't need a dossier because someone disliked the sofa cushions. You do need to know whether a report of no hot water reached anybody who could act on it.
Choose the right route for a bad Airbnb review
A genuine problem needs a straightforward answer
If the cleaner missed a cupboard, the heating instructions were wrong or the guest waited outside, acknowledge it. You can explain relevant context without making the guest read a defence statement.
“The previous guests left late” may be true. It does not help the person who arrived to an unfinished clean. The useful information is what you did then and what you have changed since.
Avoid making the public response the first time your team takes the complaint seriously. If there is an outstanding practical or financial issue, assign it to someone and handle it through the appropriate booking and support channels.
A misunderstanding needs clarification, not point-scoring
A review may say that parking wasn't included when the listing described a paid car park nearby. You can clarify that calmly. You can also check whether the information was prominent enough to be noticed.
“It was in the listing” is sometimes the full factual answer and still an unhelpful reply. If five guests miss the same sentence, move the sentence.
The same applies to a sofa bed, shared entrance, stairs or a bedroom facing a busy street. Accuracy includes helping the guest form the right expectation, not simply ensuring a detail exists somewhere.
A possible policy violation belongs in a removal request
Airbnb allows hosts to request removal when they believe a review does not follow its Reviews Policy. A negative rating alone does not establish that. The policy specifically says disagreement with a star rating is not, by itself, grounds for removal. (Airbnb Reviews Policy; removal requests)
Read the current policy and identify the provision you believe applies. Include relevant evidence and explain the connection clearly. Avoid presenting every unpleasant review as retaliation or promising colleagues that support will remove it.
You can prepare a measured public response while a request is considered. Keep any private booking details or evidence intended for support out of the public reply.
How to write the public response
Most replies can follow a simple shape:
- Acknowledge the specific concern.
- Apologise for a failure you have established, or clarify a material misunderstanding.
- Describe the useful action taken.
- Stop before the reply becomes an argument.
One compact paragraph is often enough. Match its length to the issue rather than trying to answer every sentence in the review.
Use ordinary language. “We've replaced the worn lockbox and added a photograph of the entrance” says more than “we take all feedback extremely seriously”. Avoid claiming a repair is complete when the part is still sitting in somebody's shopping basket.
The examples below are illustrative drafts, not accounts of actual stays. Use them only when their facts match what happened.
Example 1: the cleaning complaint was justified
Thank you for flagging the missed cleaning in the kitchen. That should have been picked up before your arrival, and we're sorry it wasn't. We've reviewed the handover with the housekeeping team and added the oven and cupboard interiors to the final inspection.
This reply names the failure and the change. It does not identify the cleaner, blame an agency or promise that nothing will ever be missed again.
Before using it, make sure that inspection step has actually been added. A guest who returns and finds the same problem will quite reasonably remember the promise.
Example 2: check-in instructions caused confusion
We're sorry you had trouble finding the entrance after your journey. The directions did not make the two gates clear enough. We've replaced the arrival photos and added a short walking route from the taxi drop-off point to the correct door.
The problem here is the route, not the guest's ability to read. The operational follow-up is to test the revised directions with someone who has never visited the property. Our guide to common check-in problems covers the details worth checking.
Example 3: a heating issue remained unresolved
We're sorry the flat was uncomfortable and that our follow-up did not resolve this during your stay. The heating has now been inspected and repaired, and we've changed the handover so an unresolved heating report remains with a named member of the team until it is dealt with.
Use that wording only after the inspection and repair. If work is still arranged rather than finished, say so accurately. The guest reported both a fault and a support failure; a reply about the thermostat alone would miss half the complaint.
Example 4: the guest expected private parking
We're sorry the parking arrangements were frustrating. The apartment uses the nearby public car park rather than a private bay. We've made that distinction more prominent in the listing and arrival message, including the walking route and where to check current charges.
This corrects the expectation without reproducing the guest's messages or telling them they should have paid more attention. If your listing actually promised a private space, the facts call for a different response.
Example 5: you disagree with the description of your response
We're sorry the stay left you disappointed. We did respond to the reported Wi-Fi problem during the visit, but we recognise the connection was not restored as quickly as you needed. We've since updated the troubleshooting notes and the route for reporting an unresolved outage.
A measured clarification can be useful. A minute-by-minute transcript is rarely necessary. Choose the detail that changes a future reader's understanding and leave out the rest.
What to keep out of the reply
Avoid sarcasm, threats and comments about the guest's personality. Even if the conversation was difficult, the next reader has no reason to enjoy watching it continue.
Don't disclose phone numbers, access codes, medical details, payment information or private conversations. Don't identify a member of staff to shift the blame. A public review response should not become an accidental incident report.
Also avoid offering a discount or refund in exchange for a positive review, a changed review or the removal of criticism. Airbnb's Reviews Policy prohibits exchanging something of value for reviews or withholding them. Keep any service recovery decision separate from attempts to influence the review. (Airbnb Reviews Policy)
Finally, resist the sweeping promise. “This will never happen again” is difficult to defend in a building containing plumbing, Wi-Fi and human beings. A specific change gives the reader something they can actually understand.
Can AI help you respond to a bad review?
AI can help shorten an angry draft, identify the main complaints and suggest a calmer structure. Give it the relevant facts and ask it to leave unknowns unresolved. Remove personal details that are unnecessary for the task.
A useful instruction is:
Draft a brief, calm public response using only these verified facts. Acknowledge the guest's concern. Do not invent an apology for something unverified, a completed repair, compensation or a promise about future stays. Flag anything that needs a human decision.
Read the result yourself. AI can make a response sound reassuring while quietly adding a repair that never happened. It can also smooth away a genuine admission until the reply says almost nothing.
For a sensitive complaint, keep the decision and final wording with a person. For recurring questions before they reach a review, invest the effort in clearer guest instructions. That is where better information can help the next stay.
Turn the review into a small operational task
A review response can be finished in ten minutes. The actual fix may disappear into a team chat for three weeks.
Give the issue a clear home. Record the property, the problem, who owns it and how someone will verify the improvement. Keep observations separate from assumptions: “guest couldn't find spare towels” does not automatically mean “there were no spare towels”.
For example:
Issue: guests cannot tell which parking bay belongs to the flat. Owner: property manager. Action: photograph the bay from the driver's approach, confirm the bay number and update the arrival guide. Check: ask a colleague to follow the instructions before the next arrival.
Useful improvements tend to be fairly ordinary:
- Put the Wi-Fi details where people first look for them.
- Replace a lockbox photograph taken before the entrance was repainted.
- Explain which heating control serves which room.
- Add spare towels to the turnover check, including their storage location.
- Put the checkout time and key-return step in the same short message.
Those are also the sorts of guest questions that can hurt reviews when nobody notices the pattern. A repeated complaint deserves a process change, even if each individual stay had slightly different circumstances.
Make the next guest's stay easier
A bad review doesn't need an elaborate public defence. It needs a fair reading, a proportionate reply and a fix that survives beyond today's inbox.
If the same access, parking, heating and Wi-Fi questions keep returning, letbloom can help guests find property-specific answers from your guidebook on WhatsApp, with urgent or unusual issues passed back to your team. Keep the notes accurate, give unresolved problems a human owner and make it easier for guests to get help while you can still improve their stay.
