How Airbnb's Resolution Center actually works (and what a signed acknowledgment does for your case)

Most hosts treat the Resolution Center as a button. Something happened, you click "Request money," you type a number, and Airbnb either moves it or doesn't. When it doesn't, the conclusion is usually that Airbnb sided with the guest, or that the agent didn't read the case.

That's not really how it works. The Resolution Center is not a judge weighing your story against the guest's, and it's not an automatic billing system either. It's closer to a mediator with a strict input check. A case can result in a charge against the guest — but only when the case file clears a specific bar, and only at the reviewer's discretion. Once you understand what that bar is, the denials stop looking arbitrary and start looking like a checklist you either passed or didn't.

Worth saying up front: most of the guests who'd otherwise trigger a Resolution Center case never do, once the fee is something they actively signed instead of something they skimmed. The mechanic below is for the cases that get through anyway. Nothing here is a promise that any particular case will be paid — Airbnb decides, every time, on the file in front of them.

This is a walk through the actual mechanic: what has to be true before a Resolution Center case is likely to move in your favor, and what the file needs to contain.

What the Resolution Center actually is

Start with the thing that's easy to miss. The Resolution Center is a mediation flow. When a host opens a case, Airbnb routes it through one of three paths: the guest accepts voluntarily, an Airbnb reviewer weighs the evidence and makes a judgment, or the case stalls and closes without movement. None of those paths charge a guest's card by mere virtue of the host clicking "Request money."

That matters because the file you submit isn't a button — it's an argument. The reviewer is asking "did the guest agree, before the stay, to be charged this specific amount if this specific thing happened, and did the host actually establish that?" If the answer is yes and you can show it cleanly, the case typically moves; the guest is offered the chance to pay voluntarily, and if they decline, Airbnb decides whether to facilitate the charge at its discretion. If the answer is no — or if it's yes but you can't show it — the case usually stalls.

A fee the guest never agreed to isn't really a fee for these purposes. It's a request. The Resolution Center will forward a request to the guest and ask them to pay it out of goodwill. Almost nobody does.

Two things to keep in mind, because the rest of this post assumes them:

• Mandatory fees belong in Airbnb's pricing fields, not just in your house rules. Cleaning fees, pet fees, and other mandatory charges are supposed to flow through Airbnb's pricing structure. A signed acknowledgment is not a substitute for putting the fee in the correct place on the listing.
• Off-platform collection can violate Airbnb's terms. "I'll just Venmo the guest" isn't a workaround — it's a different problem. The Resolution Center exists because the platform expects collection to happen on-platform.

The two-part requirement

For a Resolution Center case over a rule-based fee — an extra-guest charge, a smoking remediation fee, an early-arrival or late-checkout fee — to have a real chance of moving, two separate things have to be true on the file. Most hosts have one of them. Very few have both.

Part one: the fee has to be disclosed in the listing. Not in a chat, not in your house manual PDF, not in the welcome book on the kitchen counter. In the listing itself — the Additional Rules field is the standard place for rule-tied fees, with mandatory fees in Airbnb's pricing fields — stated as a specific dollar amount tied to a specific condition. "Extra guests beyond 4: $75 per person per night." A number and a trigger. "Please respect occupancy limits" is not a disclosed fee; it's a sentiment. If the amount isn't published on the listing before the booking, the reviewer has nothing concrete to point at.

Part two: the guest has to have acknowledged that fee. Disclosure establishes the fee existed and was visible. Acknowledgment establishes this guest saw it and agreed to it. These are different facts, and the Resolution Center needs both. A fee that's published but never acknowledged tells the agent the rule was on the wall — it does not tell them the guest accepted it as a term of their stay. A fee that's acknowledged but was never in the listing fails the other half. You need the published amount and the guest's confirmation of that exact amount.

Hosts tend to do part one and assume part two happens automatically because Airbnb shows house rules at booking. It doesn't, not in a way the Resolution Center treats as per-fee acknowledgment. The booking-flow "I agree to the house rules" is one bulk click over everything at once. It doesn't record which fees were shown or whether the guest read past the first line. We get into why that matters in why AirCover claims get denied — the disclosure-versus-acknowledgment gap is the same gap that sinks damage claims.

Why "I mentioned it in chat" fails

This is the most common version of a doomed case, so it's worth being specific about why it doesn't work.

You message the guest before the stay: "Just a heads up, there's a $75/night charge for guests over the four-person limit." The guest replies "ok thanks!" You feel covered. Six people show up. You open a Resolution Center case, screenshot the chat, and request the fee. It gets denied or stalls.

Three things are wrong with the chat as evidence. First, a message in a thread is disclosure, not acknowledgment — "ok thanks" is a pleasantry, not a confirmation that the guest accepted a specific dollar amount as a term of the stay. Nobody reading it later can tell what the guest was agreeing to, or whether they were agreeing at all. Second, a chat mention does not put the fee in the listing, which is where part one of the requirement lives. A fee that only ever appeared in DMs was never disclosed in the place that counts. Third, the chat proves you and the guest exchanged words — it does not produce a clean, itemized record an agent can scan in fifteen seconds and act on. Resolution Center staff process these in volume. A file that requires them to read a conversation and infer agreement is a file they'll send to the guest to "voluntarily" resolve.

The chat isn't worthless. It's just not the thing that moves a Resolution Center case in your direction.

The 14-day window

There's a clock, and it's shorter than it feels. Airbnb expects your Resolution Center request and supporting documentation to be submitted within roughly 14 days of the relevant checkout or incident. (Airbnb publishes the current window in its Help Center — read the live version yourself, since terms change.)

Two weeks sounds like plenty until you're inside it. The stay ends. Your cleaner flags the extra guests or the smoke smell a day later. You message the guest, because the platform wants to see you tried to resolve it directly. The guest goes quiet, or denies it, or counter-claims. You wait a few days. You message again. By the time you accept that the guest won't pay voluntarily and you formally escalate, ten or eleven days are gone — and now you're assembling evidence under a deadline, hunting through the chat thread, screenshotting your listing, trying to reconstruct what the guest saw.

A case built in a panic on day 13 is a worse case. And the piece most likely to be missing is the acknowledgment — because it never existed, and there is no way to create it after the fact. You cannot get a guest to agree to a fee, dated before a check-in that already happened. The window doesn't punish you for being slow. It punishes you for not having the file ready before the stay.

What a clean file looks like

Line up the cases that get paid against the ones that stall, and the paid files share a shape:

1. The fee is published in the listing as a number. A specific amount, tied to a specific condition, in the Additional Rules field — visible before the guest booked. PreArrive generates a paste-ready "Additional Rules" block from your itemized fee schedule for exactly this reason: it puts part one on the listing in the format Airbnb expects.
2. The guest acknowledged that exact fee, individually. Not a blanket "I agree to house rules" — a per-line confirmation that this guest saw the $75/night extra-guest fee and accepted it.
3. There's a timestamp, and it pre-dates check-in. The acknowledgment happened before the guest took possession of the property. That's the difference between a term of the stay and an afterthought.
4. There's an audit trail. Ideally two events — the guest opening the disclosure and the guest signing it — each with a timestamp and an IP. This is the spine that makes the record hard to wave away.

That's it. It's not exotic. It's the same standard any billing dispute applies. The catch is timing: every item on that list has to exist before the incident. After the incident, the only thing you can still produce is the chat — and the chat is the thing that doesn't work.

If you want the deeper version of why disclosed amounts and acknowledgment work together, the post on the Airbnb extra-guest fee walks through the most common case hosts try to bill, and the one on denied AirCover claims covers the damage side of the same problem.

The fix is the same in both: collect a signed, timestamped, per-fee acknowledgment before the guest checks in, so that when something goes wrong, you're attaching a finished file — not building one against a deadline. That's the file PreArrive produces. If you want to set one up for your next reservation, you can start here.