Short answer: Verify the guest through the established booking channel, check the correct entrance and authorized access window, and escalate to a vetted local responder when remote recovery fails. Do not publish bypass instructions, default codes or hidden-key locations. Safe access requires both a remote contact and a physical backup.

Assess safety before diagnosing the lock

Ask whether anyone is in immediate danger, exposed to unsafe weather or needing urgent medical help. Direct emergencies to local emergency services. Ordinary refund approval should not delay safety action. Confirm the reservation and guest through the platform thread or another previously verified contact—not a new unverified caller asking for the master code.

Collect only what is needed: property, entrance, current time, reservation status and the symptom. Do not ask the guest to post complete credentials or identity documents in a public thread.

A safe symptom checklist

Symptom	Safe remote check	Local next step
Wrong entrance	Match approved arrival instructions and property photos	Verified responder if location remains unclear
Code not active	Confirm correct booking and authorized time window	Responder if supported credential correction fails
Low battery alert	Check the installed lock’s documented status	Qualified local person following manufacturer instructions
Internet outage	Check actual device behavior; some locks retain local access	Approved physical backup if access cannot be restored
Mechanical fault	Stop repeated forceful attempts	Qualified locksmith/local responder

A Wi-Fi outage does not disable every smart lock. Follow the manual for the actual installed model; do not adapt random instructions from another device. Store that manual, installation details and the authorized support contact privately in the property operations file.

Recovery and dispatch sequence

Verify guest/reservation, entrance and check-in window using existing records.
Check supported lock status and credential configuration through authorized access.
If supported and appropriate, issue a temporary guest credential privately to the verified guest. Never send administrator credentials.
If remote recovery fails, call the vetted local responder with their authorized physical backup arrangement.
Confirm who accepted the job and their actual arrival estimate; do not promise an unconfirmed time.
Escalate mechanical failure to qualified help within the owner-approved emergency spending limit.
If access cannot be restored, contact the platform and owner about accommodation options and guest remedies.
Record the guest’s confirmation of entry, not just an app status.
Revoke temporary access and have the local person inspect the cause.

Keep emergency key locations, access tokens and feed URLs out of public articles, screenshots and broadly shared vendor chats. A co-host should have the minimum supported permissions needed, not the owner’s password.

Owner approval versus immediate help

Write down a locksmith/response cap, alternate approver, no-response fallback and conditions for contacting emergency services. These are owner-set controls, not platform guarantees. A local responder’s accepted dispatch and arrival estimate are evidence; “we have someone nearby” is not.

Refunds and relocation expenses use separate approval rules. Airbnb’s refund guidance distinguishes Resolution Center goodwill from reservation alterations; verify the correct tool and whether the platform has already acted before sending money. Airbnb refund instructions. See the refund matrix.

Keep a useful incident trail without exposing secrets

Record reservation/incident reference, first report, acknowledgement, accepted dispatch, entry confirmed, root cause, authorized expense, temporary-access revocation and device repair. Do not record the full temporary code in a broadly accessible monthly report. Restrict detailed credential records and delete them when no longer needed.

Close the ticket only when the guest has entry and temporary permissions are secured. Arrange battery or hardware maintenance using manufacturer guidance; never tell a guest to defeat a lock or dismantle electrical equipment.

Prevent repeats through the next handoff

Have the local team test guest entry between stays, confirm the intended time window and report battery/device alerts according to the property plan. Keep approved arrival photos current. Airbnb requires accurate listings and timely contextual communication; our access checklist is an editorial operating recommendation, not a new smart-lock purchase mandate. Airbnb ground rules.

If daily guest support is what you want to delegate, review Airbnb Essentials. Remote coordination does not replace a locksmith, handyman or emergency responder. Compare costs with those local roles included honestly.

Last fact-checked: November 3, 2026 · Official sources linked beside the relevant facts. Recommendations are editorial guidance, not platform requirements.