Late-night arrival message
Send this once you know they will arrive during quiet hours, or include it when the listing already allows a late door.
{Guest name}, you can arrive at {Property name} during {Arrival window}, which falls inside quiet hours ({Quiet hours}).
{Entry step} Keep voices low on the way in, and skip knocking. Neighbors are asleep, and a knock will not open the door.
The entry method still works through {Arrival window}. If you will be later than that, reply in this thread before you are on the step.
When to send
Send the late-night note when arrival and {quiet_hours} overlap. {quiet_hours} must be the hours already on the listing, not a stricter window you thought of today. {arrival_window} is the range you are actually prepared for, such as “10pm to 1am,” and it has to be a window your lock, your box, or your meet-up can support. {entry_step} is the short version of the door method: which door, whether the code from the check-in message is the one to use, and which light is safe to turn on.
Do not make this the only check-in message if the code is complicated. The smart lock, lockbox, or keypad note still carries the digits. This note carries the nighttime behavior. Repeat the code here only if you are not sending the other message, and then {entry_step} has to include the digits so they are not hunting.
{guest_name} should get this in the afternoon, once you know the arrival is late, not at midnight when they are already outside. If every stay is allowed to arrive late because the listing says self check-in at any hour after the published check-in time, you can send this with the door message whenever {arrival_window} is after quiet hours begin.
Timing tip
The trigger is information, not the clock. If the arrival-time reply says 11pm, send this within the hour so they can plan the rideshare drop-off. If you learn about the late door at 6pm, you still have time to extend a code that would have died at 9. Do that extension before you promise {arrival_window}.
A code that expires at the start of quiet hours is the failure mode. Read the lock settings against {arrival_window} before the message goes. If you cannot extend the code, do not send a message that implies the door will open. Tell them the last hour it works and what you can do instead, in a direct reply, even if that means they wait until morning somewhere else. A false window is worse than a tight one.
Skip the message when they arrive at 5pm. A late-night warning on a normal afternoon makes the home sound harsher than the listing.
Common mistakes
Asking them to call a phone number is the first one. A late guest will try, and a platform may hold the message, and you may be asleep anyway. {entry_step} should work with nobody awake. If a human is required, name the co-host inside the booking thread and the hours that person answers. Do not invent a 24-hour desk you do not have.
The second is a new noise rule. Whispering, no showers, no lights: if {quiet_hours} on the listing already covers the behavior, point at it. If you want a new limit, it does not belong in an arrival message after they have booked. The template asks for low voices and no knocking because knocking does not open a lock and it does wake people. That is operational, and it matches a quiet-hours rule they should already have seen.
The third is the wrong light. Telling them to flip a floodlight that shines into a bedroom next door creates the complaint you were trying to avoid. Name the fixture in {entry_step} after you have stood outside and seen where it points.
The building around them
If {property_name} is an apartment, {entry_step} should say whether a lobby door is propped, coded, or closed overnight. A unit code does not open a lobby that locks at 10. Walk it once at night if you can. Daylight directions miss the gate that auto-locks.
Tell them not to buzz other units. That sentence is worth adding in your edit if your panel has names on it. The template leaves it out so a house without a panel does not grow a nonsense line. Add it only where the panel exists.