Airbnb Messages: The Complete Guide to Guest Communication
A single Airbnb reservation generates 10 to 15 messages, and roughly 40% of them land outside 9-to-5. Airbnb measures two of them publicly — your response rate and your response time — and both feed search ranking and Superhost status. This guide maps the six moments that decide the whole conversation, the tone that works, and how to cover nights and other languages.
Capitolo 01 / 10
01 — What Airbnb Actually Measures
Most hosts think of the inbox as customer service. Airbnb treats it as a ranking input. Three separate numbers come out of your messages, and they behave differently.
Response rate is the percentage of new inquiries and booking requests you replied to within 24 hours, measured over a rolling 30-day window. Only first contacts count — follow-up messages inside an existing thread do not move it. Superhost status requires 90% or above.
Response time is your median time to first reply, displayed publicly on your listing as a band: "within an hour", "within a few hours", "within a day". It is the number guests see before they message you, and it changes conversion on inquiries more than almost anything else on the page.
Communication rating is the star sub-score guests leave after checkout. It is not about speed at all — it is about whether the guest ever felt uncertain. A host who replies in four hours but answers completely often scores higher than one who replies in five minutes with "I'll check and get back to you."
| Metric | Window | What moves it | Visible to guests |
|---|---|---|---|
| Response rate | Rolling 30 days | First replies to new inquiries only | Yes, as a % |
| Response time | Rolling 30 days | Median time to first reply | Yes, as a band |
| Communication rating | Last 365 days of reviews | Completeness and clarity | Yes, in review breakdown |
Dato
The practical consequence: a host who ignores three inquiries in a month because they arrived at 2am can drop from 100% to 90% response rate and lose Superhost on a technicality, without a single bad review.
Capitolo 02 / 10
02 — The Six Moments That Carry the Whole Conversation
Guest communication feels chaotic because it arrives in random order. It is not actually random. Across a typical stay, message volume clusters into six moments, and each one has a different job.
| Moment | Timing | Job of the message | Cost of getting it wrong |
|---|---|---|---|
| Inquiry / booking | Within 1 hour | Confirm, reassure, set the channel | Lost booking, damaged response rate |
| Pre-arrival | 3–7 days before | Collect arrival details, pre-empt questions | Doorstep chaos on arrival day |
| Check-in day | Morning of arrival | Deliver access instructions | 4-star check-in score |
| Mid-stay | Day 2, or day 3 of a longer stay | Catch problems while they're fixable | Silent dissatisfaction, then a public review |
| Checkout | Evening before | Departure logistics, no surprises | Late checkouts, cleaning delays |
| Review | 12–24 hours after checkout | Ask, while the memory is warm | A review that never gets written |
The pattern to notice: four of the six are things you send, and you control the timing entirely. Only the inquiry and the mid-stay are genuinely reactive. This is why hosts who feel buried in messages are usually not overwhelmed by guests — they are overwhelmed by their own missing structure, which produces guest questions that a well-timed message would have prevented.
If you want the exact wording for each of these moments, the library of ready-to-use Airbnb message templates covers all six with copy-paste text. This guide is about the system those templates plug into: when to send, how fast, in which tone, and who answers when you can't.
Capitolo 03 / 10
03 — Booking and Pre-Arrival: Where Expectations Get Set
The inquiry reply
Speed matters more here than anywhere else in the guest journey, because you are competing with three other listings the guest messaged at the same time. Airbnb's own guidance is one hour; in practice, the first host to reply with a complete answer converts a disproportionate share of inquiries.
Three things belong in that first reply, in this order: a direct answer to what they actually asked, one specific detail that proves you read the message (their dates, the number of guests, the reason for the trip if they mentioned it), and a single next step. Nothing else. A wall of house rules at first contact reads as friction.
The booking confirmation
Once a booking is confirmed, the guest's anxiety shifts from "is this place real?" to "how do I get in?". Your confirmation message should answer the second question at a high level — check-in window, neighbourhood, how instructions will arrive and when — without dumping the door code six weeks early, where it will be buried under thirty messages by arrival day.
This is also the moment to move the conversation to the channel you actually monitor. Most guests are already on WhatsApp; asking once, politely, at booking, gets a yes from the large majority and means arrival-day messages get seen rather than sitting unread in an app the guest opened twice.
Pre-arrival, 3 to 7 days out
The pre-arrival message does two jobs at once: it collects what you need (estimated arrival time, transport, any accessibility needs) and it pre-empts the questions you already know are coming. Every host has a top five — parking, luggage drop, Wi-Fi, early check-in, nearest supermarket. Answering them before they are asked removes roughly a third of all inbound messages.
Tip
Warmth belongs here more than in any other message. The Airbnb welcome message is the one guests remember, and it costs nothing to make it sound like a person wrote it. One personalised line — a restaurant near the flat, a note about the weather that week — is enough.
Capitolo 04 / 10
04 — Check-In Day, Mid-Stay, Checkout
Check-in day
Send full access instructions on the morning of arrival, not the night before and definitely not a week earlier. Include the address in a copy-pasteable format, the door code or key process, a photo of the entrance, and one line about what to do if something goes wrong. The photo matters more than hosts expect: it removes the single most common arrival failure, which is a guest standing outside the wrong door.
If you use a keybox or smart lock, the instructions carry more weight because there is nobody there to correct a misunderstanding. Hosts running unattended self check-in should treat the arrival message as part of the lock, not as a courtesy note.
Mid-stay
The mid-stay check-in is the most skipped message in short-term rentals and the one with the highest return. A short note on day two — "everything working as it should?" — turns a silent problem into a fixable one. Guests who report a broken shower on day two and get it fixed leave 5-star reviews. Guests who suffer through it in silence leave 3-star reviews with a paragraph about the shower.
Keep it to one line, and make it easy to answer with "all good". On stays of two nights, skip it: the guest is already leaving.
Checkout
Send checkout logistics the evening before departure, not at 8am on the day. Guests plan their morning the night before. Include the checkout time, what you want done with keys and rubbish, and — this is the part hosts forget — explicitly say what you don't need. "No need to strip the beds or run the dishwasher" reads as generous and prevents the awkward half-cleaned handover.
Attenzione
Never bundle a late-checkout refusal into the same message as a review request. Two asks in one message, one of them a no, reliably costs you the review.
Capitolo 05 / 10
05 — The Review Message: The Last 3%
Roughly 70% of Airbnb stays end in a review, and the difference between hosts at 70% and hosts at 90% is almost always a single message sent at the right time.
Send it 12 to 24 hours after checkout. Earlier and the guest is still travelling; later and the trip has already been filed away mentally. Keep it short, thank them for something specific, and ask once. Do not explain how important reviews are to your business, do not mention star ratings, and do not hint at what you would like them to write — Airbnb's policy prohibits review manipulation, and guests find it off-putting regardless.
If the stay had a problem you fixed, name it in the review message. "Sorry again about the boiler on Tuesday — glad we got it sorted quickly" does more to shape the eventual review than silence, because it frames the incident as resolved rather than as an unaddressed grievance.
Hosts who want the full mechanics of review recovery — including how to handle a review that has already gone badly — will find more detail in the guide on negative Airbnb reviews.
Capitolo 06 / 10
06 — Tone: Warm, Short, Complete
There is a persistent myth that guests want a chatty host. They do not. Analysis of communication sub-scores consistently points the other way: guests reward completeness and clarity, and warmth only helps once those two are in place.
Three rules cover almost every case.
Answer the actual question first. Not context, not an apology for the delay, not a preamble. The answer, in the first line. Everything else can follow.
One message, one topic. A message containing check-in instructions, a parking note, and a request to confirm arrival time will get one of the three answered. Split them.
Say what you will do and when. "I'll check with the cleaner and confirm by 6pm" is a complete answer even though it resolves nothing. "Let me check" is not.
On formality: match the guest. A guest who writes "Hi! Super excited 😊" wants a different register than one who writes "Good afternoon, I would like to confirm the arrival procedure." Both want the same underlying thing — certainty — but mirroring their tone costs nothing and makes the exchange feel human. The Airbnb messaging best practices guide goes deeper on the tone framework and on response-time benchmarks by property type.
"The problem isn't answering messages. It's answering the same eight questions a hundred times a month, in three languages, at eleven at night."
— a recurring line from hosts managing eight or more listings
Capitolo 07 / 10
07 — Response Time and Ranking: The Actual Mechanics
Airbnb has never published its ranking weights, but the observable behaviour is consistent across markets.
Response time is a soft ranking signal, response rate is a hard threshold. Dropping from "within an hour" to "within a few hours" is a gradual visibility cost. Dropping below 90% response rate costs Superhost outright at the next quarterly assessment, and Superhost itself carries a ranking boost.
The 24-hour clock only runs on new inquiries. This is the detail that saves most hosts: a guest asking a question mid-stay at 3am does not damage your metrics if you answer at 8am. A new booking inquiry at 3am that you answer at 8am is fine too — you are inside the 24-hour window. What kills the metric is the inquiry you never see because it fell off the bottom of your notifications.
Median, not average. One reply after 20 hours does not wreck a month of sub-hour replies. Consistency beats heroics.
For hosts with one or two listings, hitting "within an hour" during waking hours and clearing the inbox once before bed is enough. The maths changes at scale: five listings generate 150-plus messages a week, and manual coverage of a sub-hour median across seven days becomes a job rather than a habit.
| Listings | Messages / week | Realistic manual median | Where it breaks |
|---|---|---|---|
| 1–2 | 25–35 | Under 1 hour | Holidays, illness |
| 3–5 | 70–150 | 1–3 hours | Weekends, evenings |
| 6–15 | 200–450 | 3–8 hours | Everything after 8pm |
| 15+ | 450+ | Not achievable solo | Continuously |
Capitolo 08 / 10
08 — Nights, Weekends and Other Languages
Two problems break manual messaging, and both are structural rather than a question of effort.
The out-of-hours problem
Roughly 40% of guest messages arrive outside standard working hours, and the ones that arrive at night are disproportionately urgent: a guest locked out, a code that will not work, a late flight. These are the messages where a two-hour delay becomes a 3-star review.
The realistic options are three. Scheduled messages cover the predictable moments but cannot answer anything — they are one-way broadcasts. A shared inbox with a partner or co-host splits the burden but doubles the coordination. Or you put a conversational layer in front of the inbox that answers the routine questions itself and escalates the rest.
The guide on automated Airbnb messages breaks down all three approaches with setup times and costs. The short version: scheduled messages solve the sending problem, not the answering problem, and 60–70% of guest messages are questions.
The language problem
Airbnb's inline translation is adequate for a booking inquiry and unreliable for anything operational. "Leave the keys in the box by the gate" survives translation; "the boiler needs to be reset by holding the red button for five seconds" often does not. Guests then act on a mistranslation, and you find out at checkout.
For international portfolios, the practical bar is native-quality replies in the guest's own language, not machine translation of your English. Verto handles guest conversations on WhatsApp in more than 25 languages, understands text, photos and voice notes, and resolves 85% of conversations on its own across more than 12,000 measured exchanges — escalating the rest to you with the full thread attached.
Dato
Photos and voice notes matter more than they sound. A guest who cannot describe a problem in English will photograph it. A guest driving to the property will send a voice note rather than type.
Capitolo 09 / 10
09 — Building the System, Not Collecting Templates
The hosts who never feel buried are not the ones with the biggest template library. They are the ones running three layers.
Layer 1 — the scheduled sequence. Six messages, one per moment, sent automatically on booking, check-in and checkout triggers. Native to Airbnb, free, and it covers the outbound half of the job. Setup takes an afternoon.
Layer 2 — saved replies. Ten to fifteen answers to the questions you get every week, ready to paste. This covers the reactive half during hours you are awake.
Layer 3 — a conversational layer. Something that reads an unpredictable question, answers it correctly using your property details and live booking data, and knows when to hand over. This is the only layer that covers nights, weekends and languages you do not speak.
Most hosts stop after layer one, get frustrated that "automation doesn't work", and go back to answering everything by hand. Layer one was never supposed to answer anything.
- Six scheduled messages configured on all listings
- Top ten guest questions written as saved replies
- Arrival instructions include a photo of the entrance
- Mid-stay check-in on every stay of three nights or more
- Review request scheduled 12–24 hours post-checkout
- A defined answer for the 11pm lockout
- A defined answer for a message in a language you do not read
Capitolo 10 / 10
Conclusion: Structure First, Tools Second
Airbnb messages look like a volume problem and are almost always a timing problem. Six well-placed messages remove more inbound questions than any template library, and the metrics Airbnb publishes — response rate, response time, communication score — respond to structure far more than to effort.
Start by writing down the six moments and what each one has to accomplish for your specific property. Then automate the outbound sequence. Only then look at what is left in the inbox: whatever remains is the part that genuinely needs an answer, and that is where a conversational layer earns its keep.
If nights and multilingual guests are the gap in your setup, see how Verto handles them on WhatsApp — from €24.90 per apartment per month, setup in 30 minutes, no lock-in and cancel anytime. Plans and pricing are public.
Keep going
See Verto at work
Want to see Verto on a real conversation?
Self-service setup in 30 minutes, no lock-in. Plugs into the channel manager you already use.