Skip to main content
Answered

Schlage code error message to guest, reverts to "alternate" code which is actually the correct code

  • February 28, 2026
  • 6 replies
  • 189 views

Dillon
New Participant
Forum|alt.badge.img

This issue has been occurring for the past few months.
Upon new guest arrival, a message is automatically sent to guests stating : “We encountered an issue while setting your code on the lock. No need to worry! Please use this code instead xxxx”

The problem is that the “backup” code is always the exact code it was meant to be in the first place!
Eg: if the code was always meant to be 5566 (the last 4 digits of a phone number), then this error message is sent out to the guests just before checkin saying “We encountered an issue while setting your code on the lock. No need to worry! Please use this code instead 5566”
It’s confusing for guests and also unnecessary.

 

This is happening on both ABB and BDC

Thanks in advance to anyone who can explain and solve this.

 

Best answer by Kristijan Laco

Hi ​@Dillon ,

Thanks for flagging this, I completely understand why that would be confusing for guests.

What’s happening here isn’t actually a lock error. The “backup code” message is triggered when the system doesn’t detect the %smartlock_code% shortcode inside your check-in message. When that shortcode isn’t present, we automatically send the fallback message as a safety mechanism.

The good news is this is easy to fix.

You’ll want to edit your check-in message and make sure it includes the %smartlock_code% shortcode where you’re providing the entry code instead of using %guest_phone%. Once that’s in place, the system will recognize that the code is already being communicated and the backup message will stop sending.

Appreciate you calling this out, and we’ll also take this feedback on board, as we’re looking at ways to make this more seamless by default.

6 replies

Kristijan Laco
Hospitable Team Member
Forum|alt.badge.img+4
  • Hospitable Team Member
  • Answer
  • February 28, 2026

Hi ​@Dillon ,

Thanks for flagging this, I completely understand why that would be confusing for guests.

What’s happening here isn’t actually a lock error. The “backup code” message is triggered when the system doesn’t detect the %smartlock_code% shortcode inside your check-in message. When that shortcode isn’t present, we automatically send the fallback message as a safety mechanism.

The good news is this is easy to fix.

You’ll want to edit your check-in message and make sure it includes the %smartlock_code% shortcode where you’re providing the entry code instead of using %guest_phone%. Once that’s in place, the system will recognize that the code is already being communicated and the backup message will stop sending.

Appreciate you calling this out, and we’ll also take this feedback on board, as we’re looking at ways to make this more seamless by default.


Tom Beerley
Hospitable Hero
Forum|alt.badge.img+3
  • Hospitable Hero
  • February 28, 2026

@Dillon I was in the same boat as you, where I don’t explicitly tell the guest the actual digits of their keypad code. I just say, “it’s the last 4 digits of your phone number.” So when Hospitable implemented the customizable “failsafe” message a couple months ago, the default wording for that message unfortunately makes it sound like something’s wrong, even though there’s not. I fixed it by changing the “Smart lock backup code” message to say this:

Hi %guest_first_name%, this is an automated message to re-confirm your keypad access code for check-in: %smartlock_backup_code%. This should be the last 4 digits of the phone number that was used to book your stay. If you'd like us to use a different code, let us know.


anthonyrallo
Top Contributor
Forum|alt.badge.img+3
  • Top Contributor
  • February 28, 2026

@Dillon - we adjusted to pretty much the same thing ​@Tom Beerley is doing. 

 

I put out a big flare in the Airbnb community (and to someone who was visiting Airbnb HQ before this was finalized) that it was IMPERATIVE the “Airburner number” they give to guests must at least match in the last 4… I’m so happy that was implemented b/c all of our documentation (in HSPTB and our guides) talks about the last 4. Oh and most guests know their own number… sheesh.


Tom Beerley
Hospitable Hero
Forum|alt.badge.img+3
  • Hospitable Hero
  • March 1, 2026

@anthonyrallo you gave me a panic attack for a minute there! Based on the fact that my “suggested door code” still always matches the last 4 of the guest’s “supposed” phone number, I’ve been under the impression that Airbnb still hasn’t fully rolled out the “fake” phone numbers to all hosts, and that I am still grandfathered to receive the actual phone number. I do still send texts directly to guests as part of my welcome flow, and I’ve been presuming that the conversations are private (which they are definitely NOT when Airbnb is intercepting and relaying the SMS messages).

Luckily the panic subsided when I used the FOREWARN tool to validate the last few phone numbers I’ve received from Airbnb. Sure enough, I am still receiving ACTUAL phone numbers, as verified by the personal records returned by FOREWARN.  

BTW, FOREWARN is a self-service background check tool that the National Association of REALTORS makes available to its members. You can do your own background checks with it (it was offered as a personal safety tool after some highly-publicized attacks on REALTORS). But you can subscribe to it yourself and it could be an alternative to paying for guest verification on every reservation. It shows you everything from felonies to traffic tickets.  


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

@Tom Beerley Hadn’t heard of FOREWARN before - sounds pretty cool. I do have a tool available with my Safely plan that allows me to do background checks. 

Right now, I’m doing RAs somewhat manually until a few things are fixed with HSPTB’s ( ​@Abby Grous knows the items) - but for now I send the following message. If the number is wrong (as if Air sent over the burner number) I’d imagine the guest would reply “that’s not my number” or something.

 

 

%guest_first_name% - Did you receive an SMS at your registered mobile %guest_phone% from SignNow (888 -806-1117) with a request to complete (it's not spam)? It will say "hello@awayzingstays.com has sent you a document. " No need to download the app or pay for anything, just click the link at the bottom that says "Sign with mobile browser" and you'll be able to complete it. We would request this back within 48 hours so we can have your reservation completely processed and confirmed. Please let us know if you have questions about the area too! We have developed an extensive guide for you that we'll send digitally prior to your arrival so you can get familiar with the home and town. -whitney & anthony


Harmony Holdings
New Participant
Forum|alt.badge.img+1

Thank you for posting this! I was encountering the same issue, but with my Yale locks. It was annoying me and somewhat confusing to guests, but now I know how to fix- thank you!!