The guest communication guide for short-term rental hosts

The clock you are actually being measured against

Guest communication feels like a soft skill. On Airbnb it is a scored metric, and the numbers are published.

• Hosts are asked to respond to reservation requests, booking inquiries, and all other guest messages within 24 hours. Anything slower is recorded as a late response, which lowers your response rate and raises your response time.
• Airbnb states that response rate can affect a listing’s position in search results. Slow replies are not just a service problem, they are a distribution problem.
• Response rate is calculated from your first reply to each new message thread over the past 12 months, assessed quarterly. Response time is the average across all new messages in the past 30 days. Follow-up messages in an existing thread do not count, and you do not have to send the last message in a conversation.
• Superhost status requires replying to 90% of new messages, plus a 4.8 overall rating, a cancellation rate under 1%, and either 10 reservations or 3 reservations totaling at least 100 nights.

The five questions that generate most of your inbox

Across almost every property, the same handful of questions dominate. They are not interesting, which is exactly why they are worth engineering away.

1. Wi-Fi. The network name and password, and what to do when the router needs a restart.
2. Getting in. Where the entrance is, how the lock works, what happens if the code fails, and where to park.
3. Appliances. The coffee machine, the induction hob, the shower, the thermostat, the washer. The specific device, not a generic manual.
4. Times and rules. Check-in, checkout, quiet hours, trash day, whether the deposit covers the dog.
5. Locally, where do we go. Food that is open now, the nearest pharmacy, whether the beach is walkable.

Every one of these has a fixed, correct, property-specific answer. None of them requires judgement. If a guest is messaging you about any of them, the information existed and was not reachable.

Write answers once, at the property level

The common failure is storing answers in the wrong place. A paragraph pasted into eleven booking threads is not a record, it is eleven copies that will drift the moment the router is replaced.

Structure it per property, and write for a stranger holding a phone in a dark hallway:

• One fact per entry. “Wi-Fi” is a topic. “Network name is X, password is Y, router is in the hall cupboard, restart takes 90 seconds” is an entry.
• Include the failure case. Most guest messages are not about the happy path, they are about what happens when the code does not work.
• Name the actual device. “Turn on the coffee machine” is useless. “The black Nespresso on the left of the sink, lift the lever, drop the pod in” is not.
• Date anything seasonal. Pool closed November to March. Trash day changed in June. Undated seasonal facts are the most common source of a confidently wrong answer.

What to automate, and what to never hand off

There is a clean line here, and crossing it is how hosts end up with a horror story about a bot.

The test is simple. If being wrong costs the guest money, safety, or access to the property, a human decides.

Five rules that survive contact with real guests

1. Answer where they are standing. A guest at the door will not open a 40-page PDF. Anything needed at the threshold has to be one tap away.
2. Never guess in writing. “I think the code is” is worse than “let me check and come back in five minutes”. Wrong information in writing gets quoted back to you in a review.
3. Reply first, solve second. The response clock measures your first reply, not your resolution. An acknowledgement inside the window buys you time.
4. Fix the source, not the thread. Every question you answer twice is a missing entry. Answering it a third time is a choice.
5. Ask for the review when the goodwill exists. Immediately after you solved something is when a guest is most willing. Days later, they have forgotten.

A 30-minute audit you can run today

1. Pull your last 50 guest messages

   Any platform. Read them as a list rather than as conversations.

2. Tag each one: fact, request, problem, or judgement

   Most hosts find 60% or more are facts. That share is your automation ceiling, and it is usually much higher than expected.

3. Write every repeated fact into a per-property record

   One fact per entry, failure case included, seasonal items dated.

4. Make it reachable from the property, not from your phone

   A record only you can read does not reduce your inbox. It has to be reachable by the guest at the moment the question occurs to them.

Where Moche-AI fits

That last step is the one hosts stall on, and it is what we built. Moche-AI turns the per-property record into a Property Brain, gives each stay one link or QR code with no guest app or login, and answers from your approved material with the source attached. When your material does not support a confident answer, it escalates to you rather than guessing, which is the automation line in the table above enforced in software.

It is not a channel manager and it does not replace a pre-arrival messaging tool. It is the in-stay layer. See how it works for the mechanics, what your guests see for the guest side, and trust and safety for how guest data is handled.