How to respond to negative Airbnb reviews: 15 word-for-word templates (and what never to say)

The email notification lands the same way every time: a guest has left a review. You open it hoping for five stars and instead find two, or one, with a paragraph that feels wildly unfair, or worse, a paragraph that's fair and stings because it's true. Either way, the question every host eventually has to answer is how to respond to a negative Airbnb review in a way that protects the listing without making things worse in front of every future guest who reads it.

This matters more than it used to. Airbnb now surfaces a Guest Favorite highlight on the listings guests trust most, and it's tied directly to your review average and category scores — cleanliness, accuracy, check-in, communication, location, and value. One bad review doesn't sink that badge by itself, but a bad review paired with a defensive, argumentative, or silent public response does more damage than the original one-star rating ever could. Guests scrolling search results don't just read your star average; a meaningful share of them open the reviews tab and read how you handled the one negative comment sitting there. That response is an audition for every guest who hasn't booked yet.

This guide is built around the actual mechanics of Airbnb's review system in 2026: the 30-day public response window, the strict two-attempt limit on disputing a review, and the six category scores that quietly decide whether you keep your Guest Favorite highlight. It gives you a template for every common complaint type — cleanliness, noise, amenities, exaggeration, and safety-adjacent claims — plus the handful of phrases that will get your response flagged or, worse, make an annoyed guest into a hostile one. None of this requires guessing what Airbnb's policy says; it requires following it precisely, and knowing exactly when a response is the right move and when a dispute is.

Why does one negative review matter so much for an Airbnb listing?#

A single bad review carries more weight than its one data point on a star average suggests, for three overlapping reasons that are worth understanding before you write a single word of a reply.

First, reviews compound into a threshold, not just an average. To earn and keep the Guest Favorite highlight, a listing generally needs at least five reviews in the trailing two years and an average score around 4.9 or higher, alongside strong category ratings and a low rate of cancellations or service issues. A 3-star review doesn't just lower your average arithmetically — on a newer listing with ten or fifteen total reviews, it can be the difference between qualifying for the highlight and not. Established hosts with hundreds of reviews absorb one bad score more easily; hosts in their first year, where every review is a large share of the total, cannot.

Second, guests read the negative reviews disproportionately. Nobody scrolls through pages of five-star praise looking for reassurance; they scroll looking for the one bad review, because that's the one that tells them what could actually go wrong. It's the single most-read piece of content on your listing page after the photos. If that review sits there with no response, or with a defensive, huffy response, the guest reading it draws the worst possible conclusion: this host either doesn't care or gets combative when something goes wrong. If it sits there with a calm, specific, professional reply, the same guest draws the opposite conclusion — this host handles problems like an adult, and that's actually reassuring.

Third, and this is the part hosts underestimate: your response is permanent and public in exactly the way the original stay wasn't. The stay happened once, privately, between you and one guest. Your response to the review sits on the listing for as long as the review does, read by every subsequent guest evaluating whether to book. You're not really writing to the guest who left the review. You're writing to the next hundred people who will read it.

What are Airbnb's actual rules for responding to a review?#

Before drafting anything, it helps to know exactly what the mechanics allow, because guessing wrong here wastes your one shot at a public reply and can cost you a dispute attempt you'll want later.

Airbnb gives hosts a 30-day window after a review posts to publish one public response. That response appears directly beneath the guest's review, visible to anyone viewing the listing — there's no private, host-only version. You get one response per review; there's no back-and-forth thread, so whatever you write is the final word on that review, permanently, unless you later request to have the review itself removed through a dispute.

The response is separate from — and does not replace — a formal dispute. A public response is for reviews you're going to leave up but want to add context to. A dispute is for reviews you believe violate Airbnb's content policy outright: retaliatory content, factually false claims unrelated to the stay, extortion attempts, discriminatory language, or reviews that reference topics unrelated to the actual booking. As of the 2024–2025 policy tightening, hosts get a maximum of two dispute attempts per review, total. Once both are used, whatever the outcome, the review's fate is locked in — it stays or it's removed, permanently, regardless of any new evidence you might find later. That two-attempt ceiling is the single most important operational fact in this whole process: it means your first dispute attempt should be your strongest one, not a quick emotional flag sent the moment you're angry.

One more mechanical point worth internalizing: nothing you do — no response, no dispute, no amount of after-the-fact apologizing to the guest directly — changes the numeric star rating itself. That number is the guest's alone. What you're managing is the narrative around it: whether the text below a 2-star review reads as "host who dropped the ball and argued about it" or "host who owns mistakes and fixes what's fixable." Those two narratives produce very different booking decisions from the next reader, even sitting under the identical star rating.

Should you respond to every negative review, or only some?#

Respond to every review that scores below your average, full stop — with one narrow exception covered below. Skipping a response to a bad review doesn't make it disappear or look less prominent; it just leaves the worst version of the story as the only version on the page. Silence reads as either guilt or indifference to the next guest reading it, and neither helps you.

The exception is a review you're actively disputing under Airbnb's content policy. If you believe a review is retaliatory, fabricated, or references something unrelated to the actual stay (a pricing disagreement handled outside the app, a personal conflict, discriminatory language), file the dispute first and wait for Airbnb's decision before deciding whether a public response is even still relevant — a response to a review that gets removed is wasted effort, and in rare cases a defensive public reply can undercut your own dispute by looking like you're litigating the point publicly instead of through the proper channel.

For the much larger category — reviews that are simply negative but not policy-violating, meaning the guest genuinely didn't enjoy something and said so — always respond. That's the overwhelming majority of 2-, 3-, and even most 1-star reviews: a real complaint about a real experience, phrased more harshly than you'd like. Those get a response, not a dispute, because disputing a review just for being unflattering wastes one of your two attempts and Airbnb will decline it anyway; the content policy protects against abuse, not against guests being unhappy.

What's the right tone for a public response to a bad review?#

The tone that works is almost boringly consistent across every good example: brief, calm, specific, and forward-looking. It reads like someone who runs a business, not someone who's still upset about a Tuesday. Four things every good response does, regardless of the complaint:

• Thanks the guest for the feedback, even when it stings — this signals to future readers that you take input seriously rather than treating every critique as an attack.
• Acknowledges the specific issue in one honest sentence, without over-explaining or making excuses that sound like deflection.
• States plainly what you did or changed, if anything, or notes the context briefly if the claim is inaccurate — without arguing point by point.
• Closes warmly, inviting future guests rather than continuing to litigate the past stay.

What doesn't work is almost as consistent. A response that quotes the guest's review back at them line by line and rebuts each point reads as combative no matter how reasonable the individual rebuttals are — length itself signals defensiveness before a reader even parses the content. A response that's purely an apology with no substance ("So sorry you feel this way!") reads as insincere. And a response that takes even a mild shot at the guest — sarcasm, minimizing their experience, implying they're the problem — is the single fastest way to turn one bad review into a screenshot that circulates on social media or a hosting forum, which does far more damage than the original review ever would have.

Keep every response under about 60-80 words unless the situation genuinely requires more context. Long responses don't read as thorough; they read as an argument you're still having. The goal is a reader who skims your reply in five seconds and thinks "okay, that host handled it well" and moves on to the next photo.

How do you respond to a review about cleanliness complaints?#

Cleanliness complaints are the most common negative review category and the one where guests are, honestly, right more often than hosts want to admit — a rushed turnover, a missed spot, a cleaner having an off day. The template that works acknowledges the specific issue without excessive apology, states the concrete fix, and stops.

When the complaint is exaggerated but not entirely baseless — the guest calls a minor issue "disgusting" or "filthy" when photos or your own inspection show otherwise — resist the urge to argue the adjective. Respond to the substance, not the word choice, and let the disproportion be visible to the reader on its own.

How do you respond to a review about noise, neighbors, or amenities not as described?#

This category covers two very different situations that get lumped together in reviews: things genuinely inside your control (a broken air conditioner, a pool listed as heated that wasn't, a promised parking spot that wasn't available) and things partly or fully outside it (street noise, a neighbor's dog, a construction project that started after your last photo shoot). The response template differs for each, but the shared instinct is the same — own what you own, note context on what you don't, and never let the reply turn into a debate about whose fault the noise is.

For amenity issues inside your control, the fix matters more than the apology. Guests forgive an honest miss far more than they forgive a host who seems unaware the miss happened at all. State the fix in concrete terms — replaced, repaired, updated the listing — so the next reader can see the issue is resolved, not lingering.

For noise or neighborhood issues you can't directly control, the honest move is to acknowledge the guest's experience without accepting blame for something you didn't cause, and to add whatever context helps future guests set expectations — without sounding like you're making excuses.

How do you respond to a rude, harsh, or clearly unfair review?#

Every host eventually gets one of these: a review that feels less like feedback and more like an attack, written in a tone disproportionate to whatever actually happened. The instinct to fight back is strongest here, and it's exactly where a public response can do the most damage if you follow the instinct instead of the template.

The move is the same one that works for exaggerated cleanliness complaints: respond to the substance, ignore the tone, and let the mismatch between the guest's language and your calm reply speak for itself to the next reader. A response that matches the guest's hostility reads, to an outside observer, as two people arguing — and readers side with whoever sounds like the adult in the exchange. That's almost always the shorter, calmer reply.

There's a hard line worth naming explicitly here, because it's the single most common way hosts turn a bad review into a bigger problem: never respond in a way that identifies the guest by more than their first name, references private conversation details, or implies something about their character beyond the specific claim in the review. Public responses live on the internet indefinitely; a response that reads as an attack on a private person, even one who was genuinely rude to you, is the version of this that gets screenshotted and shared in the worst possible context.

• Never quote the guest's review back line by line and rebut each point — it reads as an argument, not a reply.
• Never accuse the guest of lying, even when you believe they are — state facts and let the reader draw the conclusion.
• Never share personal details about the guest (their behavior outside the review, their job, other listings they've stayed at).
• Never use sarcasm, all caps, or an exclamation-point-heavy tone — both read as unprofessional regardless of how justified the frustration is.
• Never mention compensation, refunds, or anything you offered the guest privately — that belongs in a private message, not a public reply.
• Never leave a review response unedited from your first emotional draft — write it, walk away, and reread it the next day before posting.

How do you respond to a review that touches on safety or a policy violation?#

This is the category that deserves the most caution, because it's also the category most likely to warrant a dispute instead of — or in addition to — a public response. A review alleging something like discrimination, a safety hazard, or a fabricated claim about the property sits differently from an unhappy guest venting about the thermostat, and it's worth pausing before you write anything public.

If the claim is true — a real safety issue the guest correctly flagged — treat it with the seriousness it deserves: acknowledge it plainly, state the concrete fix, and don't minimize it, because a defensive response to a legitimate safety complaint is the fastest way to lose the trust of every future reader, and rightly so. If the claim is false, fabricated, or clearly retaliatory (posted after a dispute over a cancellation fee, for instance, and referencing that dispute rather than the stay itself), that's a content-policy violation, and the right first move is a dispute, not a public rebuttal — arguing publicly with a fabricated safety claim, even correctly, plants the claim more firmly in a reader's mind than simply having it removed would.

How do you dispute an Airbnb review, step by step?#

Given the two-attempt limit, treat the first dispute like the only shot you're likely to get. That means gathering evidence before you file, not after, and leading with the clearest possible policy violation rather than every grievance you have about the guest.

1. 1

   Confirm it's actually a policy violation, not just unflattering

   Re-read Airbnb's content policy before filing. A review that's harshly worded but accurate isn't a violation. A review that's factually false, references a topic unrelated to the stay, or is clearly retaliatory for something you did outside the review system (enforcing a cancellation fee, declining a discount) is.

2. 2

   Gather your strongest evidence first

   Messages showing the guest's actual complaint at the time (or the absence of one), timestamps, photos from before and after the stay, and anything showing the review references something outside the stay itself. Weak evidence on attempt one wastes your best chance.

3. 3

   Write a short, factual dispute — not an emotional one

   State the specific policy the review violates and point to your evidence directly. A dispute that reads like a rant about the guest's character, without tying it to a specific policy clause, is far less likely to succeed.

4. 4

   File through the official dispute channel, not a public response

   Use Airbnb's review dispute process, not a message to support agents or a public reply — disputes go through a specific review process and decisions typically arrive within about 48 hours.

5. 5

   Decide on a public response only after the outcome

   If the dispute succeeds, the review is gone and no response is needed. If it's declined, decide whether a calm public response is still worthwhile — often it is, using the same measured template as any other negative review.

6. 6

   Save your second attempt for a genuinely stronger case

   Because you only get two attempts total, don't file a near-identical second dispute in frustration if the first is declined. Use it only if you find materially new evidence or a policy angle you missed the first time.

It's worth restating the asymmetry here because it drives the whole strategy: disputing costs you nothing but one of two total attempts, while responding costs you nothing but a few minutes and some composure. That means the default for any review that isn't a clear policy violation should always be a response, not a dispute — save the dispute mechanism for the cases it actually exists to solve.

How do you turn a bad review into a recovery plan instead of just a reply?#

A single well-handled negative review rarely does lasting damage. A pattern of them, or a bad review left to sit without a plan, does. The hosts who recover fastest treat one bad review as a signal to run a short, deliberate recovery process rather than just posting a reply and moving on.

1. 1

   Separate the signal from the noise

   Read the review once for the emotion, then again for the actual, fixable claim underneath it. Most negative reviews contain one concrete, addressable issue buried in more general frustration — find that one issue.

2. 2

   Fix the underlying issue before you reply, not after

   If it's fixable in a day (a missing amenity, a broken lock, an unclear check-in note), fix it first so your response can state a completed action rather than a promise.

3. 3

   Draft the public response, then wait a day

   Write the reply while the details are fresh, but don't post immediately. A day of distance almost always produces a calmer, shorter version of the same message.

4. 4

   Update your listing or house manual if the complaint reveals a mismatch

   If the guest was surprised by something (a noise level, a stair count, a walk from parking), that's a listing-accuracy gap, not just a one-off bad experience — fixing the listing prevents the next version of the same review.

5. 5

   Watch your category scores, not just the star average

   A dip in one specific category (communication, accuracy) tells you exactly what to focus on next, which matters directly for maintaining a Guest Favorite highlight.

How does AI Emaily help hosts handle review responses without the 11 p.m. scramble?#

Everything above is a discipline you can build by hand: wait a day, write calm, keep it short, know the two-attempt limit. The reason it's hard to actually do every single time is that a bad review usually lands at the worst moment — mid-turnover, between other guest messages, or right as you're trying to sleep — and the instinct to fire back immediately is strongest exactly when your judgment is worst. AI Emaily is an AI-native email client built for property managers and hosts running Airbnb, VRBO, and direct-booking inboxes side by side, and its job here is narrow and specific: put a calm, on-voice first draft in front of you before your own frustration does.

When a review notification arrives, AI Emaily can draft a public response in your host voice — not a generic template, but one shaped by the context you've set: your standard tone, the fixes you've already made to common complaints, and how you typically phrase an acknowledgment versus a factual correction. That draft sits waiting rather than sending itself, because a public review response is exactly the kind of message that should never leave without a human decision behind it. In Copilot mode, every response waits for your one-click approval before it posts — you read it, adjust a phrase if you want, and send, all inside the same window where the review notification arrived. Nothing about the wording, the star rating, or the guest's name is invented; it's built from what you've told the system about how you respond and what's actually true about the stay.

The same inbox also handles the mundane side of review management that eats real time: routing review notifications from every channel into one place instead of three separate apps, flagging the ones that look like potential policy violations worth a dispute versus the ones that are simply unhappy guests, and keeping a full audit trail of every draft and every send so you can see exactly what went out and when — useful if a guest ever disputes what you said, and useful for your own memory when the next similar review arrives six months later. Autopilot is available for the lower-stakes side of guest communication, like acknowledging routine check-in questions, but a public review response is squarely a Copilot-approval message: high-visibility, permanent, and worth ten seconds of your attention before it's live for good.

The value isn't that AI Emaily makes the decision for you — it's that the calm version of your response is already written and waiting by the time you'd otherwise still be composing the angry one. That's the entire gap this closes: not whether you know how to write a good response (this guide covers that), but whether a good response exists yet at the moment you're tempted to post a bad one. You can try it free at app.aiemaily.com/signup; the Free plan covers one connected account, and Pro runs $17.99 a month on the annual plan for hosts managing more.

What's the short version to remember?#

Respond to almost every negative review, publicly, within Airbnb's 30-day window — briefly, calmly, and specifically, never point by point. Reserve disputes for genuine content-policy violations, and treat your first dispute attempt as likely your only real shot, because you get two, total, per review, ever. Fix what's fixable before you reply so the response can state a completed action instead of a promise, and remember at every step that the guest who wrote the review has already left — you're writing for the next hundred people who haven't booked yet.

None of this is complicated, but almost all of it is hard to do consistently at 11 p.m. after a bad guest experience, which is exactly why the hosts who handle this well tend to have a system — templates, a wait-a-day rule, or a tool that puts the calm draft in front of them before the tired, frustrated one gets typed instead.