A Refund Conversation Backed by Records

A refund argument is won or lost before the conversation starts. The order you show the evidence in is the argument.

Last updated: November 1, 2026

Guests rarely ask for a refund because of the money. They ask because something they expected didn't happen, and the fastest way to close it is to show, in order, what was agreed, what was said and what the flat looked like. Four steps, sent once, end more of these than twenty messages do.

Key Takeaways

• Anchor on what was agreed at booking. The terms the guest actually saw are the only baseline both sides share.
• Sequence beats volume. Terms, then the message that set the expectation, then photos with dates, then one decision. Sent in that order, the file argues for itself.
• Never send evidence in a stream. A photo before the terms invites the guest to argue about the photo.
• Cut the phrases that weaken a file. "We always try to" and "as you know" read as negotiation, not as record.
• Close in writing, once. A decision stated in one message is a decision. A decision spread over five is a position.

Start from what was agreed

Every refund conversation has a baseline, and it's the listing as the guest saw it when they booked. Not the version you improved last month, not the house rules you rewrote after the stay. The one that existed at the moment of booking.

Pull that version first, with its date. If the listing has changed since, say so and show both — a host who produces the older text before being asked looks organised, and a host who produces the newer one looks like they're editing history.

Then the messages. Somewhere in the thread there's a sentence where an expectation was set, and it's usually not the one you remember. It might be your own "the street is quiet at night", or the guest's "so we can check in early, right?" followed by your "should be fine". Both of those are evidence, and the second one is the kind hosts forget they sent.

Then the practical part: dates. Arrival, the first message about the problem, the first reply, the visit, the departure. A row of dates does something no paragraph can, because it shows whether a host responded in hours or in days without anyone having to claim it.

Only then do the photos make sense, and that's the point of the order.

The four-step evidence order

Step one is the terms. The listing text, the house rules, the cancellation terms, the check-in window — as the guest saw them, with the date they were live. One document, not a summary of one.

Step two is the message where the expectation was set. Quote it, don't describe it. "You told me the flat would be ready at 2" and a screenshot of the sentence are different weights of evidence, and only one of them can be argued with.

Step three is photos and dates, in sequence. Not a folder — a sequence. The bathroom on arrival, the same bathroom on day two after the guest reported it, the same bathroom after the visit. Three images in order tell a story that thirty images in a grid destroy.

Step four is one closing message with the decision. What you're doing, what you're not doing, and by when. That message is the end of the argument, not the middle of it.

A note on where the record comes from. The booking side of a file is mostly dates and states — when the stay started, whether the room was occupied, what was due out and when. localsbnb.com answers those read-only, from the same calendar the four connected channels write to, so the sequence in step three can be built from a record rather than from memory. Memory is what makes hosts send the wrong photo in the wrong order, usually at eleven at night.

One piece of background worth knowing if your dispute concerns a rule rather than a stay. Airbnb announced changes to its house rules on 20 October 2026, applying to bookings made from 20 November 2026. Under the new terms, hosts can't charge guests penalties themselves, and the rules have to be disclosed in a set section before booking, as reported by BBC and Yahoo Travel on 31 October 2026. The practical effect on a file is the same as always: what the guest saw before booking is the thing you'll be measured against.

What not to say

Most weak files are weakened by three habits, and none of them is about facts.

The first is the character reference. "We've hosted for six years and never had a complaint" is true and irrelevant. It doesn't answer the question the guest asked, and it reads as a defence rather than a reply.

The second is the hedge. "We always try to be flexible" invites the guest to test how flexible. If the answer is no, the earlier sentence becomes the thing they quote back.

The third is the diagnosis. Telling a guest what they must have done — left the window open, used the wrong setting, dropped something — is the fastest way to turn a refund request into a grievance. Describe the state of the flat with a date, and let the sequence do the implying.

There's a fourth habit specific to written channels: answering a different question than the one asked. If the guest asks whether the cleaning fee comes back, answer that. A careful paragraph about the stay overall reads as evasion, and evasion is what makes people escalate.

Say less, date more. A file with six dated lines and no adjectives is harder to argue with than a page of explanation.

Closing it in writing

End with one message that states the decision, the reason in a single sentence, and what happens next. Then stop.

The stop is the hard part. Hosts keep talking because silence feels like losing, and every extra message adds a sentence the other side can pull apart. The argument is already in the file. A second pass usually makes it worse.

If the answer is partial, say which part and which doesn't, in the same message. Two decisions delivered in two messages become three arguments.

Then write the outcome into your own records, dated, next to the booking. Not for the platform — for the next time. The pattern behind refund requests is usually a listing that overpromises in one specific sentence, and you can only see it if the outcomes are written down somewhere other than your memory.

And if the guest comes back with something new — a photo you hadn't seen, a message you'd missed — reopen it. A closed file that turns out to be wrong costs more than a reopened one that turns out to be right.

FAQ

Should I send everything at once or in stages?

At once, in order, in one message or one attachment. Staged evidence lets the other side answer each piece separately, which is how a simple file turns into a correspondence.

What if I don't have the listing as it was at booking?

Say so, and use the earliest version you do have with its date. A missing document is a gap; an undated document is a problem, because it invites the assumption that you've edited it.

Does a refund request mean the stay went badly?

Not necessarily. Plenty of requests come from a mismatch between one sentence in a listing and what the guest found. That's a listing problem more often than a hosting one, which is why the outcome is worth writing down next to the booking.

Four steps, sent once, closed in one message. localsbnb.com can't decide a dispute and doesn't try to. What it can do is keep the dates and the room states in one place, so the sequence you send is the one that actually happened.

---

This article is general guidance for hosts and isn't legal, tax or insurance advice. Consumer rights, cancellation entitlements and what a guest may claim differ by jurisdiction and by platform. Confirm the current terms of each platform you use, and take advice on any consumer-law question that turns on your local rules, before you commit to a position in writing.