Skip to main content

Preventing unnecessary smart lock backup code messages

  • March 11, 2026
  • 7 replies
  • 283 views
Kristijan Laco
Hospitable Team Member
Forum|alt.badge.img+3

If you use smart locks with Hospitable, we've rolled out a small improvement to make sure guests consistently receive the correct door code.

In December 2025, we introduced more control over backup code messages and how they're sent to guests. You can read the original announcement here:

As part of that change, Hospitable checks whether the main door code is already being shared in your automated messages. If the system doesn't detect %smartlock_code% in the message template, it assumes the code isn't being communicated and may trigger the backup code message instead.

We found that some check-in messages were using phone-based placeholders like %guest_phone% or %guest_phone_last4% to communicate the door code. This historically worked for hosts whose locks were configured to use the last digits of a guest's phone number.

However, because those placeholders aren't recognized as the smart lock code itself, the system could still trigger the backup code message, which sometimes confused guests.

To prevent this, we ran an automated update for affected accounts.

 

What has changed

For hosts with connected smart locks, we updated guest-facing check-in messages that referenced phone-based codes and replaced them with the correct placeholder:

%smartlock_code%

Your message wording should remain the same. We only corrected the placeholder used for the door code.

 

Why it matters

This change helps ensure:

  • Guests consistently receive the correct smart lock code
  • Backup code messages trigger far less often
  • Check-in instructions remain clear and reliable

The goal is for smart lock access to feel seamless for both hosts and guests.

 

Who this affects

This update only applied to hosts who:

  • Have at least one connected smart lock
  • Have backup code communication enabled
  • Were not already using %smartlock_code% in their guest-facing message rules

If you were already using %smartlock_code%, nothing changed.

 

What you should do

No action is required. If you'd like, you can review/edit your check-in message anytime and confirm it includes %smartlock_code%.

--

If anything looks unusual in your messaging rules, reach out via in-app chat or at support@hospitable.com and our team will be happy to help.

7 replies

Forum|alt.badge.img+1
  • New Participant
  • March 13, 2026

Does this mean I can turn on the backup message again in case of real backup requirement and it won't be sent with absolutely every guest? As it had been doing for the past few weeks. Forcing me to turn off the backup message. 


32feed
New Participant
  • New Participant
  • March 13, 2026

Do you still have to be at the pro level membership with hospitable to have connected auto locks?


Port O Connor or Bust
New Participant

Does this mean I can turn on the backup message again in case of real backup requirement and it won't be sent with absolutely every guest? As it had been doing for the past few weeks. Forcing me to turn off the backup message. 

yes. turn it back on and make sure you send the message with the code early enough with check in instructions and %smartlock% in the check in instructions.


anthonyrallo
Top Contributor
Forum|alt.badge.img+2
  • Top Contributor
  • March 15, 2026

Do you still have to be at the pro level membership with hospitable to have connected auto locks?

@32feed I can confirm you do not. I’m on a legacy plan myself.  Smart lock functionality was initially the sole reason we came to Hospitable over two years ago. 
 


Homelike.ca
Known Participant
Forum|alt.badge.img+1
  • Known Participant
  • March 15, 2026

Yes, please; my locks have, like, 10 backup codes from hospitable. 


Kristijan Laco
Hospitable Team Member
Forum|alt.badge.img+3
  • Author
  • Hospitable Team Member
  • March 16, 2026

Do you still have to be at the pro level membership with hospitable to have connected auto locks?

Plans that currently support smart devices are Legacy (as a paid add-on), Professional (2 devices included per active property) and Mogul (4 devices included per active property). That said, in most cases it’s usually cheaper for users to use Professional or Mogul plans since those come with a fixed number of included devices (that doesn’t necessarily needs to be the case here, we do show in app if it’s cheaper for you to switch from Legacy => Professional for instance).


Christina Gwyneth Hamill
New Participant
Forum|alt.badge.img

Does this mean I can turn on the backup message again in case of real backup requirement and it won't be sent with absolutely every guest? As it had been doing for the past few weeks. Forcing me to turn off the backup message. 

If you use smart locks with Hospitable, we've rolled out a small improvement to make sure guests consistently receive the correct door code.

In December 2025, we introduced more control over backup code messages and how they're sent to guests. You can read the original announcement here:

As part of that change, Hospitable checks whether the main door code is already being shared in your automated messages. If the system doesn't detect %smartlock_code% in the message template, it assumes the code isn't being communicated and may trigger the backup code message instead.

We found that some check-in messages were using phone-based placeholders like %guest_phone% or %guest_phone_last4% to communicate the door code. This historically worked for hosts whose locks were configured to use the last digits of a guest's phone number.

However, because those placeholders aren't recognized as the smart lock code itself, the system could still trigger the backup code message, which sometimes confused guests.

To prevent this, we ran an automated update for affected accounts.

 

What has changed

For hosts with connected smart locks, we updated guest-facing check-in messages that referenced phone-based codes and replaced them with the correct placeholder:

%smartlock_code%

Your message wording should remain the same. We only corrected the placeholder used for the door code.

 

Why it matters

This change helps ensure:

  • Guests consistently receive the correct smart lock code
  • Backup code messages trigger far less often
  • Check-in instructions remain clear and reliable

The goal is for smart lock access to feel seamless for both hosts and guests.

 

Who this affects

This update only applied to hosts who:

  • Have at least one connected smart lock
  • Have backup code communication enabled
  • Were not already using %smartlock_code% in their guest-facing message rules

If you were already using %smartlock_code%, nothing changed.

 

What you should do

No action is required. If you'd like, you can review/edit your check-in message anytime and confirm it includes %smartlock_code%.

--

If anything looks unusual in your messaging rules, reach out via in-app chat or at support@hospitable.com and our team will be happy to help.

In our case the back up code message is being sent, but is NOT giving the guest a code. We had to provide them with a key until we can figure out the issue.