The most predictable messages a short-term rental host receives arrive in a tight cluster: between 3 p.m. and 7 p.m. on check-in day. They are almost always one of the same four questions — where to park, how to get inside, the Wi-Fi password, or the door code — and they almost always come from guests who received the information at least once but either didn't retain it or couldn't find it when they needed it. This is not a guest problem. It is a sequencing problem. The right information, sent at the right moment, gets read. The same information sent too early, too vaguely, or buried in a single long confirmation email gets ignored.
Most check-in support volume is preventable. What follows is the message sequence that eliminates most of it — four touchpoints, each with a specific purpose, that together move a guest from confirmed booking to confident arrival without needing to contact the host at all.
Why timing matters more than content
A common host instinct is to send the most detailed instructions as early as possible, ideally in the booking confirmation, so the guest has everything. The logic is understandable. In practice, it produces the opposite of the intended effect. A guest who booked six weeks out and receives a 600-word check-in walkthrough on the day they hit "confirm" will read none of it. They have a trip to plan. The property feels abstract. The information has nowhere to land.
The timing problem runs the other direction too. Hosts who withhold all access information until check-in day — waiting to send the door code until the morning of arrival — create last-minute anxiety for guests who are already in transit and may have spotty cell reception. One delayed message during peak travel hours can generate two or three panicked follow-ups.
Survey data from guest communication platforms puts the practical preference clearly: roughly 59% of guests want detailed arrival information at least one week before their stay, with another 19% preferring it one to two days before. Almost no guest wants it six weeks out, and very few want it for the first time on check-in morning. The sweet spot is the five-to-seven day window before arrival — close enough that the stay feels real, far enough that any confusion can be resolved without urgency.
The four-message framework
The sequence below is not a rigid script. It is a structure. The content will vary by property and platform; the timing logic holds across all of them.
Message 1: Booking confirmation (immediately after booking)
This message does two things: it confirms the stay and begins setting expectations for what comes next. It should be short. Guests who have just completed a booking want reassurance, not information. Lead with a warm but plain confirmation — dates, property name, host name, and a line indicating that detailed check-in instructions will arrive closer to arrival. Ask only one question: approximate arrival time. Collecting this early gives the host or cleaner a target window and avoids a logistical scramble later.
Do not include the door code here. Do not attach a PDF. Do not link to a 20-step guide. The booking confirmation is not a check-in manual; it is a handshake.
Sample language: "Thanks for booking — we're looking forward to having you. Your reservation for [dates] at [property] is confirmed. I'll send full check-in details about a week before you arrive. One quick question: roughly what time do you expect to arrive? Knowing helps us make sure everything is ready."
Message 2: Pre-arrival details (five to seven days before check-in)
This is the most important message in the sequence. It should contain everything a guest needs to arrive without contacting the host: the door code, parking instructions, a link to any digital guidebook, the Wi-Fi network and password, the check-in time, and a brief orientation to the entry flow (which building, which door, any steps a first-time visitor might miss). Where the property has a complicated approach — a shared driveway, a gate code separate from the unit code, a parking structure with a specific floor — describe it in specific terms, not general reassurances.
Keep it scannable. A guest who reads this on a work break needs to find the door code in under ten seconds. Use short paragraphs or brief labeled sections. Avoid running all of this into a wall of prose. The message is functional, not decorative.
On Airbnb, this message can be scheduled automatically using the platform's native scheduled messages feature, which allows hosts to pre-write templates and trigger them at a fixed number of days before check-in. On Vrbo, the native scheduling is more limited — the platform sends a single "Welcome Guide" email on a fixed timeline, and hosts who want more granular control typically use a property management system or a messaging tool to send additional scheduled touchpoints. Hosts running direct bookings have full control over the sequence and can use any email service or messaging platform with scheduling features.
Message 3: Check-in day confirmation (morning of arrival)
This message serves a specific function: it reaches the guests who didn't read Message 2. Sent the morning of arrival — ideally between 8 a.m. and 10 a.m. in the guest's departure timezone — it should repeat the essentials in compressed form: the door code, where to park, the check-in time, and a direct line for anything unexpected. Three to five lines is enough. The goal is not to re-educate; it is to put the critical information one scroll away at the exact moment the guest needs it.
Hosts who add this message to their sequence consistently report fewer arrival-window messages. The mechanism is simple: most check-in support tickets come from guests who are already in transit and either cannot find the earlier message or never opened it. A short message with the access code in the first line, sent the morning of a same-day check-in, sits at the top of the inbox at the exact moment it becomes relevant.
Message 4: Day-two check-in (evening of arrival or next morning)
Most of a guest's logistical questions surface within the first twelve to eighteen hours: the TV remote works differently than expected, the coffee maker requires a specific setting, the outdoor shower has a trick to it. A brief check-in message sent the evening of arrival or the following morning addresses this window before a minor friction becomes a frustration.
This message works best when it is specific rather than open-ended. A general "let us know if you need anything" is easy to skip over. A message that names two or three things guests sometimes ask about — "the hot tub takes about thirty minutes to reheat after the cover comes off; if the temperature drops, that's normal" — feels like local knowledge rather than a form letter. It also gives the guest permission to ask about smaller things without feeling like they are bothering anyone, which is often what prevents a fixable annoyance from becoming a negative review comment.
Platform constraints worth knowing
Airbnb's messaging system has enforced a policy for several years that prohibits sharing external contact information — phone numbers, email addresses, website links — before a booking is confirmed. This means that even a well-designed automated sequence cannot direct a guest to a host's direct booking site or collect contact data pre-booking. Once a booking is confirmed, hosts have more latitude, but any attempt to direct a guest to a different payment platform violates Airbnb's off-platform policy and can result in account suspension. Structure your message templates so they work cleanly within these constraints rather than routing around them. For more on how platforms shape who owns the relationship after checkout, see what Airbnb won't tell you about owning the guest relationship.
On Vrbo, automated message links must be plaintext URLs since the platform does not support hyperlinked text in host messages. Guests must copy and paste links rather than tap them. If you include a digital guidebook link in the pre-arrival message, paste the full URL on its own line rather than embedding it in a phrase.
What this does for the review
The check-in experience is disproportionately weighted in guest reviews. A guest who arrives smoothly — who found the parking, opened the door on the first try, and got onto the Wi-Fi without a message — starts their stay in a particular mental state. The property looks better when they are not frazzled. Small imperfections that might have registered as complaints go unnoticed.
The reverse is equally true. A guest who spent forty-five minutes circling the block, called twice and got voicemail, and finally reached the host who realized they'd sent the wrong door code — that guest's review will mention the check-in. It will almost always mention the check-in, regardless of how the rest of the stay goes. The pre-arrival sequence is not just operational housekeeping. For most properties, it is the single highest-leverage point in the guest journey for protecting the star rating and the relationship that follows.
A host who runs this sequence consistently — automated, reliable, timed correctly — also creates the conditions for a repeatable direct-booking relationship. Guests who arrive smoothly, feel well-prepared, and reach the host easily if something goes wrong are the guests who remember the property by name. That is what makes a repeat booking plausible, and a platform commission avoidable, the next time they plan a trip to the same destination — which is why we treat check-in sequencing as upstream of both guest retention and the playbook in our complete guide to direct bookings.
