When a Guest Wants a Refund for a Broken Amenity
Daily operations

When a Guest Wants a Refund for a Broken Amenity

Localsbnb Editorial TeamOctober 29, 20268 min read

A refund request for a broken amenity is decided by three facts, not by how upset the guest sounds: whether the amenity was promised, whether it failed, and what you did in the first hour. This is the order to work through, the three outcomes worth offering, and the record that makes the next case quicker.

Screenshot of the LOCALSBNB rate plan detail page showing nightly rate and cancellation policy fields, used to illustrate where the refund terms attached to a stay are recorded
The refund terms sit next to the rate, which is why the promise is decided by the listing and not by the argument.

The decision isn't whether the guest is annoyed. It's whether the amenity was promised, whether it failed, and what you did in the first hour.

Last updated: October 27, 2026

The message arrives at nine at night: the air conditioning isn't working, and the guest wants their money back. Two separate questions have just landed in one sentence. One is about a machine. The other is about money. Answer them in the wrong order and you'll negotiate a refund before you've established whether there's anything to refund.

Key Takeaways

  • Separate the fault from the feeling. A guest can be furious about something that works exactly as described. That's a service problem, not a refund.
  • Three facts decide it. Was it promised, did it fail, and did you get a chance to fix it before the request?
  • The first hour is the evidence. What you do between the message and midnight is what a later dispute turns on.
  • Three outcomes, one chosen deliberately. Repair, replace or move, or compensate. Picking two by accident is how a small fix becomes a large refund.
  • Write it down the same day. A one-page record turns the next case into a precedent instead of a first time.

Separating the fault from the feeling

Start with what the listing actually said. Not what the guest assumed, and not what you meant to write. Three questions, in this order.

Was it promised? A listing that names air conditioning, a washing machine, a cot or parking has made a promise. A listing that says "fans provided" and doesn't mention air conditioning has made a different one. The gap between those two is where most disputes are actually decided, and it's decided by the listing text, not by the temperature.

Did it fail? Failure is specific. A unit that won't switch on, water that runs cold, a door that doesn't lock, wifi that drops every few minutes. Slow is not the same as broken. Neither is "we couldn't work out how to use it", which is a different problem with a different fix.

Did you have a chance to fix it? This is the line most hosts skip, and it's the one that matters most. A guest who reported the fault at check-in and gave you four hours to send someone is in a different position from a guest who said nothing for three days and then asked for the stay back.

If the answer to the first question is no, you're not looking at a refund. You're looking at a guest who expected something the listing never offered, and the useful response is a clear, kind explanation plus whatever goodwill you'd extend anyway. If the answer to the first question is yes and the second is yes, the only remaining question is what you did about it.

That's why "the guest is upset" is a bad decision rule. It tells you how to speak to someone. It tells you nothing about money.

The first hour, in order

The hour after the report is where the case is won or lost, and the sequence matters more than the speed.

Acknowledge with a time, not an apology loop. One message that says what you're doing and when they'll hear from you again. "I'm calling a technician now and I'll message you by seven whether he's coming tonight" beats four messages that each say sorry and nothing else.

Get one piece of evidence. A photo or a short video of the fault, from the guest, the same evening. Not to doubt them — to know what to bring. A photo of an error code on an air-conditioning unit saves a wasted visit, and it's also the record you'll want if the case is reviewed later.

Try the cheap fix first. The breaker, the isolator switch, the filter, the remote's batteries, the router reboot, the tap under the sink. A surprising share of reported failures are one of these, and a two-minute phone call resolves them without anyone driving anywhere.

Offer a substitute while you wait. A fan, a heater, the second bedroom's unit, a portable hob. The substitute isn't the fix. It's what turns "we're working on it" into something the guest can feel, and it buys you the hours you need.

Set the review point. Decide now when you'll stop trying to repair and start discussing money. Same evening for anything that affects sleep, next morning for anything that doesn't.

All of this happens in writing, in one thread, and the thread is the case file. localsbnb.com keeps the guest conversation in one inbox for Airbnb stays, so the report, the photo, the technician's arrival and the offer sit in sequence rather than across four apps and a phone call nobody wrote down.

Three outcomes worth offering

By the review point you should be choosing one of three, deliberately, and saying which one you've chosen.

Repair. The fault is fixed within a window the guest can live with, and the stay continues as booked. Repair is the right answer when the amenity is restored the same day or the next morning, and when nothing about the stay was lost except inconvenience. Your offer here is usually a gesture — a late checkout, a bottle of something, a discount on a future stay — rather than a refund.

Replace or move. The amenity can't be restored in time, but its function can be. A different unit in the same building, a portable air conditioner delivered that evening, a laundry service when the machine is dead. This is often cheaper than a refund and better received, because the guest wanted a working shower more than they wanted money.

Compensate. The amenity failed, stayed failed for a material part of the stay, and the substitute didn't cover it. Now the question is scope, not whether: which nights were affected, and what proportion of those nights the loss justifies. Anchor it to nights, say it in one sentence, and put it in writing.

What you're avoiding is the accidental fourth outcome: refund plus repair plus an upgrade, offered one message at a time because each message was answered on its own. That's how a broken fan costs more than the booking.

Two boundaries are worth stating plainly. A refund decision isn't a finding of legal liability, and it isn't a platform ruling — those are separate processes with their own rules. And whatever you offer, offer it once, in writing, with the amount and the reason attached.

Recording it so the next case is faster

One page per case, written the same day, five fields: what broke, when the guest reported it, when it was fixed or replaced, what you offered, and what the guest said.

The value isn't administrative tidiness. It's the pattern that shows up after a quarter. The same appliance failing twice in three months isn't bad luck, it's a replacement decision, and the record is what makes that obvious before the third guest arrives.

The record also feeds the listing. If an amenity is out of service for a season, the listing text needs to change the same week, on every channel where the room is sold. A listing that still promises a hot tub in November generates the same refund conversation every month, and each one is avoidable. Editing that line once, in the listing you maintain for each connected channel, is the cheapest fix in this article.

Card: a timeline of the first hour after an amenity is reported, from the acknowledgement through evidence, cheap fix, substitute and the review point
Acknowledge with a time, get one photo, try the cheap fix, offer a substitute, set the review point.
Card: a comparison of the three outcomes for a broken amenity, repair, replace or move, and compensate, with the condition that suits each
Repair, replace or compensate: pick one deliberately, then say which one you picked.
LOCALSBNB — start free

FAQ

Should I refund immediately to avoid a bad review?

No. A fast refund doesn't buy a good review, and it sets the price for the next fault. A fast response does buy time: acknowledge within the hour, say when you'll know more, and keep the money conversation for the review point when you know whether the amenity can be restored.

What if the amenity works but the guest says it doesn't?

Believe the experience and check the equipment. Some faults are real but intermittent, and some are expectations the listing never set. Ask for a photo or a video, test it yourself or send someone who can, and then answer the actual question: whether the stay matched what was promised.

Do I have to refund the whole stay for one broken amenity?

Almost never, and offering it as a first move removes your ability to scope the answer later. Work in nights: which nights were affected, and what part of those nights was lost. A broken appliance on the last morning of a week isn't the same event as one that failed on arrival.

The case is decided in the first hour and settled in the second message. Get the order right and the money question becomes small, specific and answerable. localsbnb.com keeps the conversation and the listing text side by side, which is where a refund argument usually starts and where it can be closed.


This article is general guidance for hosts and isn't legal, tax or insurance advice. What a guest is entitled to, and what a platform's own resolution process requires, differ by jurisdiction and by the terms in force at the time of booking. Check the current terms of each platform you use, and take advice on your own position, before you commit to an amount.

Reviewed by

Localsbnb Editorial Team