Overbooking: The Order You Fix Things In

The first ten minutes decide the cost. The guest standing in the lobby outranks the channel that caused the overlap, and the calendar outranks both of them.

Last updated: October 26, 2026

Two bookings, one night, and a guest twenty minutes away. It costs money either way. The order decides how much. House the person at the door first, close the night second, and open the channel only after those two are done.

Key Takeaways

• The guest outranks the channel. A channel is a queue. The person at the door isn't.
• Block the night, don't cancel the booking. A cancellation frees the night again and erases the evidence of the overlap.
• Move the booking that hasn't travelled. If somebody has to change, pick the guest who hasn't started their journey.
• Look for the second booking, not the guilty channel. Overlaps come from a sequence, and the sequence is usually human.
• Write the cause the same night. A month later you'll remember the apology and not the mechanism.

Guest first, channel second

Before you dial anyone, decide what you can actually deliver. Three options cover most nights: another unit you control, a hotel room you book and pay for, or a refund plus help finding somewhere. Pick the one you can confirm in the next twenty minutes, and only that one.

Then call the guest. Say what you know, say what you don't, and offer only what you can deliver. Guests forgive an overbooking far more easily than they forgive being told three different things in an hour, so don't promise the hotel until the hotel has a room.

The channel can wait twenty minutes. Nothing you type into a channel dashboard changes where the guest sleeps tonight, and a message sent one-handed at eleven at night is how hosts end up modifying the wrong reservation. The channel's own record survives the delay. Your guest's patience doesn't.

This is where the cost sits, and it's worth being blunt about it. You pay for the difference between the room you sold and the room you can find. You pay for the distance between them. You pay for the hour. The order doesn't remove any of those. What it stops is paying for them twice, because you fixed the channel first and the guest second.

What the guest needs tonight is smaller than it feels. An address they can reach, a door they can open, and one sentence about who is paying for the taxi. Everything else — the apology, the explanation, what happens to the second booking — can wait until morning. Guests remember the bed. They rarely remember the reasoning.

Closing a night without erasing the record

The moment you know two bookings share a night, close that night on that unit. Not after the calls. Now. A same-day rate can take a third booking while you're on the phone, and a three-way overlap is a much worse evening.

Closing is a calendar action, and it takes one move: block the dates on the unit. What you block, you stop selling. What you cancel, you release.

One detail belongs to closing rather than to the calls. If the second booking has self check-in, that guest may already be holding a door code. Change the code, or keep the unit open for the person you're actually housing. A code that works for two bookings is the same overlap happening a second time, an hour later.

That distinction is the whole point. Cancelling the duplicate frees the night back into the market, which is how a two-booking night becomes a three-booking night. It also deletes the thing you need most tomorrow, which is the visible record that two bookings were held for the same night. Leave the duplicate in place, marked as unresolved, and deal with it once the guest is asleep somewhere.

There's a second reason for keeping it. When you reconstruct the cause later, the timestamps on the two bookings are the evidence. Which one came in first, which one came in while the night was already sold, and what the calendar showed at that minute. A cancellation collapses that into one line that tells you nothing.

On a direct connection the block is one action in one place, which is the point of having a calendar at all. localsbnb.com holds every unit's availability in one calendar, so the night you close is the night you closed. Doing the same thing in four dashboards at eleven at night is how you block three of them.

Who to call, in what order

The calls have a sequence, and each one unblocks the next.

Start with the person who can produce a room: your cleaner, your co-host, whoever holds spare keys. Ask a closed question. Can another unit be ready tonight, and by what time? If the answer is no, you've eliminated an option in thirty seconds.

Then the second guest, if one of the two bookings has to move. Choose the one who hasn't travelled. A guest still at home can be moved with a message, an apology and a refund, and most will take it. A guest in a taxi at midnight can't be moved at all, only housed.

Then the channel, last, and in writing. What you want from that conversation is narrow: confirmation of what the guest has been told, whether the booking can be relocated, and a reference you can quote later. Not a ruling. Rulings arrive days later and don't help anyone tonight.

Then whoever needs to know for tomorrow: the cleaner who now has a room to turn twice, and the neighbour who has a key if the second unit is theirs.

Give the cleaner a time, not a task. Unit 4 by six is actionable. Can you sort out unit 4 starts a conversation at the worst possible moment. And if the second unit was cleaned yesterday with nobody in it since, say that first, because it changes what's possible tonight.

The reason the channel comes fourth isn't that it matters least. It's that it answers on a queue, and everything above it answers on a phone.

The note that stops it recurring

Before you sleep, write three things. Which booking arrived second, and on which channel. How far apart the two bookings were, in minutes or hours. And what the calendar showed at that moment, in your own words.

That third one is the useful part, and it's the one people skip. The night was open. I'd just extended someone by two nights. I removed a block this morning. I added a phone booking by hand and didn't check the date twice. Causes repeat because the same small action gets done the same way every time.

Read the notes together once a month, in one place, and look for the repeat rather than the incident. Two overlaps in a season with the same cause aren't bad luck. They're a process with a gap in it, and the gap is usually the handover between two systems or two people.

There's a second pattern worth watching: overlaps that arrive in pairs. A weekend where two happen is usually one cause firing twice, not two separate faults. A rate plan opened for dates that were already sold, or a block removed on the wrong unit. Fix the cause once and both go away.

One more habit worth having: check the night before you go to bed on any day you changed availability by hand. Most overlaps start with an edit, not with a sync.

FAQ

Should I cancel the duplicate booking?

Not while a guest is still travelling. A cancellation puts the night back on sale and removes the record of what went wrong. Block the night instead, house the guest, and settle the duplicate in the morning when you can see both bookings side by side.

Who pays for the hotel room?

That depends on your local rules, your agreement with the guest and the channel's terms, and no article can set the answer for you. What you control tonight is the order and the record. Both of those decide how the conversation goes next week.

How do I make sure it doesn't happen again?

You can't make it impossible, and anyone who promises that is selling something. You can make it rare and visible: close the night in the calendar as soon as it's sold, check after any manual edit, and read your causes together once a month.

Overbookings are cheap to fix in the right order and expensive in the wrong one. Guest, calendar, channel, record. At midnight, the calendar is the last thing you want to be fixing by hand. localsbnb.com keeps availability for every unit in one calendar, so a night you close stays closed while you deal with the person in front of you.

---

This article is general guidance for hosts and isn't legal, tax or insurance advice. What you owe a guest who can't be housed, what a channel requires you to do after an overlap and how a refund is treated differ by jurisdiction and by platform. Confirm the current rules with the competent authority and the current terms of each platform you use before you rely on any of this.