How to Set Up Self-Check-In at a Short-Term Rental

Self-check-in is expected now. Most guests would rather walk in with a code than coordinate a handoff with a stranger at 9pm. The question isn't whether to offer it. The question is what happens when it fails.

A smart lock is not a self-check-in system. The lock is one component. The system is the timing of the access message, the content of the arrival instructions, the pre-arrival confirmation, and the documented backup when the keypad doesn't respond. Operators who set up the hardware and skip the rest end up fielding calls they assumed the lock would eliminate.

The places it breaks

Guests arrive with the wrong code in hand. Not because the code is wrong. Because the message that contained it scrolled off their phone four days ago and they're now searching a cluttered inbox with two bags in the driveway.

The lock has a dead battery. You checked it three months back. A lot of turnover has happened since.

The guest enters through the wrong door. The listing says "main entrance," which to them is the gate off the street, not the side door off the driveway that your instructions mean. They stand in front of the gate for fifteen minutes before calling.

These aren't rare. Each one generates a call to whoever has the ops phone that evening.

When to send the code

Sending access information two weeks early is a genuine risk. Guests who receive codes well before arrival occasionally share them with people they trust. A code in the hands of a houseguest's sibling who decides to pass through while you have another booking is a specific category of problem.

Send the access message 24 to 48 hours before check-in. That window is close enough to travel that the information is on the guest's radar. Far enough that they're not already pulling into the driveway when it arrives.

A second send on the morning of check-in day is worth adding to the sequence. Not a repeat of the full arrival message. A shorter note: "Here's your access code for today." Guests who are thinking about their drive are thinking about their check-in. That's when the information is most likely to get read.

What goes in the arrival message

The temptation is to consolidate everything in one place. The check-in instructions, the wifi password, the parking notes, the pool settings, the house rules. Resist this. A five-minute message produces guests who read none of it and call you when they arrive.

The arrival message has one job: get the guest through the front door. It should contain:

• The specific door they need, with a landmark if the entrance is at all ambiguous
• The code, formatted in a way that's hard to misread (avoid fonts where 0 and O look identical)
• A single instruction for what to do if the code doesn't work

That last item matters more than most operators expect. "If the keypad doesn't respond, hold the handle down before entering the code" or "wait two seconds after the last digit before pulling the handle" prevents a significant share of lockout calls. Guests who understand the quirk don't call.

The welcome guide comes later, once the guest is inside and looking around. That's the place for the wifi password and the pool instructions. Guests who have settled in will read it. Guests who are standing on a porch in the dark will not.

The confirmation step

This change eliminates more calls than any other single addition.

The day before check-in, send a short message asking guests to confirm they have the access information. Not a general "do you have questions?" A specific ask: "Do you have your access code for tomorrow?" Guests who can't find the original message respond immediately. You resend the code. The problem is solved at 2pm instead of 9pm.

Guests who booked months ago are the ones who need this most. A booking placed four months in advance may have had the original message buried under a hundred other emails. A one-line prompt the day before is a reset that takes thirty seconds to send and saves an evening call the rest of the time.

A backup plan that actually works

Every self-check-in setup needs a documented backup that isn't "call us." Calling you is what they'll do. Your job is knowing what happens next before the call arrives.

Options that hold up in practice:

A secondary code. Most smart locks support multiple user codes. A backup code that doesn't rotate with each guest gives you something to share immediately without a physical handoff. Keep it separate from the standard guest code and rotate it on its own schedule.

A lockbox with a physical key, mounted away from the primary entrance. If the electronic lock fails entirely, you can direct a guest to the lockbox code over the phone and they're inside in two minutes. A combination lockbox that uses a different code from the smart lock is better than a keyed box they'd need to bring back.

A co-host or neighbor who can get to the property within 30 minutes. Not someone who might be around. Someone who has agreed in advance, has a key, and knows the property layout.

Most backups never get called on. The value is knowing the answer to "the code isn't working at 9pm on Friday" before that call comes.

Testing the hardware

A lock that fails is usually a lock nobody tested in several months. Set a recurring check every 60 days: battery level, keypad response, code entry, and the physical mechanism. On wifi-connected locks, also confirm the app is showing connectivity before you rely on it for an arrival.

If your lock app reports battery percentage, check it before each arrival. Under 20% is a replacement, not a watch-it-for-another-week. Batteries going out mid-stay leave a guest who can't unlock the door from outside and can't lock it when they leave.

The maintenance schedule post covers how to build a rotation that actually runs across multiple properties without relying on anyone remembering.

Rotating codes after checkout

The guest has left. Their code should stop working at checkout or very shortly after.

Smart locks connected to a property management system can handle this automatically. Codes tied to a reservation expire when the checkout time passes, no manual step required. Pomello uses Seam to manage access grants per reservation, so the rotation happens in the background alongside the rest of the turnover.

For locks managed manually, code rotation is a checklist item the same as the cleaning confirmation. Building it into the post-checkout process is more reliable than treating it as a separate habit.

Check periodically that expired codes stay expired. Pull up a code from two stays ago and test it. If it opens the door, the rotation process has a gap. Better to find that in a test than to wonder later who has access.

When a guest still calls

A well-run system still produces occasional calls. A guest who skips all the messages, a genuine hardware failure, a situation the instructions didn't anticipate.

The gap between a system that works and one that doesn't is how often that call happens. One call in every forty or fifty bookings is normal variance. One call in every six or seven stays is a structural problem somewhere in the sequence.

Track each one. Note what broke. After six months, you have a list of actual failure points specific to your property, which is a more useful guide to fixing things than any generic checklist. The guest communications post covers other places in the guest sequence where templates and timing reduce friction.