Checking in a foreign guest at 2am: what actually happens

The last flight into Gimhae lands late, and the airport bus gets into the city well after midnight. If you run a guesthouse in Korea that takes international guests, someone is arriving at 2am tonight. Whether that costs you a night shift depends on decisions you make long before they knock.

Here is what the arrival actually involves, step by step, and which parts can run without a person.

The five things a late check-in has to accomplish

1. Establish who this is. The name on the booking has to match the person standing there — and OTA bookings routinely arrive with a nickname, a romanisation variant, or the name of whoever paid rather than whoever is staying.
2. Record the guest as required. Accommodation businesses in Korea keep a guest register, and the required details for a foreign national differ from those for a domestic guest. Confirm the current requirements for your licence category with your local authority — they are not identical across business types.
3. Collect anything outstanding. City tax, a deposit, an unpaid balance on a pay-at-property booking.
4. Hand over access. A key, a door code, a locker, plus how to get back in at 4am.
5. Answer the three questions everyone asks. Where is the bathroom, when is breakfast, how do I get to the station. In a language the guest reads.

Only the third and fourth are transactional. The rest is information transfer, and information transfer is the part a person does not need to be awake for.

Where late check-in actually goes wrong

The name does not match

This is the most common friction point and it is rarely fraud. It is a booking made by a friend, a passport spelling that differs from the OTA profile, or a name where the family name and given name arrive in the opposite order. A human deals with this by looking at the booking list and using judgement. Any automated system has to do the same thing — which means fuzzy matching against the reservation list, not exact string comparison. A system that only accepts an exact match will fail often enough to need a person anyway.

The guest cannot read the instructions

A door code taped to the entrance in Korean is not a door code for half your guests. Arrival instructions need to reach the guest before arrival, in their language, and be retrievable on their phone when they are standing outside with no wifi.

Nobody knows which bed

For a private room, the room number is enough. For a dorm, the guest needs the room, the bed number, and ideally which locker. Sending "Room 302" to someone booked into a twelve-bed dorm guarantees they wake two people up.

The booking changed and the instructions did not

A room move made at 6pm has to reach the message the guest already received. If arrival details are sent once and never revised, the guest walks to the wrong door.

What self check-in changes, honestly

Self check-in does not remove the front desk. It moves the routine 80% of arrivals off the night shift and leaves the exceptions for a person to handle in the morning — or by phone.

A working flow looks roughly like this: the guest gets a link before arrival, opens it on their phone, scans their ID, the system matches them against tonight's reservations, and returns their room number and door code on screen in their language. If the match is confident, they are in. If it is not, the attempt is flagged for staff instead of being rejected outright.

That last sentence is the important one. The value is not in automating the easy case — it is in failing gracefully on the hard case so that the guest is not stuck outside and you are not woken up. A system that rejects an ambiguous match and shows an error has not saved you the night shift.

The Kimchee flow works this way: an entrance QR or a pre-arrival link, ID scan, fuzzy name matching against the reservation list, and the room and door code on screen. Guest pages are available in Korean, English, Japanese and Chinese. The how it works page walks through the sequence.

What we would do before automating anything

Track your arrivals for two weeks. Write down the arrival time and, for each one, whether a person was needed and why. Most operators find the shape is not what they assumed — often a small number of specific causes account for nearly all of the staffed arrivals, and one of them is fixable with a better pre-arrival message rather than any new system at all.

Automate after that, not before. And if a chunk of your late arrivals turn out to be one OTA whose guests never get your instructions, that is a channel settings problem with a fifteen-minute fix.

We run three properties in Busan and did exactly this exercise before building anything. If you want to compare notes on what your two weeks turn up, get in touch — and the pricing page has the monthly figures if you are costing it out.