Keypad check-in message
Send this on arrival day. A keypad code is not an app, and the message should not talk like it is one.
{Guest name}, {Property name} uses a keypad on {Door name}. The code is {Door code}.
{Confirm step} Wait for the click, then open the door. If nothing clicks, clear the pad and enter {Door code} again from the first digit.
When you leave, lock {Door name} from the outside with the keypad. Do not share {Door code} beyond the guests on this stay. If the pad will not take the code, reply in this thread.
When to send
Use this message for a keypad on the door itself: a deadbolt or handle the guest touches, with no phone app and no box. {confirm_step} is the part that changes by brand. Some pads want the code and then a lock or check button. Some want a start button before the digits. Write the sequence you just used with your own finger, in order, including whether a leading zero matters. {door_code} should be the digits as the pad expects them.
{door_name} picks the door when a gate and a unit both have pads. Guests will try the first pad they see. If the gate code and the unit code differ, this message should be about the unit, and the gate sequence should be its own sentence inside {confirm_step} or a line you add above it. Do not make them guess which code belongs where.
{guest_name} gets this on arrival day, after you have entered {door_code} and heard the bolt move. A code you programmed and did not test is a common source of “it blinks red.” Test, then send.
Timing tip
Morning of arrival is the right time if you change {door_code} between stays. If the code is stable for a season, you can send it the evening before, still after a test that week. Do not send a keypad code at booking. It will be forwarded, and you will not know who has it by {property_name}’s next guest.
If the pad beeps loudly, and they may arrive during quiet hours, say the beep is short and they should not knock. That belongs with the late-night message if the arrival is actually late. Keep the code in this note so there is one place to look.
Same-day turns: send the code only after the previous guest’s code is no longer the one on the pad, if your pad stores a single code. Overlapping codes are how a departed guest walks back in. Program first, test, then fill {door_code}.
Common mistakes
Describing a keypad as if it were a smart lock is the first mistake. There is no app to refresh, no Bluetooth, and often no time window. Do not tell them to “sync the lock” or to wait for a phone notification. {confirm_step} is fingers on a pad. If your device is actually a smart lock with a keypad fallback, use the smart lock message for the primary path and mention the pad only as the backup step on that message.
The second is a leading zero or a check button you forgot. Pads drop a zero, or they time out if {confirm_step} is slow. Write the pause if there is one: “press the digits, then the checkmark within three seconds.” Read it while standing at the door once. Your hands know the rhythm and the message might skip it.
The third is locking instructions that only work from inside. Many guests leave and pull the door shut, and the pad never locks. The template tells them to lock from the outside. If your model locks by holding a button, that hold belongs in the last paragraph, in words you add, because a door left unlocked is the incident you will hear about from the next guest or from a neighbor.
Share the code narrowly
The template says the code stays with the guests on this stay. Keep that line, especially for a code that does not expire on its own. If you cannot expire it, change it at checkout as part of turnover, and say nothing in this message that implies the code is permanent. A “save this for next time” line is an invitation to a return visit you have not booked, and it leaves a live code in their camera roll.