Hi Joshua,
Airbnb does manage the process of sending smart lock codes through integrations, but the code activation timing can sometimes get mixed up due to syncing issues on Airbnb’s end, rather than with the lock itself. When you integrate a Schlage or other smart lock with Airbnb, the platform sends activation and deactivation commands based on the booking dates and times. So, technically, the timing and sharing of the code are managed by Airbnb, not the lock provider.
While Airbnb works with third-party software to facilitate this connection, the behavior you’re seeing often results from Airbnb’s system pushing the command earlier than expected, potentially due to a delay or misalignment in its sync schedule. This is why support teams sometimes struggle to identify the problem as they may first assume it’s a problem with the lock or its configuration rather than with Airbnb’s backend commands.
When talking to Airbnb, clarify that the lock itself is working correctly but that Airbnb’s integration seems to have activated the code earlier than expected. Explain that the problem is with the timing of the code activation triggered by Airbnb’s system, not with the lock hardware or your setup.
Here’s how you might frame it:
"The Schlage lock is operating as expected, but the issue is with Airbnb’s timing for the code activation. Despite the reservation start date being three days away, Airbnb has already activated and shared the code with the guest. This is not a problem with the lock itself, as it’s following the commands it's receiving from Airbnb’s system. I need support to escalate this to the technical team managing Airbnb’s smart lock integration to review the timing settings on Airbnb’s end."
This emphasizes that it’s a scheduling sync issue within Airbnb’s system, which can help route your case more effectively to the team that handles smart lock integrations.
I hope this helps.
All the best,
Upfish Management