A Practical Guide to Airbnb Guest Messaging

Guest messaging is where most of the perceived quality of a stay is produced. Guests forgive a broken dishwasher; they do not forgive four hours of silence while standing outside a locked door. The working rule: automate facts, handle judgment personally, and make sure someone owns the inbox at every hour a guest could reasonably need you.

What you'll learn

• Which messages to automate and which never to
• A default message sequence that covers most stays
• Escalation rules that keep small problems small
• How to cover the clock without answering messages at 3 a.m.
• What belongs in a handoff note

Automate facts, not feelings

Safe to automate: booking confirmation, pre-arrival details, check-in instructions, mid-stay check-in on longer bookings, checkout reminder, post-stay thank you. These are logistics. They are the same for everyone and they are better when they arrive on time rather than when you remember.

Never automate: complaints, refund discussions, damage conversations, anything involving a safety issue, or the response to a guest who is clearly upset. A templated reply to a real problem reads as indifference and turns a fixable complaint into a public review.

The middle ground is saved responses used as a floor: the template supplies the first sentence and the accurate detail, and you edit the rest for the person in front of you.

A default sequence

Two rules for the whole sequence: never send instructions the guest already has to scroll to find, and put the access code in the morning-of message even if it is also in the pre-arrival one.

Write escalation rules and give them numbers

The point of escalation rules is that whoever is on the inbox does not have to guess. Write yours down, with thresholds:

• Handle without asking: questions answerable from the listing or house guide, minor requests, late-checkout when the calendar is open.
• Handle and notify the owner: small issues resolved on the spot, a vendor scheduled, a guest complaint that was fully resolved.
• Ask the owner first: any refund or credit above your threshold, any repair above your spend limit, any request to break a house rule, anything involving a third party entering the property.
• Escalate immediately, day or night: lockout, no heat or no A/C in extreme weather, water leak, gas smell, no hot water, safety concern, or a guest threatening a claim.

Amounts make this work. "Refunds under $50 without asking" is a rule; "use good judgment" is not.

Tone

Short sentences. Plain words. One acknowledgment, then the fix.

• Lead with what you will do, not with an apology paragraph.
• Give a specific time — "the plumber will be there between 2 and 4" beats "as soon as possible."
• Never argue in writing. Everything you type may end up quoted in a review or read by platform support.
• If you were wrong, say so once and move on.

Key takeaway: speed and specificity are the whole game. A fast, concrete, slightly imperfect answer outperforms a polished one that arrives two hours later.

Response-time coverage

Decide, explicitly, who is answering messages in each block of the day — including nights and weekends — and what qualifies as worth waking someone. Most owners land somewhere near:

• 8 a.m.–9 p.m.: answer everything, target under 30 minutes.
• 9 p.m.–8 a.m.: monitor for the escalation list only; everything else waits until morning.

Then make the coverage real. A guest locked out at 11 p.m. is the exact scenario a co-host is for, and it is the scenario where an unstaffed inbox costs a review.

Handoff notes

Whenever a stay gets complicated, leave a short note attached to the reservation so the next person to open the thread is not starting cold:

• What happened, and when
• What was promised to the guest, and by whom
• What is still outstanding
• Anything the owner approved

Three sentences is usually enough. Continuity is most of what guests mean when they say communication was good.

Two examples

Maintenance issue, in-stay

Thanks for flagging this — sorry about the A/C. I've reached our HVAC tech and he can be there between 2 and 4 today. I'll confirm the window as soon as he does. There's a fan in the hall closet if it helps in the meantime, and I'll follow up either way this afternoon.

Refund request above your threshold

Thanks for laying that out clearly — I understand why that was frustrating. I want to get you a proper answer rather than a quick one, so I'm confirming a couple of things with the owner and will come back to you today. In the meantime, here's what we've already fixed: [specifics].

Neither message promises money. Both give a time.

Tired of the inbox? We handle guest communication end to end while you keep approval over every refund and every dollar. Email go@vacohost.com.

FAQ

Q How fast should I respond to guests? A: Aim for under an hour during waking hours and under 30 minutes for anyone currently in the property. Pre-booking inquiries convert best when answered quickly, and in-stay problems get more expensive with every hour of silence.

Q Should I use an AI assistant to answer guests? A: For drafting logistics replies it can save time. Do not let it send unreviewed messages about refunds, damage, or safety — those need a human who knows what you have already promised.

Q What do I do about an angry guest threatening a bad review? A: Answer the substance, not the threat. Document what you offered and when, keep the tone neutral, and never trade a refund for a review — platform policy prohibits it and it invites repeat attempts.

Sources and further reading

• Airbnb Help Center: scheduled messages — how to set up automated message timing.
• Airbnb Help Center: response rate and response time — how the platform measures messaging performance.
• Airbnb Help Center: review policy — what is and is not allowed around reviews.