A Refund Request for a Bug or Amenity Failure

Most refund requests are decided by evidence you already have, not by negotiation. Collect first, offer second, and write the outcome down.

Last updated: October 18, 2026

A message lands at nine in the evening: the air conditioning has quit, or there's a bug in the kitchen, or the shower runs cold after four minutes. The guest wants money back. The reply you send in the next hour decides whether this is a repair with a discount attached or a case that runs for three weeks. The difference is rarely generosity. It's how quickly you sort the complaint.

Key Takeaways

• Sort before you answer. Fault, shortfall or preference. Only the first two involve money, and they involve different amounts.
• Ask for one thing at a time. A photo with a timestamp, the specific item, when it started. Three questions in one message gets you one answer.
• Offer a remedy in the first reply. A time window for a repair beats an apology, and it moves the conversation off the refund question.
• Price by affected nights. A refund covers the nights the guest lost, not the whole stay, unless the whole stay was lost.
• Write the outcome down. The message that confirms what was agreed is what ends the case, and what protects you if it reopens.

Separating a fault from a preference

Three categories, and the whole conversation changes depending on which one you're in.

A fault is something that doesn't work. No hot water. A lock that won't latch. A fridge that's warm. A bug in the kitchen at midnight. The test is simple: would the next guest hit the same thing tomorrow? If yes, it's a fault, and it's yours to fix.

A shortfall is something that works but isn't what the listing promised. The "sea view" is a slice of blue between two buildings. The "quiet street" is next to a delivery depot. The "two-minute walk to the station" is fifteen. Nothing is broken, and the guest has a legitimate point about the gap between the description and the reality.

A preference is a guest who would like a different unit, a softer mattress, a later check-out, a room on a higher floor. Nothing is wrong. They'd simply rather have something else.

The categories aren't academic. They decide what you owe. A fault earns a repair and, if the repair takes time, money for the nights affected. A shortfall earns an apology and sometimes a gesture, because the description is your responsibility. A preference earns sympathy, help if you can give it, and no refund.

One warning about the grey zone. A guest who reports a fault late in a stay, after four nights of not mentioning it, may have a genuine fault and a slow reaction to it. Ask when it started. The answer tells you whether you're refunding one night or four, and it does so without an argument.

The evidence you ask for first

Ask for one thing, in the first reply, and make it easy to give.

For a fault, that's a photo or a short video with the phone's timestamp on. Not a written account. A thirty-second clip of a shower running cold, or a photo of the bug, or a picture of the thermostat showing the set temperature next to a room that isn't cooling. Visual evidence takes ten seconds to produce and settles most questions on its own.

For a shortfall, the evidence is already in your listing: the photo you published, the sentence you wrote. Pull it up before you reply. If the listing overstated the case, say so plainly and offer the gesture. If it didn't, point at the wording without sounding like a lawyer.

For a preference, there's no evidence to collect. There's a decision about whether you can help. A late check-out costs you a cleaner's hour. A different unit costs you a turnover. Neither is a refund, and both are cheaper than one.

Two habits make this quicker. Ask for the booking reference and the exact item in the same line, so you're not chasing a thread. And keep your own evidence current: the pre-arrival photos, the inspection note, the date the kettle was replaced. When a guest says the kettle was broken on arrival, a photo from the morning of check-in ends the discussion in one message.

LOCALSBNB's inbox connects to Airbnb, so the request and everything you've already exchanged sit in the same thread. Reading back through it before you answer takes a minute and often shows that the guest mentioned the problem on night one, which changes the arithmetic.

Two remedies that end most cases

Almost every fault closes with one of two moves. Pick one in the first reply, and say which one you're doing.

Fix it, with a time window. "I can have someone there between ten and eleven tomorrow morning" does more work than any apology. It converts a complaint into a schedule. If the fix needs a part, say when the part arrives and what the guest can use in the meantime. A fan tonight, a spare kettle in an hour, the neighbour's parking space while the plumber works.

Refund the affected nights. If the fault can't be fixed inside the stay, or the guest has already lost the use of the thing they paid for, price it by nights. Two nights without hot water in a five-night stay is two nights, not five. Work out the nightly figure from what the guest actually paid, not from your rack rate, and put the number in the message rather than inviting the guest to name it.

A gesture sits alongside those two, not instead of them. Waiving a late check-out fee or covering a taxi is a goodwill move. It's not a remedy, and it shouldn't be offered as one, because a guest who accepts a gesture and still wants a refund will feel cheated twice.

What to avoid is the open-ended offer. "Let me know what you think is fair" invites a number you'll refuse, and the refusal is what turns a small case into a formal one. Name a figure, explain the nights it covers, and leave room to move once.

When a full refund is the cheaper answer

Sometimes the arithmetic points the other way, and hosts lose money by being careful.

Full refund is usually right when the unit was unusable and stayed unusable. No water for the whole stay. A broken lock on the only door. A bug problem that needs treatment, not a spray. In those cases the guest didn't receive the product, and a partial refund is a negotiation about a stay that never happened.

It's also right when the failure arrived at the worst possible hour. A family arriving at eleven at night to a unit that's forty degrees inside, with no way to cool it until morning, has lost the first night entirely, whatever you do next. Refunding that night in full, immediately, costs less than the argument about whether a fan counts as a remedy.

And it's right when the case has already cost more than the refund. Add up what a week of messages, a platform case and a two-star review costs you against one night's rate. The review is the expensive line, because it sits on the listing for years and it's read by every guest who compares you to the unit next door. localsbnb.com puts ADR and RevPAR on the Home dashboard, which is the honest way to see what a damaged month does to the numbers you actually keep.

That isn't an argument for refunding everything. A host who refunds on request teaches every future guest that the request works. The distinction is fault versus preference, and it holds up in both directions: refund the faults quickly and generously, and decline the preferences clearly, once, in writing.

Whichever way it goes, end with a message that states the outcome in plain terms. The amount, the nights it covers, when it will be processed, and what happens next. That message is the case file. It's also the thing that stops the same conversation restarting in a week.

FAQ

How fast should I reply to a refund request?

Within the hour if the guest is still in the unit, and the same day if they've left. Speed matters less for the answer than for the signal: a host who replies in twenty minutes is a host who's handling it.

Should I refund the cleaning fee?

Usually not, unless the unit wasn't cleaned. The cleaning fee pays for a clean that happened. If the fault was dirty conditions on arrival, that's the one case where it comes back.

What if the guest asks for more than I offer?

Say what the offer covers and why, once, and then stop negotiating in the thread. If they want to escalate, that's their right, and a clear written record helps you more than a series of concessions.

Do I have to follow the platform's refund rules?

The platform's current terms apply to bookings made through it, and they decide how a case is handled if it's escalated. Read them before you answer rather than after. Your own policy sits inside those terms, not above them.

Handle the next one the same way and the pattern does the work for you. Sort the complaint, ask for one piece of evidence, name a remedy with a time on it, and write the outcome down. If you want the thread and the nightly figures in one place while you work through a case, the product pages at localsbnb.com show how the inbox sits next to the dashboard.

---

This is general advice for hosts, and it isn't legal advice. Refund rules, consumer protections and platform terms vary by place and change over time; check the current requirements of your local authority and the current terms of each platform you use.