Airbnb Pre-Check-In Messages: A Three-Message Cadence for Arrival Day

An Airbnb welcome message can mean a booking confirmation or a greeting when the guest arrives. Those messages have different jobs. The examples below are original templates to edit, not customer conversations or evidence of a measured conversion lift.

Same-day booking — combine, do not duplicate:

Hi [first name], thanks for booking [listing] for [dates]. Check-in is from [confirmed time]. Your current arrival instructions are here: [verified link]. What time do you expect to arrive? If anything is unclear, please reply here.

If readiness is still unconfirmed, state the actual update instead of promising early access. Review pending scheduled messages so another welcome does not follow immediately.

Arrival greeting — ask, do not assume:

Welcome, [first name]. Have you been able to get in and find what you need? Please reply here if anything is missing or not working.

For a longer stay, add only a relevant, agreed service question: “Would [agreed service time] still work for you?” Keep unresolved arrival problems ahead of routine follow-ups.

Most arrival confusion is not caused by hosts who forget to write. It is caused by hosts who write everything at once, three days early, into a message the guest skims once and then cannot find again.

A single long note has a predictable failure mode. The parking detail is read and forgotten, the address is buried in paragraph four, and the door code sits in the same thread for days. By the time the guest is standing at the building, the only thing they remember is that there was a message.

For advance bookings, splitting the information into short, single-purpose messages can make it easier to find. Each message should have one job and one useful moment. For same-day bookings or an active guest conversation, combine or skip notices the guest no longer needs.

The timing does the work. Each message covers a different kind of information, and mixing them is what makes a guest scroll past the one field they needed.

The arrival-time question in the logistics message is doing more work than it looks like it is. A guest who says 6 p.m. has given you something real to plan around, including whether the turnover has enough room, and a guest who never answers is a signal to check in again rather than assume.

The honest version of message automation is narrower than most software implies. It is very good at timing, repetition, and pulling the right context into a draft. It is not a source of truth about the physical property.

Use the middle column to compare the capabilities of your chosen scheduler or assistant; the table does not imply every product supports each job. A scheduled send is not proof the guest received or understood it, and a code in a message does not prove the guest got in.

If you already run a smart lock, a keypad, or Airbnb check-in instructions, keep running them. Morphic does not compete with the layer that creates and rotates a code, and it does not need to, because the two tools sit at different levels of the same arrival.

That split keeps each job with its owner. The lock generates codes, the listing stores stable facts, and the selected scheduling tool sends the timed message. An assistant can help with questions without replacing that schedule.

The one rule is that the code in the message has to come from somewhere real. If your lock rotates it per stay, paste the current code as a host-supplied fact before the access message goes, or send your lock app's own instructions and use the Airbnb thread for the address and the fallback. A messaging tool that invents a code it has no authority over is worse than a host sending it late.

Every message inside the platform is timestamped and tied to the reservation. That matters the moment a guest says they never received the address, because the record either exists in one place or it is spread across three apps you now have to reconcile.

Guests also get a push notification for an Airbnb message. An email with the door code can sit in a promotions folder until the guest is already at the door, and a code sent only by text is a code you cannot prove arrived.

If a guest genuinely prefers another channel, keep the option, mirror the important parts back into the thread, and never send the entry detail only off-platform.

Write these once and keep each short. Use supported reservation variables in Airbnb scheduled quick replies, then check the actual preview before saving.

1. Confirmation:

Hi [Guest name], thanks for booking [dates]. Your arrival guide is here: [link]. Message me any time with questions before your stay.

2. Logistics (24 to 72 hours out):

Hi [Guest name], a quick note before [day]. Parking is [detail]. The neighborhood has [one useful tip]. Roughly what time do you expect to arrive? It helps make sure everything is ready.

3. Access (at the confirmed release time, or a useful reminder afterward):

Hi [Guest name], here is everything for tomorrow. The address is [address]. Check-in opens at [time]. Entry is [method the host supplies]. If anything is unclear when you arrive, reply here and I will help straight away.

The access message is the one to keep plain. Guests want it fast and functional, and it is the last message that should carry a new fact they have to remember.

Leading indicators are whether timing used the actual booking, whether the arrival-time question got an answer, and whether verified access instructions were available at the confirmed release time without duplicate or contradictory reminders.

The lagging signal that matters is simple: how many arrival-day questions you answered this month compared with last month. Do not report a scheduled send as proof of a better review outcome, a rating change, or revenue. A sent message is a sent message, and the guest experience is the only thing that can confirm the rest.