Reply in three to five sentences: name the concern, give one fact you can support from your own records, and say what changed. There is no clock on it. What Airbnb publishes is a condition rather than a deadline: “You can post a public response to a published review that someone has left for you as long as you follow our policy on authentic and trustworthy reviews.” The reply waits for the review to publish, and then it sits under it for every future guest.
Here is a finished reply for the most common case, a real problem that has already been fixed. 46 words, three sentences:
“Thank you for flagging the shower drain. It was inspected the morning after checkout and the trap was replaced the same day. I would rather hear about something like that while you are still in the apartment, so please message me the moment anything stops working.”
That does the three things a public reply can do: it shows the complaint was read, it hands the next reader a fact instead of an argument, and it puts the problem in the past tense. It does not remove the review, change the rating, or win the guest back. None of those are available, and a reply written as though they were is the one that does the damage.
What follows is the judgement rather than the wording: which reviews are worth answering at all, four situations that need different replies, and the five habits that turn a response into evidence against the host who wrote it.
Write a short public reply that acknowledges the concern, states the relevant fact, and names the resolution or the next step. Three to five sentences is my own ceiling, not a platform rule, and there is no platform deadline to race either. Airbnb gates the public response on policy rather than on time: the response has to follow the policy on authentic and trustworthy reviews, and the review has to be published before there is anything to answer. Airbnb does print 30 days near reviews, and it belongs to a different action. The person who wrote a review can remove it themselves, up to 30 days from the date it publishes. That clock is not the host’s and it has nothing to do with the reply.
The reviewer is not the audience. That stay is over and the conclusion is already written. The audience is the person reading the listing three weeks from now, and that person is doing arithmetic of their own. Take a host with 20 reviews, nineteen at five stars and one at one star: the average shows 4.8, which is (19 × 5 + 1) ÷ 20, so the rating barely moves and the one-star paragraph is still the thing a guest stops to read. The reply underneath it is the only part of the exchange the host still controls.
A good response lets that reader answer three questions without opening a message thread: what happened, what the host did about it, and whether it could happen to them.
Halina runs three units in Spokane and lists them on Airbnb. When a review lands badly she opens the reservation instead of the reply box, and works through the same five checks I do:
Those five minutes prevent the most common mistake, which is replying to the guest’s tone instead of the guest’s problem. One of Halina’s reviews said the building was “impossible to find”, and the message thread showed the guest had driven past the turn twice without asking for help. She did not write that. She wrote that the entrance photograph now appears first in the arrival message, which is true, checkable by the next guest, and costs the reviewer nothing.
Five sentences, in this order:
Filled in, for that entrance complaint:
“Thank you for the feedback. I am sorry the entrance was hard to find after dark. The door is on the courtyard side and appears in the arrival photographs, though I understand it is easy to miss at night. The instructions now open with that photograph instead of the street address. Anyone who is unsure on arrival can message me and I will walk them in.”
It accepts the inconvenience without accepting the claim that was not true, that the entrance was undisclosed, and it tells the next reader what changed. That is worth more than a sentence-by-sentence explanation of why the guest should have found the door.
A bad review usually carries four or five complaints. The reply should take one or two. A review naming a broken air conditioner, street noise, dated furniture and three days of rain has exactly one item a future guest can act on, and it is the air conditioner. Answer the maintenance failure and leave the weather alone.
The narrow reply reads as confident because it is not a rebuttal, and it keeps details out of public view that nobody asked for. If a guest reported a plumbing leak and disliked the sofa, name the day the leak was repaired and say nothing about the sofa.
If the mechanics are the unclear part, who sees what and when, how Airbnb reviews work covers it. Keep two jobs separate while you are there: the review you write about the guest is a different text with different rules, which is what the host review templates are for. This page is only about the public reply to a review already written about you.
Most of the complaints I read started as a message nobody answered. A guest told at 11pm that the heating switch is behind the bedroom door does not write about a cold bedroom two days later. That is the earlier stage, and it is covered by automated guest messages, check-in and checkout templates, and keeping the response rate at 100%.
Answering guests at 11pm is the part software should do.
Start free — first 500 messagesOr book a demo callThree steps, in this order: acknowledge, context, forward. The labels are mine; the order is what makes a reply readable to somebody who has no idea who was right. Acknowledge what the guest says happened, without confessing to something that did not. Add only the context the next reader needs. Then point forward, to the repair, the changed process, or the way to raise a problem while there is still time to fix it.
Acknowledgement is not agreement. It is proof the complaint was read. One sentence is enough, and the wording decides how the other four are heard:
The first version of each names the subject. The second makes the guest’s reaction the problem, which tells the next reader how their own complaint would be received. A long apology fails in the opposite direction: four sentences of regret read as an admission that the whole review was accurate.
Context has to be short, factual, and supported by something the host already holds: a repair completed after checkout, a rule disclosed before booking, a feature shown in the listing photographs, the help offered while the guest was still in the property. One or two sentences. The public reply is not the case file.
Take a complaint that the apartment was too far from a concert venue. Useful context: the map location is shown before booking and the listing now names the travel time. Useless context: a paragraph arguing that the guest should have looked at a map. Same fact underneath, and only one of the two is aimed at the reader who has not booked yet.
The last sentence answers the only question a future guest really has, which is whether this is still a problem. “The lamp has been replaced” closes it. “The guest never told me” does not, because it leaves the reader wondering what else has gone unreported. The silence is worth mentioning once, as an invitation: “Please report anything that stops working during the stay, so it can be dealt with the same day.”
65 words, three steps, no argument:
“Thank you for the feedback. I am sorry the Wi-Fi outage disrupted your stay. The connection was tested after checkout and the router has been replaced. Please message me as soon as an internet or maintenance problem appears, so there is a chance to look at it while you are still in the apartment. The router in there now is not the one you used.”
It acknowledges the disruption, gives one verifiable fact, and names both the resolution and the preferred next step. It does not accuse the guest of staying silent, guess at the cause, or promise that the internet will never fail again, which is the promise the next outage publishes as a lie.
I read every draft twice. The first pass removes anything the listing, the messages, the photographs or the maintenance record cannot support. The second removes the words that are there to punish the reviewer rather than inform the next guest. The second pass usually cuts more than the first.
Absolute words are the tell: always, never, everyone, spotless. “The turnover was completed and signed off before arrival” is narrower and stronger than “the home is always spotless”, because the first is a record and the second is a slogan a single photograph can break. “The router was replaced after checkout” survives contact with the next review. “The internet never has problems” does not.
When the pattern behind a bad review is communication rather than the property, look at where the thread broke down: late-night guest messages and the mistakes beginners automate into place. Arrival timing has its own version of this, where the complaint is really about an offer that was never clearly limited, which is the subject of early check-in and late checkout.
Keep the reply separate from a removal request. If the content may break a platform rule, preserve the records and report it through the proper channel: getting a review removed and editing, removing and responding cover that process. A public reply arguing that the review should not exist does neither job.
Four situations, four different replies. A cleanliness complaint, a maintenance failure, a broken house rule and a review the records contradict are not the same problem, and one paragraph cannot answer all four. Change the specifics in the templates below and keep the shape. The facts come from the reservation record and nothing else: no diagnosis, no motive, no claim about the guest that would need a screenshot to prove.
Use this when the turnover and the inspection show something different from the review. Do not claim perfection. A photograph shows the state of a room at inspection, not what the guest saw at 1am.
“Thank you for raising the cleanliness concern. The turnover was completed before arrival and the inspection did not record the condition described here. I have added that area to the checklist as a separate line for future turnovers. If something has been missed, please message me during the stay, because that is the only point at which it can be inspected and put right.”
Four sentences, and not one of them calls the guest dishonest. It states what the record shows and leaves room for the record being incomplete, which it sometimes is.
A complaint like that is a message about the inspection as much as about the guest. Halina’s answer was a written checklist with a photograph against each line, so “the bathroom was cleaned” stops being an opinion: the cleaning checklist sets out what to inspect, while cleaning apps for hosts and sharing the calendar with a cleaner are how the same information reaches the person doing the work.
Use this when the guest was right. It is the easiest reply to write and the one hosts most often ruin by adding a defence at the end.
“I am sorry the bedroom air conditioner stopped cooling during your stay. The unit was inspected the day after checkout and the failed part has been replaced. Thank you for telling me, because it is the reason the next guest has a working unit. If anything stops working during a stay, please message me while you are still in the apartment so it can be assessed on the spot.”
Four sentences. It admits the failure without dressing it up and names a specific action, inspected and part replaced, instead of a promise to do better. Vague improvement language is what a reader discounts. A replaced part is a fact.
The repair itself should leave a trail: what was reported, who it went to, what state it is in, what closed it. That is the record a reply quotes from, which is the subject of maintenance tracking for short-term rentals, and task management for vacation rentals compares the tools built to hold it.
Use this only if the rule was disclosed before booking and the reply can be written without naming anyone: not the neighbour who complained, not the rest of the guest’s party.
“Thank you for the feedback. Quiet hours are listed in the house rules shown before booking, and they apply to every reservation because the apartment shares a wall with two neighbours. The message during the stay was a reminder of that rule rather than a complaint about you. Guests who read the house rules first and find them workable tend to have a good stay here, and I would rather set that expectation clearly than leave it to chance.”
Four sentences, no labels. “Bad guest” and “rule breaker” are the words that get a reply screenshotted. Name only the rule in dispute, whether that is occupancy, pets, parties, parking or noise, and leave every other disagreement from the stay out of it. A public reply that reviews the guest is a second review, and the reader can tell.
Careful language here. “The records do not match” is not the same statement as “the guest is lying”, and only the first one is safe to publish.
“The events described here do not match the reservation record or the maintenance log for those dates. I have kept the documentation and raised the review through the platform’s reporting process. While that is open I will not publish reservation details in a public reply. I am available through support if anything further is needed.”
Four sentences and no accusation. Fraud, retaliation and extortion are serious claims, a disagreement about what happened is not evidence for any of them, and a host who publishes one has handed the reviewer a grievance that outlives the review.
According to Airbnb’s Reviews Policy, a factual dispute on its own does not qualify a review for removal unless the review breaks that policy. A host can be certain a statement is unfair and still watch it stay up. That is why the report and the reply are two separate tasks, done in that order: the report can fail, and the reply still has to be there.
Three things change: the concern, the supported fact, the next step. Everything else holds. A dead refrigerator, so the concern is the lost food, the fact is the repair date, the next step is to report it immediately. A staircase nobody expected, so the concern is access, the fact is the listing disclosure, the next step is to check suitability before booking.
Nothing goes in that a screenshot would embarrass you with. No full names, phone numbers, addresses, payment disputes, medical information, or the identity of a neighbour. A private detail always makes the host’s argument stronger and the host’s page worse.
Asking for reviews is a different job from answering them, and it is the one worth handing over. BnBGenius asks each guest for a review after checkout and publishes the host’s review, which is the routine half, and Halina stopped doing it by hand across three units. What it will not do is decide what a bad review deserves: it cannot remove a review, it cannot edit a published reply, and it does not write the response for the host. That decision is one paragraph a month and it belongs to the person whose name is on the listing. The neighbouring tools are the review request flow, review management tools compared, and the 14-day review window.
Response speed and calendar hygiene, handled for you.
Start free — first 500 messagesOr book a demo callThat most reviews do not need a reply. Respond when a short factual clarification helps the next guest, and skip when there is nothing to clarify. If a review makes three complaints and only one describes a condition that is still true of the property, answer that one: three rebuttals read as a dispute, one correction reads as a host who fixed something.
| Review type | Decision | Why | What the reply does |
|---|---|---|---|
| Specific complaint | Respond | The next guest needs to know whether it was looked into. | Names the concern and the action taken. |
| Inaccurate claim about the property | Respond | A short correction stops a wrong expectation spreading. | Points at the disclosure without insulting the reviewer. |
| Problem already resolved | Respond | The repair closes the issue for everyone reading later. | Names the item repaired or the instruction rewritten. |
| Vague feedback | Optional | There may be no fact to clarify at all. | One line of acknowledgement, or nothing. |
| Rating with no text | Skip | There is no complaint to answer, and a guess creates one. | Nothing. Do not invent the reason. |
Airbnb calls it a public response, and public is the operative word: once a review is published, anyone can read it and the overall star rating that came with it. The editing rule Airbnb publishes covers the review rather than the reply: “You can edit a review for a home until your review is published.” On changing a response after it goes up, Airbnb publishes nothing either way that I can find. I do not build a habit on a gap, so I draft the reply in a text file and paste the version that survives. Halina’s air-conditioner reply took three drafts; the two she threw away both ended with a sentence about the guest instead of about the unit.
Where the dispute is serious and a second person is available, split the reading in two: one checks that every factual claim is supported, the other reads only for tone and for private information. A host working alone gets the same result by reading twice with the two questions kept apart, or by leaving the draft overnight and opening it cold. Those are my working habits, not rules.
Do not publish angry. Write it outside the response box, come back to it, and ask of every sentence whether it helps somebody decide about a booking. If a sentence is there to embarrass the reviewer, delete it. That is the sentence that gets quoted.
I keep a defensive reply under about 150 words, which is my limit and not an Airbnb one. Most good replies are half that. A response that needs three paragraphs is usually a private dispute being conducted in public, and the public is on nobody’s side.
Photographs, logs, invoices and the message thread decide what the host believes. They do not belong in the reply. Halina’s turnover inspection produces six photographs per unit and not one of them goes into a public response; the sentence carrying all six is “the pre-arrival inspection did not record the condition described here”. If the platform asks for evidence during a dispute, it goes through the private channel, where it counts for something.
The same restraint applies to messages. A host may have twenty of them showing every attempt to help. “Help was offered during the stay” says it. A message-by-message timeline says something else, which is that this host will publish a conversation.
A well-written reply repairs nothing. After publishing, turn the usable part of the complaint into one task: replace the router, reshoot the parking photograph, reseal the shower, put quiet hours on the door, add a landmark to the arrival message. One task that is finished beats five promised in public.
If the same confusion turns up in three reviews, the fix is upstream of the reply, in the listing and in the guest journey. That is the ground covered by what to change in the listing, how the owner side works, and automation software for hosts.
Where software helps is volume, and the price tells you what kind of help it is. BnBGenius answers guest messages on Airbnb and VRBO around the clock, asks for the review, publishes the host’s review, and opens cleaning and repair tasks after checkout. It installs as a Chrome extension in about five minutes, with no API keys and no password handed to anyone, because it reads the host’s own dashboard inside the host’s own browser. Halina pays for 3 units on Pro, which is 3 × $10, or $30 a month, and it is the same $30 in February as in July; a manager charging a percentage of rental revenue invoices the July number. The line has to be drawn honestly, too: BnBGenius is not a property management system, and it does not remove reviews, edit a published reply, sync calendars, run direct bookings, set prices, or keep owner accounting.
Hosts deciding where any of this belongs can read Airbnb automation, whether a small host needs a PMS, and what AI property management actually covers. Better communication prevents some of the complaints that become bad reviews. None of it makes a published review disappear.
A no to any of the three sends the draft back. A review with no actionable content gets no reply at all, because silence beats speculation and a three-sentence correction beats a long attempt at the last word. The review stays up either way. What the host decides is whether the paragraph underneath it reads like judgement or like a grievance.