Vacation rental check-in without a lockbox

A guest lands at 23:40 after a delayed flight and someone has to open the door. In vacation rental check-in there are three ways to handle that: you go, you pay someone to go, or you let the arrival run on its own. The lockbox hanging on the façade was for years the cheap version of the third option. Today there are better ways to do it, with a record of who goes in and a code that expires when the stay ends.

This guide explains what replaces the lockbox, how to choose the lock, how to chain each step of the arrival and what to do when something breaks at midnight.

Why drop the lockbox?

A lockbox solves one problem and creates several. It works as long as nothing goes wrong, and when something does go wrong it leaves no trace.

These are the failures that come up again and again:

• The code almost never changes, so former guests, cleaners from past seasons and anyone who saw it written in a message know it.
• Nobody knows who opened the box or when. If something goes missing from the flat, you have nowhere to start.
• The key gets lost, stays inside or leaves with a guest by mistake, and the next arrival is left on the street.
• The box is in plain view of everyone walking down the street, with what that means for the flat's security.
• At night, in the rain or with a poor connection, the guest cannot find the box or cannot open it.

None of these problems is about the box itself. They are about a shared physical key and an access point that knows nothing about the booking. Changing the box does not fix them; changing the model does.

What you lose by removing it, and how to cover it

The box has one real virtue: it depends on neither internet nor batteries. Any alternative has to cover that gap with codes that work offline, low-battery alerts and a plan B for the night when everything fails. You will see how below.

Which options replace the lockbox

There are four common models. Each one fits a different kind of operation.

| Model | How it works | Late arrivals | Entry record | Technical dependency |
|---|---|---|---|---|
| In-person handover | You or an employee wait for the guest | Expensive and hard to cover | Only what you note by hand | None |
| Check-in company | A third party does the handover for you | Possible, at a surcharge | Depends on the provider | Low |
| Pickup point | The guest collects the key at a nearby shop | Limited to the shop's opening hours | The shop notes the pickup | Low |
| Smart lock | The guest gets in with a code or an app | No problem | Every opening is logged | High: battery, connection and API |

In-person handover makes sense with few flats and predictable arrivals. A pickup point is a reasonable middle ground, except when the flight lands after closing time. Beyond a handful of flats, or with many night arrivals, the smart lock is the only option that scales without adding people.

The lock alone is not enough

This is where most setups fail. A smart lock goes in, but codes are still created and sent by hand from the calendar or the platform chat. This is the same old trip disguised as a message: it breaks just as easily when the guest arrives before anyone has pressed send.

What changes the operation is the rule that decides when the code is issued. The lock is the cheap part of the investment; the integration with your bookings and with the guest register is what makes it reliable.

How to choose a smart lock for vacation rental check-in

The look of the device matters least. Look at these criteria, in this order.

| Criterion | What to ask | Why it matters |
|---|---|---|
| Open API | Can I create and revoke codes from my software, with a start and end date? | Without an API, every code is manual work again |
| Offline codes | Does the lock accept temporary codes even if the wifi drops? | The wifi bridge fails more often than the lock |
| Door compatibility | Does it fit my cylinder and the thickness of the door? | Older buildings often need European profile cylinders with a double clutch |
| Opening log | Does it record who opened and when, and can I read it through the API? | It is your evidence in any incident |
| Battery | Does it warn in advance, and how does it open if the battery dies? | A dead battery at midnight is the worst possible call |

Codes that work without internet

Locks with offline codes compute the code inside the device itself from the time, the same way a bank's key generator does. The code you send the guest works even if the wifi bridge has been down for hours. When the bridge drops, you get an alert on your dashboard rather than a guest locked out on the landing.

Ask the manufacturer whether its temporary codes work this way. Some models only accept temporary codes if they are connected at the moment the code is created and used.

The building's street door

It is the problem nobody looks at until the first guest is stuck on the street. The flat's lock is useless if the street door still needs a key.

The most common solutions:

• A smart module on the video intercom, if the residents' association allows it.
• A second smart lock on the street door, agreed with the residents' association.
• A street-door code that the building manager already runs, sent together with the flat's code.

Talk to the residents' association before installing anything in shared areas. A written agreement keeps someone from removing it on a Monday morning.

Before you buy, check the door

Half an hour in the flat with a tape measure saves returns. Check these points:

• Measure the cylinder on both sides of the door and note the brand and model.
• See whether the door is reinforced or armoured: some locks do not accept certain security plates.
• Check whether the door closes on its own with a spring or has to be pushed. A door that does not fully close leaves the flat open even when the lock works.
• With your phone, look for wifi coverage next to the door if you are going to use a bridge.
• Take a photo of the door from inside and outside to show the installer.

With that information, most manufacturers will tell you which model and which cylinder fit before you pay anything.

How to automate the arrival step by step

The pattern that works is a chain of events: each step starts when the previous one finishes, with nobody watching the calendar.

1. Receive the confirmed-booking notice from the platform or your booking engine and create the stay record.
2. Send the lead guest a check-in link specific to that booking, with one form per occupant.
3. Validate the data while the guest types it: document format, dates and required fields.
4. Report the travellers' data and store the response with its time. The legal detail of this step is in our guest register guide.
5. Once the report is accepted, create a code valid only from the check-in time to the check-out time.
6. Send the code to the guest through the channel they use: email, message or the lock's app.
7. When the stay ends, revoke the code even if it has expired, and keep the opening log.

Why the code depends on the register

Make the code a direct result of the traveller's data having been reported and accepted. No accepted record, no code. The guest register then stops being a task someone has to remember and becomes a condition for getting in.

Starting at the booking, and not at the arrival, leaves room to fix errors in time, even for same-day bookings.

Codes limited to the stay

Issue each code valid from the agreed check-in time to the check-out time, never indefinitely. A code that keeps working after check-out is the same as a lost key. This window is a layer of security the physical key never had.

For cleaning, create separate codes, also limited to the service slot. Mixing the guest's code with the staff's leaves you no way of knowing who went in.

Which messages the guest receives, and when

The chain works best when the guest always knows what is still missing. A sequence that is usually enough:

| Moment | Message | What it contains |
|---|---|---|
| On booking confirmation | Welcome | The check-in link and what it is for |
| The day after booking, if there is no form | Reminder | The same link and which data to have at hand |
| When the record is accepted | Access | The code, its validity window and how to use it |
| The day before arrival | Instructions | Address, street door, floor, photos and a help phone number |
| The morning of check-out | Check-out | Check-out time and what to do with the door on leaving |

Send the code separately from the general instructions. That way, if the guest forwards the address to their companions, the code does not travel with it.

What to do when something fails

A good system is not one that never fails, but one that fails safely and warns you in time.

| Situation | What happens | What to do |
|---|---|---|
| The guest arrives in the small hours | Nothing special: the code was issued when the record was accepted | Check on the dashboard that the opening was logged |
| The lock loses its connection | Offline codes keep working | Check the wifi bridge the next day |
| The battery is low | The lock warns before it runs out | Change it at the next cleaning; do not wait for the final warning |
| The guest register is rejected | No code is issued | Fix the data with the guest and report it again |
| The guest does not fill in the form | The chain stops before the code | Send automatic reminders the day after booking and the day before arrival |
| The code does not open | Usually a code outside its time window | Check the lock's clock and the code's time zone |
| The guest arrives early | The code is not valid yet | Decide in advance whether you accept early arrivals and widen the window only in that case |

Plan B for the bad night

Always have a way to open that does not depend on the chain: a physical key kept in a safe place known only to your team, or a person on call with access to the lock's app. Use it rarely, and note every time you do: if you need it often, there is a fault in the chain worth finding.

How to explain the arrival to the guest

The best lock fails if the guest does not know how to use it. Most calls in the small hours are not breakdowns: they are people who cannot find the street door or who type the code without the confirm button.

Write the instructions as if the guest were arriving tired, at night and without mobile data:

1. Give the full address and a photo of the façade as it looks from the street.
2. Explain how the street door opens, with a photo of the panel or the video intercom.
3. State the floor, the door and add a photo of the landing.
4. Describe how to enter the code, including the confirm key if the lock has one.
5. Add what to do if it does not open: check the arrival time, wait a moment and repeat, and who to call.

An example message that works: "Your code is the one we sent you in the access message. Press the lock's key to wake it up. Then type the code and confirm with the brand key. When it does not open, wait a moment before trying again. And if it still does not open, call our help number: we answer at any time."

Translate the instructions into your most frequent guests' languages and review them every time you change something on the door or the street door.

How much time it saves (and how to measure it)

We will not give you other people's savings figures: they depend on the distance to your flats and on how many late arrivals you have. Measure it yourself; it is easy.

During your next in-person handovers, note down in a table like this one:

| What to note | Why |
|---|---|
| Time you leave and time you get back | The real time of each handover, with travel and waiting |
| Expected and actual guest arrival time | Measures how long you wait because of delays |
| Kilometres or transport cost | The direct cost that disappears |
| Arrivals outside your normal hours | The ones that cost you most and fit worst in your week |

Multiply the average time by the arrivals in a normal month. This is the field time the automatic chain removes. The rest is supervising exceptions: a rejection, a battery, a guest who did not fill in the form.

The second saving does not show up in any table. Nobody on your team has to stay awake for an arrival at two in the morning.

Checklist before removing the lockbox

Go through this list flat by flat. With a single empty box, it is not time yet.

• ☐ The lock has an API and accepts temporary offline codes.
• ☐ The cylinder fits the flat's actual door.
• ☐ The building's street door has a solution agreed with the residents' association.
• ☐ The check-in link goes out with the booking confirmation.
• ☐ The code is only issued when the guest register is accepted.
• ☐ Each code is valid only for the stay window.
• ☐ Cleaning and maintenance have their own codes.
• ☐ You receive low-battery and lost-connection alerts.
• ☐ There is a documented plan B to open without the chain.
• ☐ The opening log is kept and you can look it up.

Klimpy is in pre-launch; in the features we are building we describe how we approach this same flow.

Related articles:

• Klimpy