The door code doesn't work. Now what?

Get the guest inside first, diagnose second. Nearly every smart-lock failure at the door is one of four things: the code is being entered wrong (or the keypad has briefly locked itself out), the code never actually reached the lock, the batteries are dead, or the lock has dropped its connection. Three of the four can be fixed from your phone in a few minutes — if you check them in the right order. Here is that order, what it looks like on Schlage, Yale, and August, and the one habit that makes the whole problem rarer: a fresh code for every guest.

Get them inside before you diagnose

A guest standing at a locked door with luggage is not a debugging session; it is a countdown to a bad review. Reply first — "I'm on it, give me two minutes" — then reach for the fastest unlock, not the correct one. Most locks can be opened remotely from the app. If yours can't, or it's offline, send a backup one-time code, or point them to the physical key in the lockbox you keep for exactly this night. Elegance can wait. The diagnosis below happens after the door is open, or in parallel while they wait.

The four failures, in the order to check them

1. Entry error or keypad lockout. The cheapest fix is the most common. Most keypads want a confirm press — the Schlage logo button, Yale's checkmark, a # on others — and guests skip it. And after several wrong attempts, most locks disable the keypad for a minute or more, so the correct code entered on try five also "fails." Ask the guest to wait sixty seconds, then enter the code slowly, ending with the confirm key. This resolves a surprising share of "the code is broken" messages by itself.

2. The code never reached the lock. A guest code you created in the app only works once the lock has synced it. If the lock was offline when you pushed the code — or the code was scheduled to activate at check-in and the sync never happened — the app looks fine while the lock has never heard of it. Open the app and check whether the code shows as active on the lock itself, not just created. If it doesn't, push it again or issue a new one, and watch for the lock to confirm before telling the guest.

3. Dead batteries. If the keypad won't light up or beep at all, it's power, not the code. Check the app for a low-battery warning or a last-seen time that's hours old. Cold weather drains batteries fast — a cabin market in January eats them in months, not the year the box promises. Some Schlage and Yale models take an emergency battery held against terminals under the keypad; otherwise it's the key override or the lockbox. Put battery checks on the turnover checklist and this one mostly disappears.

4. The lock is offline. August needs its Wi-Fi bridge in range and powered; many Yale models talk through a module or hub; Schlage Encode sits on your Wi-Fi directly, and a router reboot or an ISP blip can orphan it. Here is the useful fact: codes already stored on the lock keep working offline. Connectivity failures stop you from pushing new codes and from unlocking remotely, but they don't break an existing code — so if the guest's code fails and the lock is offline, the real problem is usually #2: the code never made it on before the connection dropped.

Why every guest should get their own expiring code

A reused "house code" fails you twice. It is a security hole — every past guest, and everyone they shared it with, can still open your door. And it is a diagnostic fog: when the one code everybody uses stops working, you learn nothing. Per-guest codes, activated at check-in and expired at checkout, fix both. If this guest's code fails but the cleaner's still works, the lock is fine and the problem is the code sync. The lock's log tells you who opened the door and when. And a former guest's code opens nothing, ever.

Make it a system, not a scramble

Everything above is doable by hand, which is exactly why it gets skipped in a busy week. This is the part StayPilot automates: for Schlage, Yale, and August locks, each guest's code is created, sent, activated for their stay, and expired at checkout — nothing reused, nothing to remember. When a guest messages "the door code says invalid" at 2am, it answers in under a minute, walks the checks above, diagnoses the lock remotely, and issues a fresh code to get them inside — with every message logged, and anything unusual flagged to you.

If you want to see what that sounds like for your property, paste your listing into the demo and ask it the question this post started with: "the door code doesn't work." The answer should read like a host who has done this before — calm, specific, and already reaching for the backup code.