Codes are created in Hospitable and sent to our integration partners as soon as a reservation is accepted.

The code is visible in your conversation thread with the guest and can be added to any guest message by using the %smartlock_code% short code.

If the lock code hasn't been previously communicated to guests by using the %smartlock_code% short code, we will automatically communicate the lock code to your guest when it is scheduled to be active, including any configured buffers. Read more about guest code communication here.

The start and end time for an individual code can be changed in Hospitable by updating the check-in or check out time in the inbox conversation.

If we are unable to set a guest's code on the lock, we will automatically send a backup code to your guest. Once the guest checks out the code will then be deleted from the lock and replaced with a new one.

Users with Autohost Integration Only: If the Autohost verification setting is enabled in your smartlock settings, we will delay sending any code communications until the reservation has been verified.

By default, codes are created based on the guest's phone number. If the phone number is not present within 5 minutes after accepting the booking a random code will be used instead. You can adjust your settings to always be a random code for increased security.

By default, codes are scheduled to activate at check-in time and deactivate at check-out time, with automatic removal from the lock after deactivation.

You can add a buffer to the start and end times to be sure your codes are always ready for early arrivals or late departures. If check-in time is 3 pm and check-out is 11 am, and you have a 1-hour buffer set for both, the code would be active at 2 pm and expire at 12 noon.

You can view the guest code communication message that's automatically sent in your settings as well.

Users with Autohost Integration Only: You can enable Autohost verification to delay any messages that would be sent if the guest is not verified.

Codes become visible in the lock app and are sent to the lock 3 days before the code is scheduled to be active with any buffer times applied.

Codes are immediately accessible in the RemoteLock app, but still won't be sent to the lock until 3 days before the code is scheduled to be active with any buffer times applied.

Codes are sent to the lock and become visible in your lock app within 30 minutes before the code is scheduled to be active with any buffer times applied. This will not impact the timing of our code communications.

Codes are not allowed to start with "12" or include a "0". If your settings are configured to use the last digits of a guest's phone number for the code and use of the phone number is restricted due to this, we will use a randomly generated code.

Pending - the time and date that we have started creating the code. This is usually the same time that your reservation was received. At this point, we are still waiting on a confirmation from the integration partner. Your code will be in a grey box.

Created - the code has successfully been created on our system, ready to be sent to the lock at the given time. The code will be in a yellow box.

Visible on lock - the time and date that the code will be sent to the lock. At that point, you will see it in your companion app. The code will still be in a yellow box.

Active - the start time of the code. At this point, the code will be fully ready to use by your guests. The code will be displayed in a green box.

Lock Disconnected - If there are any connection issues with your lock, the lock name will be replaced with Lock Disconnected in red lettering. Check your lock's internet connection if you see this. You may have a flaky connection and need to move your router closer to your lock or hub.

Retry Code - If the code has failed to be created, the colored box will instead read Retry Code in red lettering. Click this to restart the code creation process.

+Add a smart lock - There is no lock matched with the property. Click this to be directed to the Apps page and sign in to the required integration.