Mid-Stay Guest Requests: What to Say Yes To

Most mid-stay requests are cheap to grant and expensive to refuse. The exceptions are the ones worth having a rule for in advance.

Last updated: September 25, 2026

A message arrives on the second afternoon: could we have two more towels, and could we leave at noon? Both cost you almost nothing, and both buy something out of proportion — a guest who tells the next one you were easy to deal with. The requests that deserve a rule are rarer than hosts assume, and they're predictable enough to decide now rather than at four o'clock on a Saturday.

Key Takeaways

• Sort before you answer. Time, cost and who else it touches — five seconds, before you type.
• Four requests are nearly free. Consumables, an hour, bag storage, reversible changes.
• Three need a line. Capacity, safety, and the terms you advertised to everyone else.
• Speed beats generosity. A fast no reads better than a slow yes.
• Write it down. The thread is where a boundary becomes a record rather than a mood.

Sort the request before you answer it: time, cost and who is affected

The reflex is to answer the question that was asked. Do that and you've already lost the only advantage you had, which is a few seconds of thinking before anyone sees a reply. Sort first, on three axes.

Time. Does answering this take a minute, or does it re-order your afternoon? A message you can answer from where you're standing is a different animal from one that needs a cleaner called, a code changed, or a drive across town.

Cost. Is there real money leaving your pocket — a consumable, a call-out, a replacement — or is this something you already own sitting in a cupboard? Most mid-stay requests are the second kind, and that's the part hosts forget when they're feeling put upon.

Who's affected. Only the guest asking? The guest arriving tomorrow? The neighbours, the building, or the person who cleans the unit? A request that touches somebody who isn't in the conversation is the one that needs the most care, because the person who'd complain isn't the person you're talking to.

Two more filters help. Reversibility: an extra hour on check-out can be taken back; a door code given to a fifth person can't. Precedent: will the next guest read this in a review, or hear it from a friend, and expect the same thing? A yes that sets a precedent is a policy decision, not a favour.

That's five seconds of sorting, and it's the difference between having a policy and having a mood.

The four that are almost always worth granting, and why they are cheaper than they look

Consumables. Towels, coffee, bin liners, a spare phone charger, more toilet paper. These cost pennies against the price of a guest who feels watched. Sending someone to a cupboard is the alternative, and it's a worse look than the money.

An hour on check-out, when the calendar allows it. If the next arrival isn't same-day, that hour costs you nothing at all. If it is same-day, it isn't a small favour any more — it's the turnover problem from a different angle, and the answer is no.

Bag storage before check-in or after check-out. It costs a corner of a locked room and it removes the single most common source of mid-stay friction, which is a guest wandering a city with suitcases. Decide where the bags go once, write it in the house rules, and never negotiate it again.

A reversible change to the space. A fan from the cupboard, a travel cot you already own, a chair moved. Reversible is the operative word: if you can put it back in ninety seconds on turnaround day, it's cheap. If it changes what the unit is — furniture out, beds added, a fixture moved — it isn't.

They're cheaper than they look because the real cost of refusing isn't the thing asked for. It's a guest who stops asking and starts deducting. A guest who doesn't ask for towels doesn't go without towels; they write that the place was under-equipped.

The three that need a boundary: capacity, safety and the terms you advertised

Capacity. An extra guest staying overnight, beyond the number you advertised. Occupancy isn't a preference, it's a number with consequences attached: linen, wear, noise, your insurance, your registration if the locality caps it, and the building's own rules if it has any. "Can my friend sleep on the sofa" sounds like a small question and isn't — it changes what you're operating.

Safety. Anything that changes who has access, what's plugged in, or what's supervised. A spare key or a code for someone not on the booking. A space heater in a unit where you've never checked the wiring. Candles. Young children left in a unit with a pool or a balcony. An appliance used for something it wasn't designed for. These are the requests where being liked isn't worth the downside, and the answer is no even when the guest is lovely.

The terms you advertised. Early check-in that collides with a same-day turnover. A pet where the listing says no pets. A gathering in a unit you've described as unsuitable for events. Each of these is a promise you made to other people — to the next guest, to the building, to the channel — and granting it quietly rewrites a term everybody else is relying on.

What the three have in common is the reason they need a line: they're either irreversible, or they change an obligation you owe to somebody who isn't in the conversation. That's the test. If a yes can't be taken back, or if it edits something you published, it isn't a favour.

Write the boundaries down somewhere you can point at them. A boundary that only exists in your head changes with your mood. Airbnb conversations land in one inbox at localsbnb.com, and that's the practical place for a refusal you may need to point at later.

How to refuse one without turning it into a review problem

Answer fast. This is the whole trick, and hosts get it backwards — they go quiet because they're deciding, and the silence is what converts a request into a grievance. An unanswered message at noon is a worse experience than a refused one.

Say no to the constraint, not to the guest. "The unit's set up and registered for four" is a fact about the unit. "I'd rather you didn't" is a judgement about them. Same outcome, completely different reading.

Offer the alternative you can actually deliver. Not "let me see what I can do", which kicks the decision into next week and reads as a soft no anyway. Something concrete: bags can go in the locked cupboard at noon even though the unit isn't ready until three. A nearby left-luggage, if you've checked it exists.

Keep it to three sentences, and put it in the thread even if you said it on the phone. The phone call is a conversation; the message is a record. Two days later, when the same question comes back, you'll want the one you can point at.

Then close the loop. Confirm what you have done rather than only what you can't. It takes one more line and it's the difference between a guest who felt refused and a guest who felt handled.

The rating risk isn't the refusal. Most low scores trace back to things that went unanswered rather than things that were declined, and a guest who was told no quickly, with a reason and an alternative, rarely writes about it.

And pre-make the rules. Put the four cheap yeses and the three boundaries in the house rules and the listing text, and half of these requests stop arriving — which is the cheapest outcome available.

FAQ

What if the request is reasonable but inconvenient for me?

Grant it if it's one of the cheap four. If it isn't, buy five minutes rather than answering immediately — "let me check the calendar and come back to you" is honest when you actually come back.

Should I charge for a late check-out?

A fee on a small favour turns a gift into a transaction, and it reads badly. Handle timing with calendar rules and minimum stays instead, and keep the favour free when the calendar allows it.

What if a guest keeps pushing on something unsafe?

Hold it, in writing, without getting drawn into a debate. It's the one category where being liked isn't worth it, and the message thread is what shows you held it.

Most mid-stay requests are worth a yes, and the four cheap ones cost you less than the time you'd spend deciding. The three that aren't cheap — capacity, safety and your own published terms — need a line you wrote before the phone rang, not one you invented on a Saturday. Sort first, answer fast, put it in the thread, and the awkward ones get rarer once the rules are already written at localsbnb.com.

---

Occupancy limits, safety obligations, building rules and platform terms differ by property and locality, and they change over time; confirm each with your local authority, your building and the channel's current terms. This is general guidance for hosts and isn't legal, tax or platform policy advice.