Night Coverage Without a Night Shift

A guest at 2 a.m. is not a staffing problem before it is a routing problem. Three tiers beat one exhausted person.

Last updated: November 1, 2026

Most of what lands in a host's inbox after midnight is one of four things, and only one of them needs you. Sort those messages by type before you sort them by hour, and a night shift starts to look like an expensive answer to a question nobody asked.

Key Takeaways

• Four messages cause most night calls. Access, noise, a broken essential and a question about tomorrow. The rest can keep until seven.
• Tier the response, not the person. An answer that already exists, a morning human and one escalation line cover the whole night between them.
• Keep the escalation line to two or three cases. Write it as a sentence rather than a category, because categories invite an argument at three in the morning.
• The guest inbox covers one channel. Messages inside LOCALSBNB are Airbnb messages, so Booking.com, Agoda and Trip.com threads stay in their own apps and need their own night plan.
• A handover note beats a good memory. What came in, what you did, what's still open — written before you sleep, read by whoever wakes up next.

What actually arrives at night

Pull the timestamps off a month of guest messages. Almost every thread opened between eleven at night and six in the morning is a version of the same four asks. Someone can't get in. Someone can't sleep. Something that should work doesn't. Someone wants to know what happens tomorrow.

The mix shifts with the property, but the categories don't. A flat with a key safe collects access messages. A converted basement collects noise complaints from the flat above. An older building collects the third kind — the radiator that clanks, the shower that runs cold, the lock that needs a second turn.

None of those four needs a person who is awake all night. Three of them need an answer that exists, and one needs a decision you can make in advance. That's the whole problem, and it's a design problem, not a hiring one.

There's a boundary to fix before you design anything. The guest inbox in LOCALSBNB covers Airbnb. Booking.com, Agoda and Trip.com keep their own threads in their own dashboards, so a night plan that watches a single inbox has three blind spots by default. Whatever you build has to reach every app your guests actually use to message you, or the plan only covers the guests who happened to book through one channel.

Three tiers, not one person

Tier one isn't a person. It's the answer that's already written down: the door code and where the box is, the wifi network, the checkout hour, the trick with the boiler, the number for the noise, the bin day. Load all of it into the arrival message and the listing itself, so the guest who reads at midnight finds it without asking.

The test for tier one is simple. If a calm guest, reading on a phone in a dark hallway, could solve it in ninety seconds with the text you already sent, it belongs there. Most access messages fail this test not because the code was wrong but because it was buried in a paragraph four messages up.

Tier two is a person, but not at two in the morning. It's the first hour of the working day. It takes everything that needs judgment and can survive six hours of waiting: the guest who wants an extra night, the room that isn't the one in the photo, a question about a late checkout. Six hours is the point. A message that reads like an emergency at 2 a.m. often reads like an ordinary request at 8.

Tier three is the one number a guest can reach when the other two won't do. It should ring one person, not a queue, and that person should already know what they're allowed to decide.

The cheapest tier is the one where the answer already exists somewhere in the system. localsbnb.com keeps Airbnb, Booking.com, Agoda and Trip.com on one calendar. The question underneath most night messages then becomes one lookup instead of four: who's arriving tomorrow, is the flat empty, which room is due out. Anyone on the team can answer it at any hour, not just you. The read-only side of that is deliberately plain: today's arrivals, who's in house, which rooms are due out. The write steps are narrower still. Checking a guest in, extending a stay, moving someone to another room all run on overseas properties and wait for a person to confirm them. Nothing happens on its own while you sleep, which is why tier three needs a human rather than a setting.

The escalation line

Draw the line in daylight, when you're bored rather than frightened. Two questions decide whether a case crosses it.

The first: if this waits until eight, does something become unfixable? Water where water shouldn't be, no heat in a cold month, a lockout with a child on the wrong side of the door, anything that puts a person in danger. Those cross. A slow drain doesn't, however angry the message is.

The second: can the guest solve it with one sentence from you? If the answer is a sentence — the stopcock is under the sink, turn it clockwise — then it isn't an escalation, it's tier one arriving late. Send the sentence and go back to sleep.

Two or three cases is the right size for the list. A line that catches everything catches nothing, because the person on the other end learns to treat the phone as noise. Write each case as a sentence rather than a heading. "No heat between November and March, or water where water shouldn't be" survives the test; "urgent maintenance" doesn't, because at three in the morning every host thinks their problem is urgent maintenance.

Then decide, in the same sitting, who may spend what. Not the amount — the permission. Someone at the door at 3 a.m. needs to know whether they can call a locksmith or must wait until morning, and that answer can't be a phone call to you.

What to write down before you sleep

Five lines, every night, in the same place. The time. What arrived. What you did about it. What's still open. Who has it now.

That's it. It isn't a report and nobody reads it twice — except one person. Whoever picks the problem up at seven has none of your context, and no idea the guest has already been told twice that someone is coming.

The note does more work than it looks like. It stops the same guest being answered twice by two people. It turns a bad night into a pattern you can see after three weeks, which is the only way a recurring fault ever gets fixed rather than apologised for.

And it's the reason a small host can run a property without a rota. Not because the night is quiet, but because the night leaves a trace.

FAQ

Do I need someone awake all night?

No. You need an answer that exists, a person who arrives at a known hour, and a number that rings when something can't wait. Most hosts who hire night cover are paying for the first two, which are documents rather than shifts.

A guest messaged at 2 a.m. on Booking.com. Will I see it?

Not in the LOCALSBNB inbox. That inbox carries Airbnb messages, and Booking.com, Agoda and Trip.com each keep their own thread inside their own dashboard. Either check the other apps on a schedule you can actually keep, or tell guests at booking which channel to use for anything urgent.

Should I settle a refund at two in the morning?

No. Money decisions made at 3 a.m. tend to be more generous than the file supports and harder to explain later. Log the request, say when you'll respond, and decide in daylight when the booking record is in front of you.

Three tiers, one line, five lines of notes. localsbnb.com doesn't answer the door for you and doesn't pretend to. What it does is keep four channels and the night's facts in one place, so the person who does answer starts the morning already knowing what happened.

---

This article is general guidance for hosts and isn't legal, tax or insurance advice. Access arrangements, safety obligations and what a guest is entitled to differ by property, by platform and by jurisdiction. Confirm the current terms of each platform you use, and where safety is involved, check the requirement with the competent local authority before you rely on it.