Stop staying up for late check-ins: a host's guide to async arrivals

The 23:30 phone call is the host's rite of passage. First booking that lands on a delayed flight; first guest who can't find the lockbox in the dark; first time you realise the “flexible check-in” you advertised actually means “you, awake, until they arrive.”

This guide is how to make late check-ins zero-touch. The principles are the same whether you have one property or fifty: pick an access method that doesn't need you, document it so the guest can't miss it, and have a single fallback for when something goes wrong — that's a person, not a device. Below: the three access methods, their honest trade-offs, what to say in the manual, and the fallback layer that keeps the system robust.

The three access methods

In practice, short-term rentals use one of three patterns. Each has trade-offs in cost, reliability, and guest experience.

1. Mechanical lockbox

A small combination box mounted near the front door that holds a physical key. Cheap (≈$20–40), no electronics, no batteries, lasts a decade. The guest dials the code, opens the box, takes the key.

Pros. Failure modes are rare and physical — the box doesn't run out of battery, doesn't lose WiFi connection, doesn't care if your phone is dead. Works identically at 03:00 in a power cut as at noon. Cheap enough that having a spare on hand for replacements is trivial.

Cons. Three real ones. (a) The code is shared — every guest gets the same code unless you change it between stays, which most hosts don't. (b) The key inside is a physical key, which gets lost. (c) Mechanical boxes can be picked or shimmed by anyone determined enough. For a city-centre Airbnb the security ceiling is modest; for a remote cabin it's fine.

Right for: hosts who want zero ongoing maintenance, properties where the security risk is acceptable, anywhere the local power grid is flaky.

2. Smart lock (battery-powered, on the door)

A motorised lock that replaces (or sits over) the existing deadbolt. Guests enter a code on the keypad and the bolt slides back. The host generates a new code per stay via an app.

Pros. Per-stay codes mean the code that worked for the last guest doesn't work for the next, which closes the shared-code problem. App-based monitoring tells you when the guest arrived, which is a small but real service-quality signal. Modern smart locks are well designed and survive years of daily use.

Cons. Three real ones. (a) Batteries. The lock needs them, they go flat, the guest is locked out. Reputable models give 6–12 months of life and a low-battery warning, but the warning depends on you noticing it. (b) WiFi-coupled smart locks add another failure mode — when the WiFi goes down, the remote-management piece breaks (the local keypad still works on most models). (c) Upfront cost is $150–300 per door and installation can require basic tools and a steady hand.

Right for: urban properties, multi-property managers, anywhere the per-stay code change matters more than the upfront cost. Less suitable for remote or off-grid properties where battery monitoring is hard.

3. Smart key safe (or smart lockbox)

The compromise option. A keypad-equipped lockbox that issues per-stay codes via an app, but the box itself holds a physical key. The guest punches the code into the box, the box opens, they take the key, the key unlocks the door normally.

Pros. Per-stay codes (like a smart lock) without modifying your front door. The door itself is unchanged — a landlord can't object, a building manager can't veto. Cheaper than a smart lock (often $80–150).

Cons. Same battery problem as a smart lock. The physical key inside still gets lost, just less often because each stay starts and ends with the key being returned to the box. Slightly more friction for the guest (two steps: open box, then unlock door) but no real difference once they've done it once.

What to put in the manual

Whatever access method you pick, the manual section for it lives or dies on specificity. The guest is standing in the rain at 23:47; vague instructions are worse than no instructions.

A template that works, regardless of method:

1. Exact location with a landmark — “to the left of the front door, wall-mounted, brass, next to the porch light.”
2. Photo of the device from the guest's perspective (i.e. how they'll see it when they arrive).
3. The code, copy-able. For shared codes, just the number. For per-stay codes, the code embedded in the manual the guest is reading (which is unique per booking on platforms that support it).
4. The exact order to press buttons or dial digits. Some lockboxes need the digits dialled then a lever pulled; some smart locks need a hash key pressed first.
5. Any quirks. The handle that lifts before pushing. The door that needs a shoulder against it. The lock that turns the unusual direction.
6. The fallback line: “If anything's not working, tap Call Host below — the cover person on duty will get you in.”

The fallback is the most important part

The 95% of arrivals go fine. The 5% that don't are the entire reason the system needs robustness. Dead battery, jammed lock, code typo, lockbox stuck — the cause varies, the guest's situation is the same. They're outside, late, increasingly worried.

A fallback layer that routes the guest to a real person within minutes is the difference between a minor inconvenience and a one-star review. The practical patterns:

• A night-cover phone number. Someone — you, a co-host, a neighbour, a property manager — who answers between 21:00 and 08:00 and can drive over with a spare key in 20 minutes.
• A spare key hidden somewhere the guest can be guided to over the phone. Useful as a tier-2 fallback when even the night cover can't reach the property. Best practice: don't put this in the written manual — give it to the night cover, who reveals it on the phone if needed.
• A clearly-stated “if the lock is dead, here is the locksmith we'll send” line. Sets expectations and turns an emergency into a solvable scenario.

Multi-property hosts run into a related problem: who's on duty for WHICH property at WHICH hour? Hard-coding a single phone number in every manual means whoever owns that number is on call 24/7 for every property forever. Better to set up a rotation and route the “Call Host” button to the right person automatically — see Call Host for how this works.

The two-week test

When you change anything in the access system — new lockbox, new smart lock, new code rotation — the first two weeks tell you most of what you need to know. Watch for: messages asking for re-clarification of the steps, mid-stay reports of jamming, any guest who arrives at the door and stops. Each one is feedback. Tighten the instruction, add the photo, fix the quirk in the manual.

What this gets you

The host who sets this up properly stops answering late-arrival messages within a couple of months. The system either works (95%) or escalates to the cover person (5%) — neither path lands on your phone at 23:30 on a Sunday. Combined with a tightly-written welcome manual that handles the other four canonical guest questions (WiFi, parking, checkout, house rules), the host's actual workload per stay drops to: respond to one or two genuinely interesting questions, and do one cleaning.

staymanual's starter manual ships with a Check-in section pre-formatted with the right structure (with photo + quirks + fallback line), and the Call Host feature routes the guest's late-night tap to whoever you've put on duty for that night. Start free for one property — every feature, no card on file.