A No-Show With a Deposit: Reminders Without Automating Judgement

The calendar says no-show. The guest says the flight was cancelled. Deciding what happens to a deposit belongs to a person who has read both, which is why reminders should stop short of it.

Last updated: October 26, 2026

At eleven at night the calendar still says the guest is arriving. No message, no call. Both things can be true at once: nobody checked in, and nothing about that night is settled. A reminder can go out on its own. The decision that follows shouldn't.

Key Takeaways

• A status isn't a verdict. No-show is what the record says. Why is what the thread says, and the thread is a person's job.
• Three reminders, none of them an accusation. Before arrival, an hour after check-in time, and the next morning.
• The reminder's job is to produce a reply. Not a charge, and not a released booking.
• Three decisions stay with a person. Whether the reason holds, whether to hold the room, and what happens to the deposit.
• Write the outcome while the thread is open. The next case will look like this one, and you'll want the sentence you used last time.

What the record can and can't tell you

The record is good at facts. The dates that were booked, the channel they came through, the arrival time the guest typed in, every message sent and received, and whether the booking is still live. It's a clean timeline of what happened on your side.

It's bad at reasons. It can't tell you whether the guest is on a plane, in a hospital, at the wrong address, or sitting at home having changed their mind. All four look identical in the reservation list, and three of them aren't the guest's fault.

Three states get confused on arrival night, and only one of them is a no-show. A late arrival is a guest who is coming and hasn't messaged. A wrong-date booking is a guest who booked next month by mistake, which is a calendar error and not a deposit conversation at all. A no-show is somebody who isn't coming and hasn't said so. Before you act, work out which of the three you're looking at, because the handling is different for each.

One more thing the record can't tell you: silence isn't refusal. Most guests who go quiet on arrival night had a plan that fell apart, and a fair number of them are embarrassed about it. The reminder exists to give them a way back into the conversation.

The three reminders worth sending

The first goes out a few hours before arrival, and it asks practical questions rather than confirming anything. What time are you expecting to get in? Are you coming by car or by train? Is there anything I should know about the arrival? It's the message that catches a delayed flight while there's still time to hold the room.

The second goes an hour after check-in time, and it's one line. I've kept the room for you. Are you still coming tonight? No deadline, no consequence, no mention of the deposit. This is the message that gets answered at eleven at night, because it's the only one that doesn't sound like the start of an argument.

The third goes the next morning, and it states three things: the fact, the options, and the deadline you'll act on. The room stayed empty last night. I can hold it until six tonight at the same rate, or release it and leave the deposit question for a conversation. Tell me which you'd prefer.

None of the three is automated in the sense that matters. A template saves you the typing, and a saved reply is worth having at midnight. But somebody still reads the thread before pressing send, because the difference between the second and third message is judgement, not wording.

localsbnb.com keeps Airbnb guest messages in one inbox, so all three reminders and the guest's answers sit side by side instead of across two phones. A deposit conversation conducted from memory, at midnight, is where hosts say things they have to walk back.

Where a person has to decide

Three decisions sit after the reminders, and none of them should be made by a template.

The first is whether the reason holds. A forwarded cancellation notice, a hospital document, a one-line apology that says plans changed. You aren't a court and you don't need to be. You're deciding whether this is a person you want to keep a relationship with, and whether the deposit is the right instrument for the message you want to send.

The second is whether to hold the room. Holding costs you the night if nobody comes. Releasing costs you the booking if they're two hours away. There's no rule that fits both cases, which is exactly why the decision belongs to whoever can see the whole thread and the calendar at the same time.

The third is what happens to the deposit, and it splits in two. A deposit the channel holds follows the channel's process. A deposit you hold yourself follows your own terms and whatever your local rules require. Either way, one person reads, decides, and can explain the decision in two sentences afterwards.

Two habits make the third decision easier. Decide in writing, in one message, rather than across three calls. And decide what you'd do if the same thing had happened to you as a guest, not because that's a rule, but because it's the version you'll be able to explain in six weeks without flinching.

That's the line worth drawing clearly. Nothing in this workflow charges a card by itself, and nothing releases or cancels the booking. Both are acts with consequences, and an act with consequences needs a name attached. If a tool offers to settle the case for you, ask it to show you the thread it read. A settlement you can't trace back to a message isn't a decision.

Writing the outcome down

Before the thread goes cold, write five things in one line. The date. What the record said. What the guest said. What you decided. And the sentence you'd use if they asked you to explain it again.

That last one is the part that pays for itself. A deposit decision you can't explain in two sentences is a decision that comes back later, sometimes as a review, sometimes as a chargeback, sometimes as a message six weeks on asking why. If you can say it plainly on the day, you'll say it plainly in six weeks.

Then read the lines together once a season. No-shows cluster: the same channel, the same lead time, the same weekday, the same kind of trip. A run of them in one month usually says something about your minimum stay or your same-day settings rather than about the guests.

And keep the record where the next person can find it. If somebody else answers the phone next month, the line tells them what happened and how it was settled, which is the difference between a policy and a habit.

FAQ

Should I hold the room for a guest who hasn't shown up?

Hold if the night is unlikely to sell anyway and the guest is still answering. Release if the night is worth selling and the thread has gone quiet. The honest test is what you'd do with that room tonight if this booking didn't exist.

Can a reminder message settle the deposit question?

No. A message produces information, and the deposit question needs a decision made by somebody who has read the answers. Keeping the two apart is what stops a late-night message from becoming a position you have to defend later.

What if the guest replies after I've released the night?

Then you have a released night and a guest who wants it. Check what's actually available, quote the current rate rather than the old one, and say plainly what changed. Most guests accept that answer when it's given in one clear message.

A no-show is a small event with a long tail, and the tail is almost always the deposit. Send the three messages, keep the thread in one place, and let a person make the call with the whole conversation in front of them. For Airbnb bookings, localsbnb.com keeps the guest conversation and the booking it belongs to on one screen, so the decision is made from the thread rather than from memory.

---

This article is general guidance for hosts and isn't legal, tax or insurance advice. Whether a deposit may be kept, what has to be shown before it is, and how a cancelled stay is treated for tax 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 a deposit.