The guest is outside in the rain, the cleaner is still making the bed, and a WhatsApp message arrives: “Which flat is it?”
The most common check-in problems are rarely dramatic. They are small gaps between what the property manager knows and what a tired guest can work out while holding a suitcase in front of three similar doors. The fix is usually not a longer welcome pack. It is better timing, clearer photos, property-specific instructions and a backup plan that does not depend on one person spotting a message straight away.
Why check-in instructions fail in the last 20 metres
Most teams already send the address, access code and check-in time. Yet the guest still gets stuck. The information exists. It just is not usable at the exact moment they need it.
At the door, guests may be carrying bags, checking a low phone battery, keeping an eye on children or trying not to block the pavement. They will not enjoy searching a twelve-page PDF for one photo of the key safe.
A useful arrival message answers the next question, in the order the guest will ask it. It does not ask them to understand your filing system.
Write for the guest at the door, not for the person calmly reading at home.
The common check-in problems worth fixing first
1. The guest arrives before the property is ready
An early arrival request can turn into a turnover problem quickly. It is 1:45pm, check-in is at 3:00pm, the cleaner has just arrived, and the previous guest is still asking whether 12:30pm counts as a late checkout. Do not leave the arrival time buried halfway down a welcome message.
Your guest should know:
- The confirmed check-in time
- Whether early access is possible
- Whether luggage can be left at that specific property
- How they will be told that the property is ready
If early check-in depends on cleaning, keep the answer conditional and make sure one person owns the update. “We’ll see” is useful for ending a conversation, but not for managing an arrival.
Check-in is from 3:00pm. The flat is still being prepared, so please wait for our ready message before entering. We cannot store bags before check-in, but you can use [local luggage option]. We’ll update you here if it is ready early.
A portfolio-wide promise about bag storage is risky. One building may have a locked cupboard; another may have nowhere sensible to put two large suitcases without blocking the cleaner.
2. The key safe is visible, but impossible to find
“The key safe is beside the door” sounds clear until the building has three doors, four black boxes and a recycling area that looks suspiciously like an entrance.
Give the guest one exact location sentence:
The key safe is fixed to the brick wall on the right of the blue entrance door, below the intercom and roughly knee height.
Adding useful photos to your guidebook can help guests recognise the entrance and key safe before they arrive. A close-up proves that a key safe exists, but not where it is. Retake photos after changes to paintwork, gates, signs or landscaping. Bins are poor landmarks because they move, especially on collection night. A planter that disappeared six months ago should not remain the main navigational clue.
Test the full sequence with someone who does not know the property. For late arrivals, test it after dark too. A stiff key-safe cover can feel very different in cold rain with a suitcase balanced against your leg.
3. The code in the message is wrong
Wrong door codes usually come from stale notes, copied templates or a last-minute code change that was updated in one place but not another.
Keep one source of truth for each property. It should make clear:
- Which code opens the communal entrance
- Which code opens the flat door or key safe
- Where each code is used
- When the code was last changed
- What the backup access plan is
After a code change, update the main property record first. Then update any scheduled messages, guidebook content and team notes. Finally, test the code as a guest would use it. Be careful with similar property names. “Oak House 2B” and “Oak Court 2” are different enough in a spreadsheet and dangerously similar in a busy WhatsApp thread.
If the guidebook still says 4182 but the lock was changed to 7410, AI will repeat the wrong code. Speed cannot rescue stale instructions.
4. The parking bay is obvious only if you already know where it is
“Parking is at the rear” is not an instruction. It is a clue.
Good parking directions explain the route a first-time visitor should take, including:
- Turn: where to turn
- Entrance: how to recognise the vehicle entrance
- Bay: the bay number or marking
- Access step: any gate, barrier or permit step
- Fallback: what to do if the assigned bay is occupied
Drive past the main entrance and turn into the narrow lane immediately after the brick wall. Use bay 7, marked “Flat 2B”. The parking photo is taken facing the building. If the bay is occupied, message us before using another space.
Photos should show the approach as well as the bay. A tight shot of a white number painted on tarmac does not help a guest who is circling the block at 8:45pm. Also check the map pin. Postcodes can cover several entrances, and navigation apps may lead drivers to the service road while pedestrians are sent to the front gate.
5. The guest does not read the arrival message
Sometimes guests skim. Sometimes the message is simply too long, arrives too early or hides the useful part under restaurant recommendations and house rules. If this is part of a wider guidebook problem, see why guests do not read your short-let guidebook.
Do not send one giant message at booking and assume the job is done. A practical rhythm is:
- At booking: Confirm the check-in window and ask for an estimated arrival time.
- The day before arrival: Send the exact address, parking route, access method and any action the guest must take.
- On check-in day: Send a short, action-only reminder with the entrance, code location, flat number and help route.
Same-day bookings need a compressed version, but the order should stay the same. Put the immediate steps in the message body. The full guidebook can hold appliance instructions, bins, heating and local recommendations. A guest standing outside should not need to open a PDF, zoom into page seven and hunt for a tiny key-safe photo.
The same rule applies once they are inside. If the Wi-Fi code is buried in that PDF, someone will ask for it.
6. The guest finds the building, but not the flat
This is the classic “Which flat is it?” message. The street address may be correct, but the final route is missing. The guest enters through the right communal door, sees an unmarked staircase and has no idea whether “second floor” means two flights up or the level above ground.
Include:
- The building name or number as it appears from the street
- The correct entrance colour, material or fixed landmark
- The floor in plain language
- The flat number, name or door label
- The final turn after leaving the stairs or lift
- A door detail that is unlikely to change
For an awkward layout, “two flights above the ground floor, then the first door on the left” is often clearer than “Flat 6, second floor”. Walk the route with someone who has never visited. Do not give them hints. Every place they hesitate is a sentence or photo that needs fixing.
7. There is no backup when self-check-in fails
Every self-check-in process needs a plan for the moment it stops being self-service. Set the escalation triggers before the 11:40pm message arrives. A human should step in when:
- The confirmed code fails more than once
- The key is missing
- The key safe or smart lock is jammed
- The communal entrance is unexpectedly locked
- The guest opens the door and the property appears occupied
- The instructions and photos no longer match the building
The backup plan may involve a spare key holder, a local team member, an approved alternate entrance or a call to the lock provider. The right answer depends on the property. Write down who owns the next step and what information they need. Asking the guest for a photo of the door or key safe can help, but automation should not keep repeating the same code while someone stands in the rain.
Build a check-in message that works under pressure
One message should follow the sequence the guest will physically experience. Put the details in this order: ready time, address, entrance, access, flat, parking and help.
| Detail | Why it matters |
|---|---|
| Ready time | Prevents early entry while the turnover is still active. |
| Address | Gets guests to the right building, not just the right postcode. |
| Entrance | Stops them choosing the wrong identical door. |
| Access | Shows where the code, lock or key safe is used. |
| Flat | Confirms the final door, floor and label. |
| Parking | Keeps drivers from guessing at the kerb. |
| Help | Tells them what to do when the notes stop matching reality. |
Check-in today
Ready from: 3:00pm. Please wait for our confirmation before entering.
Address: [full address and postcode]
Entrance: [colour or fixed landmark]. Use the [left or right] door shown in photo 1.
Access: The key safe is [exact position]. Lift the cover, enter [code], then [opening action].
Flat: [flat number or name], [floor], [door description].
Parking: [route and bay]. See photo 2.
If the code fails twice, the key is missing or the box is jammed, reply
LOCKED OUThere so a person can step in.
Do not cram the thermostat, bin schedule, nearest coffee shop and checkout rules into this message. Those details can live in the guidebook. First, get the guest through the correct door. For a fuller framework, see how to write guest instructions that people actually follow.
Use AI for repeatable answers
Check-in questions are good candidates for AI support because many have clear, property-specific answers:
- What time can I arrive?
- Which entrance should I use?
- Where is the key safe?
- Which parking bay is mine?
- Can I leave my bags?
- How do I find Flat 2B?
That is the kind of routine, factual question letbloom.io is designed to support: the guest asks in normal language, and the answer comes from the property’s guidebook, house rules, local notes and arrival instructions.
AI is useful when the notes match reality. If a code fails twice, a key is missing, a lock is jammed or the guest may be at the wrong property, a person should take over. The guide on late-night guest messaging goes deeper on what to answer automatically, what to hold and what to escalate.
It is also only as useful as the information behind it. If three guests ask the same parking question in a week, treat that as a guidebook problem and rewrite the directions.
In summary
Many check-in problems come from small assumptions: the guest will spot the right door, recognise the bay, remember the code or read the whole PDF. Remove those assumptions. Give the right detail at the right time, show the route clearly, test the access steps and make the human backup obvious. It is not glamorous work, but it prevents a lot of 3:05pm chaos.
