Hospitable now lets guests lock and unlock the door from the guest portal

Hospitable has put smart lock control into its guest portal. Guests can see their door code, request a backup code, and lock or unlock the door themselves, without installing a separate app from the lock manufacturer.

The sequencing is the interesting part. A "Getting inside" section appears in the portal before arrival. The code becomes visible 24 hours before check-in, but it does not actually work until the access time set on the reservation. After check-out the whole section disappears, so the codes and the lock controls go with it.

Before any of that, the guest has to verify their identity by SMS or email. No verification, no code and no remote unlock. Properties with more than one lock are supported, and the guest sees each of them.

What this changes day to day

Most operators running smart locks currently send a code by message, or ask the guest to install the lock vendor's app. Both have the same failure mode: the code arrives, the guest loses the message, and somebody on the team ends up finding it again at 11pm. Putting the code in the portal the guest already has, with a self-service backup code behind it, takes that call out of the night.

Remote lock and unlock is a bigger shift than the code. It moves a piece of access control from the operator to the guest. For a guest who has shut themselves out while the door was on a deadbolt, that is a real fix. It also means a guest can unlock a door remotely for anyone, which is worth thinking through on multi-unit properties and on anything with a shared entrance.

What the changelog does not say

Two gaps, both material.

It does not name the supported lock providers. Hospitable connects to a range of smart lock brands, and nothing in the entry says this works with all of them or only some. If you run mixed hardware across a portfolio, which is common, you will need to check your own brands rather than assume coverage.

It also does not say which plan this lands on. Hospitable has put several recent features on specific tiers, Direct Premium among them, so the absence of a tier here is not the same as it being on every plan.

The verification step deserves a second look too. SMS or email confirms that whoever is in the portal controls the phone number or inbox on the booking. That is a reasonable bar for releasing a door code. It is not identity verification in the sense of checking a document, and it inherits whatever the booking channel put in those fields. On an OTA booking with a masked email address, that is worth testing before you rely on it.

Where it fits

This is the second access-related change Hospitable has shipped in two weeks, after exposing lock control through its MCP server so an AI assistant can open a door on a plain English request. The direction is clear enough. Hospitable is making the lock a first-class object in the platform rather than an integration you configure once and forget.

For operators the near-term action is small. Check your lock brand is covered, check the plan, and run one reservation end to end before you stop sending codes by message.