You're watching TV, or asleep, and the phone buzzes. "Hi so sorry to bother you, how do we turn on the heat?" It's 10:47pm. You answer because you're a decent host, you fall back asleep eventually, and the next day you forget it happened.
That's the mistake. Not answering late — that's unavoidable sometimes. The mistake is treating the message as a one-off interruption instead of what it actually is: a note, written by your guest in real time, telling you exactly where your documentation ran out.
The message is never really about the thermostat
Nobody messages a host at 10:47pm because they're curious about heating systems. They message because they're cold, right now, and the thing they tried didn't work. The question "how do we turn on the heat" is really saying: I looked for this information, I didn't find it, or I found it and it was wrong, and now I'm uncomfortable enough to bother a stranger at night.
That's useful data. It tells you three things at once: the gap exists, it's bad enough that a guest would rather text you than keep guessing, and it's bad enough to surface after dark, when most people are more reluctant to reach out, not less. If someone's willing to message at 10:47pm, the problem was real during the day too — they just muddled through until it got cold enough, or dark enough, or frustrating enough to stop ignoring it.
Sort the messages into what they actually reveal
Not every late text points to the same kind of hole. A few patterns show up again and again if you keep track:
"We can't find X." This is a documentation gap, plain and simple. The item exists, the guest knows roughly what they're looking for, but nothing told them where it was. Extra blankets, the spare key, the circuit breaker — these generate near-identical messages across totally different properties because every host assumes the location is obvious once you're standing in the room. It isn't. You've been in that kitchen fifty times. They've been in it for three hours.
"X isn't working." Sometimes this is a real maintenance issue. But often it's an instructions issue wearing a maintenance costume. The guest who messages "the hot water isn't working" at 11pm might be dealing with a water heater that needs five minutes to warm up, a mixer tap that needs to be pushed rather than turned, or a shower that requires the bathroom door to be shut for the pressure to build. The equipment is fine. Nobody told them how it behaves.
"Is it okay if we...?" These are the permission-seekers — can we use the fire pit after 9, can we park a second car overnight, can we check out a little late. These usually mean your house rules covered the big, obvious restrictions but skipped the smaller judgment calls that only come up in practice. You wrote rules for the situations you worried about. Guests are asking about the situations they're actually in.
Anything about the neighborhood. "Is anywhere still open for food near here?" at 10:30pm means your local recommendations section either doesn't exist or doesn't account for what people need once the day is basically over. A list of nice brunch spots doesn't help someone standing in your kitchen at 11, hungry, with no car.
Keep the log, even if it's three words
You don't need a system for this. A running note in your phone — "heating: couldn't find switch, 10:47pm, unit 2" — is enough. Do that for a month and patterns show up fast. If three different stays in the same place all generate a question about the washing machine, that's not three unlucky guests. That's the washing machine.
The timestamp matters too. A question that always arrives around midnight is different from one that always arrives at 8am. Midnight questions tend to be about comfort and access — heat, locks, how to get back in if you forgot the code. Morning questions tend to be about departure and logistics — checkout time, where to leave keys, whether the dishwasher needs to be run. Match the fix to the moment: comfort information needs to be visible from the moment someone unlocks the door, not buried on page six of a guidebook they skimmed once during check-in.
The fix is rarely a longer guidebook
The instinct, once you notice a gap, is to add more text. Resist that a little. The guest who messages at 10:47pm didn't fail to read enough — they failed to find the one sentence they needed, fast, while standing in a cold room holding a phone. A fifteen-page guidebook with the heating instructions on page nine doesn't solve the problem that created the message in the first place.
What solves it is putting the answer where the question happens. If people keep asking about the thermostat, a small card taped near the thermostat itself beats another paragraph in a document nobody reopens after arrival. If it's a digital guidebook, it means the search inside it needs to surface "heat" or "hot water" immediately rather than requiring someone to know it's filed under "Appliances" or "House Systems." We built the Q&A feature in TouchGuides because of exactly this pattern — guests type what they're actually wondering, in their own words, at 11pm, and get an answer without having to guess which section a host filed it under.
Reply to the late message, then actually act on it
The late-night reply matters on its own — nobody wants a guest sitting in the cold for forty-five minutes waiting for the host to wake up and check their phone. But it's also, every time, a sample of one specific thing in your listing that isn't quite finished. Answer the guest kindly, then the next morning, fix the actual gap: tape the instruction to the thermostat, add the line to the welcome sheet, put the washer cycle on a sticky note inside the lid. Do that consistently and the messages don't stop entirely — new guests always find new edges — but the same question stops arriving for the third, fourth, and fifth time. That's the part worth paying attention to: not that you got a message, but that you got the same message twice.