Airbnb Pre-Arrival Message Template: What Hosts Should Send
An Airbnb pre-arrival message should arrive when the guest can actually use it. Its job is to make the final approach to the property easier: confirm arrival timing, point to the official check-in instructions, clarify parking or building access, mention any approved special arrangement, and tell the guest how to reach the host if something goes wrong.
This page is different from the Airbnb Pre-Arrival Checklist. The checklist is the host’s internal readiness process. The message is the guest-facing communication sent after the property details have been verified.
Quick answer: what belongs in a pre-arrival message?
- Guest name
- Check-in date and time
- Where to find official check-in instructions
- Parking or building-access note
- Important reservation-specific arrangement
- Host/co-host support path
- Brief reminder to review the Arrival guide
1. Send the message after the property facts are confirmed
Do not tell the guest the property is ready before turnover, maintenance, access, and parking have been checked. Complete the internal pre-arrival review first. This prevents the host from sending a polished message while a cleaner, technician, or access problem is still unresolved.
2. Time the message around usefulness, not habit
Airbnb’s scheduled quick reply examples include a check-in reminder a couple of days before the trip. Airbnb also says guests usually receive detailed check-in information about 48 hours before arrival. A host can therefore use the pre-arrival message to reinforce where the official details are, without duplicating every line.
3. Lead with check-in time and action
The guest should immediately know when arrival begins and what they need to do next. If the property uses self check-in, tell the guest where to find the access instructions. If there is an in-person handoff, confirm the meeting plan. Avoid burying the arrival action under welcome text.
4. Include parking only if it helps the arrival
Parking information is useful when it affects the route, gate, assigned space, permit, garage, or street restrictions. Keep it concise and point to the Arrival guide for full detail. If parking changed recently, verify the message and photos before sending.
5. Do not paste a permanent access code into a reusable template
Use guest-specific or dynamic access information when supported. For smart locks, keep the code lifecycle tied to the reservation. For manual systems, share the minimum credential needed at the appropriate time. Backup entry should remain separate from normal pre-arrival communication unless it is actually required.
6. Mention Wi-Fi only when it adds value before arrival
Airbnb’s scheduled-message example includes Wi-Fi information, but hosts do not have to put every detail into the pre-arrival note. If guests commonly need connectivity immediately for a smart building or work stay, include it. Otherwise, the welcome book or Arrival guide may be a cleaner source.
7. Reflect approved exceptions
Early check-in, late arrival, accessibility arrangement, pet approval, parking exception, or special building access should be reflected in the message if it changes the normal process. Do not send a default scheduled reply that contradicts an approved reservation-specific arrangement.
8. Use Airbnb dynamic details only after testing them
Scheduled quick replies can insert guest, reservation, and listing details. Airbnb notes that missing source information can make a detail appear unavailable. Preview the message, especially after changing check-in time, directions, Wi-Fi, or listing information.
9. Handle last-minute bookings intentionally
Airbnb says messages scheduled before check-in may be skipped for last-minute bookings unless the host enables the option to send them anyway. A same-day guest may receive several scheduled messages at once if the system is not configured thoughtfully. Combine essential information and suppress low-value duplicates.
10. Keep the support path visible
End with one clear way to get help if arrival does not go as expected. Airbnb Messages should remain the primary record. If an urgent access issue requires a phone call after confirmation, summarize the resolution in the reservation thread when practical.
11. Avoid re-sending the entire house manual
The pre-arrival message is not the welcome book. Link the guest to the current information they need. Long messages make critical details harder to find while the guest is traveling.
12. Review the message after any operational change
A new lock, different parking space, new building entrance, revised check-in time, co-host change, or new Wi-Fi system can make the template wrong. Assign a review date and update the source property records first.
A practical pre-arrival template structure
- Welcome the guest by name.
- Confirm check-in date and time.
- Point to official check-in instructions.
- Give the essential parking/building note.
- Reflect any approved exception.
- Give the support contact path.
What should not be in the pre-arrival message?
- Permanent master access credentials
- Unnecessary personal data requests
- Surprise rules not disclosed in the listing
- Old screenshots of a previous lock or parking layout
- Long local recommendation lists
- Internal cleaner or vendor instructions
How this fits into the PropertyBinder system
The Property Management Binder keeps the property facts behind pre-arrival communication organized: parking, access, contacts, Wi-Fi, house rules, emergency information, and maintenance status. The host can update one source record, then refresh the guest-facing message when something changes.
FAQ
When should I send the Airbnb pre-arrival message?
Airbnb provides scheduled-message examples a couple of days before check-in, while detailed check-in instructions are generally available about 48 hours before arrival. Choose timing that matches the property and reservation.
Should I include the full check-in instructions?
Usually it is better to point to the official Arrival guide and highlight only the most important action or exception.
Can I automate the message?
Yes. Scheduled quick replies can automate predictable communication, but hosts should review last-minute bookings and reservation-specific exceptions.
Should Wi-Fi be included?
Include it if it helps the arrival experience. Otherwise, keep it in the welcome book or Arrival guide.
Build the message around the guest’s next physical step
A good pre-arrival message should help the guest move from travel to the correct parking area, gate, building, or entrance. Test the message by imagining the guest reading it on a phone with luggage in hand. If the first useful instruction appears halfway down the message, rewrite it. Arrival information should be chronological: where to go, where to park, how to find the entrance, where the official access instructions live, and who to contact if something does not match.
Use an exception block for high-risk arrivals
Add a short internal note for late-night arrivals, first stays after a lock change, first booking after renovation, severe-weather arrivals, or properties with building staff or gate restrictions. These reservations may need a manual review even when the standard message is automated. The host can then verify the backup entry plan, confirm after-hours support, and decide whether the scheduled message needs to be edited for that stay.
Keep a “last verified” date
Record when parking, access, Wi-Fi, support contacts, and arrival photos were last checked. A pre-arrival message can look polished while still being wrong because one small property detail changed. A review date makes stale information easier to spot before the next guest receives it.
Keep a backup contact visible to the hosting team.
Related PropertyBinder resource: Airbnb Guest Message Timeline