Three-day pre-arrival message
Send this about three days before arrival, in the property's time zone, once the stay is still confirmed.
{Guest name}, you arrive at {Property name} on {Arrival date}. Check-in starts at {Check-in time}.
Parking: {Parking line}.
I will send the door steps on {Arrival date}, once the entry code or key is active for your stay. If your arrival time changes, reply in this thread so the door is ready when you are.
When to send
This is the bridge between “your stay is confirmed” and “here is the door.” Send it when {arrival_date} is about three days away and the reservation is still on the calendar. {checkin_time} is the same time as the reservation. {parking_line} is one or two sentences: which spot, which side of the building, what to avoid. It is not a full driving route. The directions message can carry landmarks if the route itself is confusing. This note only needs the car to have a legal place to stop.
{guest_name} gets the note in the booking thread, including anyone the platform has added to that thread. Write it so a traveling companion who did not book can follow it. Do not assume they read the confirmation from last month.
Skip this message for a same-day or next-day booking. Those guests need the door message, not a three-day preview of a door message. Sending both an hour apart duplicates {parking_line} and buries the code.
Timing tip
Schedule it for roughly 72 hours before {checkin_time}, in the listing’s time zone, not in yours if you live elsewhere. A message set for your morning can land in the middle of their night, or after they have already left for the airport.
If the code is stable and you have tested it, you can move the door steps earlier for a guest who asks. The default in this template is to wait until {arrival_date} because rotating codes are often wrong when they are sent at the three-day mark. Say that the door steps are coming, so the silence on the code is a plan and not a forgotten host.
Re-read {parking_line} the week of the stay if the city changes street rules for an event or a sweep. A line that was true in the confirmation month can be wrong on arrival week. Fix the sentence before this message goes.
Common mistakes
Repeating the confirmation word for word is the first one. They already know they are booked. If this note does not add {parking_line} or the promise of when the door steps arrive, delete it and send nothing.
The second is a code that is not live. Guests test codes in the rideshare on the way from the airport, even when you wrote that the code starts at {checkin_time}. A code in this message will be tried early. Leave it out until the day it works.
The third is a new chore. “Please start the dishwasher when you arrive” or “take shoes off, which I forgot to put on the listing” is a rule added after booking. {parking_line} should match the parking the listing already described. If the listing said “street parking” and you now need them in a numbered stall, update the way you describe it only if the stall was part of what they booked. Do not spring a paid garage on them here.
If the plans move
When they reply with a new arrival time, do not send this whole note again. Answer the time, and let the check-in message carry the door. If they ask for an early check-in in reply to this message, decide from the cleaner’s schedule before you answer. A maybe is harder to unwind than a no. The template does not promise an early door. Keep that promise out unless you have already agreed to a time.