Why do guests ask about check-in when the details are already in the listing?

Because arrival is the one point in a stay where being wrong is expensive. A guest standing outside a locked door with luggage and tired children cannot afford to be working from stale information, so they confirm even when they already have the answer. Most check-in messages are not requests for information; they are requests for reassurance, and they are best answered by sending confirmation before the guest feels the need to ask.

What should a check-in message include?

Four things, in this order: the exact address with a note on what the building looks like, where to park, how to get in including the code or key location, and what to do if something goes wrong on arrival. Send it the day before, not a week before, so it is near the top of the guest's messages when they need it. A photo of the door and the parking spot is worth more than a paragraph describing either.

Should I automate early check-in requests?

No. Early check-in and late check-out depend on the cleaning schedule and on whether anyone stayed the night before, so an automatic yes creates a promise you may not be able to keep and an automatic no gives away goodwill you could have had for free. Automate the facts — the standard times, the code, the parking — and answer the exceptions yourself.

How do I stop guests arriving before check-in time?

State the time more than once and give early arrivals somewhere to go. Guests who arrive early are usually not being inconsiderate; they have landed, they have bags, and they have nowhere to wait. Naming a nearby cafe, a car park where luggage can stay in the boot, or offering bag drop when the cleaner has finished removes most early arrivals more effectively than a firmer rule.

Why do guests still ask about check-in when it's all in the listing?

Q: When should I send check-in instructions?

The day before arrival. Sent at booking, they are read on a laptop weeks early and forgotten; sent an hour before, they arrive while the guest is already driving. The day before is when the guest is packing and planning the journey, which is the moment the information is actually used. Many hosts also repeat the door code on the morning of arrival, because that is the single fact people most often cannot find again.

Most check-in messages aren't questions

Read them again with this in mind. "Just checking — is the code still 1-2-3-4?" is not someone who lost the code. "What time can we get in?" from a guest whose confirmation says 4pm is not someone who can't read. These are requests for reassurance, sent by people about to commit to a two-hour drive on the strength of a message they got three weeks ago from someone they've never met.

That reframing changes the fix. You can't reduce a reassurance request by supplying more information — the guest already has the information. You reduce it by supplying confirmation, close enough to the moment that it still feels current.

The four things arrival actually needs

Where it is, and what it looks like. The address plus one sentence: the blue door beside the bakery, second driveway past the church. Sat-nav gets people to the street; hosts forget that the last thirty metres is the confusing part.
Where to park. Consistently underrated. Parking is spatial, and prose is bad at spatial. A photo of the actual spot, taken from the direction guests approach, removes more messages than any paragraph you can write.
How to get in. The code, or where the key is, in plain digits, on its own line. Not embedded mid-paragraph in a message that also covers the hot tub rules.
What to do if it goes wrong. One line. "If the code doesn't work, call me on X — it's usually the # at the end." This is the sentence that prevents the panicked 8pm call, because it converts a crisis into a known step.

Timing beats thoroughness

Send it the day before. Not at booking — that version is read on a laptop three weeks early and is buried by departure. Not an hour before — they're already driving. The day before is when people pack and plan the journey, which is when the information gets used.

Repeating the door code on the morning of arrival is worth the extra message. It's the one fact guests most reliably can't find again, and the one whose absence produces the worst five minutes of the stay.

Arrival is the only part of a stay that can go badly wrong while the guest is standing outside in the rain. It earns its own redundancy.

Early arrival is a logistics problem, not a rules problem

Guests who show up at 1pm are rarely being difficult. They've landed, they have bags, and there's nowhere to be. Repeating the check-in time in bold doesn't solve that; giving them somewhere to go does. Name a cafe. Say whether the driveway is fine to leave a car in. Offer bag drop once the cleaner is out.

And treat the request itself as a human one. Early check-in and late check-out depend on the turnover, so this is exactly the message that should not be automated — an automatic yes is a promise your cleaner may not be able to keep, and an automatic no gives away goodwill you could have had for nothing.

What arrival friction costs you

Two things, neither of them obvious from the inbox.

The first is the review. Guests write reviews roughly in narrative order, and arrival is the opening scene. A stay that went well but started with twenty minutes of confusion at the door often gets a review whose first paragraph is about the door. Nothing later in the stay fully overwrites it.

It's also the window where reply speed genuinely matters — one of the few where it does.

The second is the rest of the stay's message volume. A guest whose arrival was smooth tends to trust the house information they were given and consult it. A guest whose arrival went wrong has learned that the written material can't be relied on, and messages you about everything for the next four days.

Common questions

When should I send check-in instructions?

The day before arrival, with the door code repeated on the morning of. Booking-time messages are read too early to stick.

What should be in a check-in message?

Address plus what the place looks like, parking, entry code or key, and one line on what to do if it doesn't work. Photos for the door and the parking spot.

Should I allow early check-in?

Decide case by case — it depends on your turnover. Just don't automate the answer, and give early arrivals somewhere to wait either way.

Is self-check-in worse for reviews?

Not inherently. Guests overwhelmingly prefer letting themselves in. What hurts reviews is a self-check-in that's ambiguous — unclear parking, a lock with a knack, no fallback if the code fails.

How we handle this

This is the problem HiyaGuest was built for, so take the rest as interested rather than neutral.

We don't send your platform messages — the day-before message above is still yours to schedule. What we cover is the other half: the guest who is already inside and can't remember what they were told.

The Home Concierge shows the check-in and check-out times for the stay that's actually booked, pulled from your booking system rather than typed once and left to drift, and hosts can add their own screens for things like a gate code or the parking note. The Pocket Concierge gives each stay a private page the guest keeps on their phone, so the arrival details are still reachable on day three when the second car turns up and needs the same instructions.

Last updated August 2026. Written by the team at HiyaGuest, who make a guest concierge for short-term rentals — so the last section is a pitch, and the rest is what we'd tell a host who wasn't buying anything.