Guest Messages That Arrive Out of Hours: A Triage Order

Not every message that arrives at midnight needs an answer at midnight. A triage order keeps the two that do from sitting behind the ten that do not.

Last updated: October 2, 2026

Most messages that land at midnight can wait for morning. A few can't. The whole point of a triage order is to separate the two, so you're not scrolling past ten routine notes to reach the one about a locked door. Here's how to sort them before you answer any.

Key Takeaways

• Sort before you reply. The tier decides the response, not the order the messages arrived in.
• Access and safety skip the queue. A guest who can't get in isn't the same as a guest with a question.
• Holding replies buy the morning. One short line, sent once, keeps a message alive till daylight.
• State your hours once. A named window earns more patience than a silent delay.
• Only one channel feeds the inbox. The message view connects to Airbnb, so check the others directly.

What actually breaks when a message waits

Most messages carry no clock. A request for a restaurant tip, a question about whether coffee is provided, a happy note saying the stay's going well — none of those get worse while you sleep. Answering them at nine in the morning loses nothing.

A few do carry a clock. A guest who can't open the door. A guest with no hot water in winter. A same-night arrival whose time just changed. Anything touching safety. These get worse by the hour, and they get worse faster than you'd expect, because the guest is standing in the situation while you're asleep.

The failure mode isn't slow replies. It's treating every message as one pile. Read that pile top to bottom and the locked door gets answered after the restaurant question, by which point the guest has been outside for an hour.

There's a second thing worth naming. The messages you receive don't all arrive in the same place. Your inbox connects to Airbnb, so those conversations land in one view. Messages that come through other channels don't appear there. An empty inbox then reads as "nothing happened" when it actually means "nothing was routed here." Anyone running more than one channel has to check the rest directly, and that's a habit, not a fault.

So the triage order starts with an honest map: which messages reach the one place you watch, and which ones you have to go and find.

The pile itself is worth understanding too, because it grows in a predictable way. Nothing arrives for hours, then three messages land between eleven and midnight, and they look identical on a lock screen. That's not a sign of a busy night. It's what happens when guests finish their day at the same time, usually on a phone, usually with a small question they'd have asked in person if you were standing there. The size of the pile tells you about the hour, not about the urgency.

Three tiers, sorted by what they cost if they wait

The tiers are about cost, not urgency in the abstract. Ask what gets worse if this sits for eight hours, and you have your answer.

Tier one — act now. Access and safety. A guest who can't get in, a lock that won't read a code, no heat or no water, anything that puts a person or the property at risk. This tier doesn't wait for your hours.

Tier two — answer in the morning. Check-in details for a later day, questions about the unit, a change request for a future date, a complaint about something that can hold. Real, but not on a clock.

Tier three — answer when you're next working. Recommendations, general enquiries, notes that need no reply at all. These are the messages that make the pile look bigger than it is.

Sort by the guest's situation, not by tone or length. An angry message about the pillows is still tier two. A calm message saying "I'm stuck outside" is still tier one. Length lies too: the shortest message is often the one that matters.

One more rule belongs here. When a message asks for something that turns into an action on the stay — a check-in, a check-out, an extension, a room move — the action waits for your confirmation before it runs. Nothing changes on the guest's word alone, and nothing changes on the system's either.

Writing a holding reply that buys you the morning

A holding reply is one line, sent once, with a time inside it. It doesn't answer the message. It buys the hours you need to answer it properly.

For anything in tier two or three, the shape is simple: acknowledge, promise a time, and keep the promise. "Thanks for this — I'll come back to you in the morning" does the job. So does saying you'll confirm a detail after you've checked it. What you avoid is a reply that sounds finished when it isn't.

Two rules keep the holding reply honest. The first is not to promise a time you can't hold. A holding reply that says "first thing" and then arrives at noon teaches the guest to message you three more times. The second is to send it once. Repeated holding replies read as noise, and noise is what makes a guest escalate a tier-two message into a phone call.

For tier one, a holding reply isn't the answer. The answer is the call, the code reset, or the visit. Part of triage is knowing when the message stops being a message.

One thing the tooling won't do is reply for you. Whatever you send is sent by you, and that's deliberate — a guest can tell the difference between a person and a template, and out-of-hours is exactly when the difference shows.

Setting the hours you answer, and saying so

A stated window changes what guests expect. Say it once, clearly, in the places they'll see it before they need it: in the listing, and in the message that goes out before arrival.

The window doesn't have to be generous. It has to be real. Guests respect "I answer between eight and ten in the evening" far more than silence, because silence reads as not caring while a window reads as a plan. When someone knows your hours, a midnight message stops feeling ignored when it's answered at eight.

The window never covers tier one, and it's worth saying that out loud. Access and safety break through it. Guests who know that will use it properly instead of testing it with routine questions.

If you've told guests the hours, hold them on your side too. Sending a reply at three in the morning once is fine; doing it every week quietly cancels the window you set, because the guest learns the real hours by watching your behaviour.

A window also gives you something to point at later. When a guest complains that a reply felt slow, the answer isn't an argument about how late it was; it's the stated hours and the timestamp of your reply inside them. That's a calmer conversation for both sides.

This is also where the two sides of the tool meet. Conversations from Airbnb arrive in one inbox, which is the pile you're triaging. When a message turns into a change to the stay — a check-in, a check-out, an extension or a room move — those actions wait for you to confirm them, and they apply to overseas properties, with China properties staying read-only. localsbnb.com keeps that inbox in one place and puts the guest and the dates in front of you before anything runs.

FAQ

Should I answer every message the moment it arrives?

No. Most messages lose nothing by waiting until morning. Answering everything instantly isn't service; it's a habit that hides the two messages that genuinely can't wait.

What counts as urgent enough to break my stated hours?

Access and safety. A guest who can't get in, no heat or no water, a same-night arrival in trouble, anything that risks a person or the property. Those three break the window; nothing else does.

Do messages from every channel arrive in one inbox?

No. The inbox connects to Airbnb, so those conversations land in one place. Messages from your other channels don't appear there, so check those directly rather than reading an empty inbox as a quiet night.

Triage isn't about working later. It's about deciding once which messages carry a clock, so the decision doesn't get made half asleep at midnight. localsbnb.com keeps Airbnb conversations in a single inbox and holds every stay change for your confirmation, which leaves you free to answer the right message first.

---

This article is general guidance for hosts rather than advice on any platform's messaging rules. Response expectations, messaging features and channel coverage differ between platforms and change over time; check the current terms of each platform you sell on.