Host not responding and you land tomorrow: an hour-by-hour plan for the check-in that never happens

Your flight is tomorrow morning. Two days ago you sent a polite message asking for the check-in instructions, and the app still shows it as unread. The listing page has an address but no door code, no key box, no arrival time. You call the number you have; it rings out. You start doing the thing everyone does at this point — refreshing the chat, telling yourself the host is probably busy, and quietly hoping it sorts itself out while you pack.

It rarely sorts itself out, and hoping is the move that costs you money. A host not responding is not a small admin problem to be solved on arrival: it is the early warning for a booking that may not exist, and everything that protects you — the record, the refund, the affordable replacement booking — gets harder to arrange the closer you are to the door. This guide is the hourly plan: what to write down, how long to wait at each stage, when to book somewhere else, and how not to pay for two beds. It is general information, not legal advice, and nobody can promise you an outcome.

Two kinds of silence from a host

A host not responding describes two very different emergencies, and treating them the same is what leaves travellers stranded.

Silence from a host before you travel is the cheap kind. Nothing has failed yet. You still have a working phone, daylight, and a market of other places to sleep at ordinary prices. Every hour you wait for the host is an hour of that cheap choice burning away. The goal here is not to be rescued; it is to force an answer early enough that a calm replacement booking is still affordable.

Silence from a host on the doorstep is the expensive kind. You are tired, standing beside your luggage, possibly in the dark, and the nearby rooms are priced for someone with no choices. The goal changes: you are not trying to save the booking, you are trying to get a bed tonight while building a clean record that the host never delivered the stay.

Almost every mistake in these cases comes from running the second protocol in the first situation — waiting patiently, giving the host the benefit of the doubt, right up until the moment when patience stops being free.

That traveller's second problem is what decides the cost: the area was booked out for a concert, so the rooms still available were far above their budget. That is the pattern to watch. The damage from a host not responding is rarely the booking itself — it is what the replacement booking costs on the day you have no time left.

The pre-arrival clock: chasing the check-in instructions

Here is the timetable for a host who has gone quiet before the trip. The dates are guides, not rules: compress them where rooms sell out, stretch them if check-in is still weeks away.

Two rows in that table do most of the work. The first is the second message with a deadline — something as plain as "if I don't have the check-in instructions by Thursday evening I'll ask the platform to step in, since I fly on Friday." It is polite, it is dated, and it turns vague silence into a documented refusal. The second is opening the platform conversation early. A support agent reading "my booking is in four days and I have no way to get in" still has time to chase the host — and time is the only thing support can really spend on your behalf.

Read the newest reviews before you travel, not after. One review describing the same locked door and the same silent host turns your worry into evidence of a pattern, and a pattern is what makes a support agent act before your trip rather than in the middle of it.

The doorstep protocol when nobody opens

Now the second kind of silence: you are there, the host is not, and no code works. This is where people lose money by improvising. Work through the rungs below in order, and stop the moment you have a bed and a record.

The thirty-minute mark in step three is worth memorising. It is long enough to be fair to a host stuck in traffic, and short enough that support is handling a problem rather than a disaster. Guests who wait longer tend to open the case from a bar, exhausted, once the affordable rooms have gone.

Booking a replacement without paying for two beds

The fear that keeps travellers frozen is sensible: book somewhere else and you might be holding two bills for the same night's stay. There is an order that keeps that risk small.

• Report the host before you rebook. The complaint goes first, even if it is a single line in the platform's chat. A replacement booking made before anyone was told reads as your own change of plan; the same booking made twenty minutes after a logged report about the host reads as a cost the failure forced on you.
• Never cancel the original booking yourself while it can still be saved. This is the expensive mistake. When you press cancel, the rate's cancellation policy decides what comes back — and on a strict rate that can be nothing. When the platform cancels because the host could not deliver the stay, you are in a different situation entirely, built around a refund rather than a policy. If cancelling is the only way forward, get the platform to say in the chat what you will be refunded, then act.
• Choose a refundable rate for the backup, even at a small premium. Paying a few units more for a room you can cancel for free is the cheapest thing in this whole guide. If the host surfaces at ten in the evening with a working door code, you keep the option to use the stay you already paid for.
• Keep the replacement booking proportionate. A comparable room in a comparable area is a reasonable cost. A suite twice the size, booked out of frustration, is a harder number to defend, and nobody owes you an upgrade because a host went quiet.
• Keep both confirmations and the price gap in a single place. The figure you will eventually ask for is usually simple: the money you paid for a stay you did not get, plus the difference between the two bookings, plus any transport the change forced on you. A screenshot of each, saved that night, is enough.

If the replacement booking genuinely cost far more because you were in a city during a concert or a holiday weekend, say so plainly, with both prices. That is a checkable fact, and exactly the kind of foreseeable cost a failed booking creates.

What the platforms' own rules say about a silent host

You do not need to quote anything at anyone, but knowing where you stand changes how the conversation with a silent host feels.

On Airbnb, the terms are clear that a confirmed booking creates a contract for the stay directly between you and the host: the platform arranges the booking, the host has to deliver the stay. The terms also point to a rebooking and refund policy for homes that covers exactly this shape of problem: if the host cancels, or something disrupts the stay in a way the policy treats as a reservation issue, you may be eligible for rebooking help or a partial or full refund. A confirmed booking with no way to get in is the plainest example there is. That policy is built around reporting the problem promptly, which is the practical reason to open the case while you are standing outside rather than a week later at home.

Airbnb's off-platform policy is worth a moment here too, because it forbids things that show up in the middle of these situations: a host may not push the payment for a booking off the platform, and may not require you to install a separate app or create another account simply to get into the property. If a silent host resurfaces with "send the money to this account and I'll send the code," that is not a rescue. It is a separate problem.

On Booking.com, the equivalent promise is blunter. Its own rules say that once a booking is confirmed the property must honour it, and if it cannot, you cancel at no cost, get the money back, and get help finding a comparable place at a comparable price — with the difference covered where the replacement booking costs more (§1L). That line, along with the other clauses that put money back on the table, is decoded in our guide to the money-back clauses.

Behind both sits the ordinary consumer protection of the place you live: a service you paid for should actually be provided, and a booking whose door never opened was not provided at all. Those everyday rules were never any platform's or host's to switch off, and they are why "the rate was non-refundable" is not an answer to a room you were never let into. The European Consumer Centres publish plain-language summaries country by country if you want to read further in your own language.

When the silence is not a red flag

An honest guide has to include the cases where the host did nothing wrong, because an angry message into one of those wastes goodwill you may need later.

Plenty of small properties simply have nobody to answer the phone at night. A twenty-five-room independent hotel cannot pay someone to sit by the phone until morning, and many apartments are run by a host with a day job. That is not neglect; it is arithmetic.

So before you assume the worst, check the boring explanations. Are you messaging the host outside the platform's chat, where a notification may never arrive? Are the check-in instructions sitting in an email you have not opened, or under a tab in the app you never scrolled to? Is it the middle of the night where the host lives? Did you book a place with automated self check-in, where nobody was ever going to greet you and the door code arrives the day before by email? Silence at eleven at night with a working code is an inconvenience. Silence with no code is the problem this guide is about.

There is a broader shift worth naming here, because it changes what "someone will be there" means.

Keyless, staffless stays are now normal, and they work well right up to the moment something is wrong — at which point there is no desk to stand at and nobody to hand you a spare key. The response is not to avoid them but to treat the check-in instructions as the thing that must exist before you travel. If a listing has no reception, the door code is the reception. Ask the host for it early, in writing, and treat its absence seriously.

How long should I wait before I decide the host isn't coming?

Before the trip, give a written message a full day, then treat a second day of silence as your answer and start the platform conversation. On the doorstep the clock is much shorter: try every contact route you have, wait around thirty minutes, and if there is still nobody and no working code, open a case with the platform then and there rather than after a cold hour on the pavement.

The address that changes at the last minute

This variation deserves its own paragraph, because it looks like a small administrative fix and sometimes is not. A day before arrival, a previously silent host writes with a different address from the address on the booking — a different street, sometimes a different neighbourhood.

Sometimes there is a dull, true explanation: a building with two entrances, a numbering quirk, a second identical unit. But the change matters, so handle it in the app rather than by private message. Ask the host to confirm the new address in the platform's own chat, ask why it changed, and compare the photos of the new place with the listing you booked. Being moved to a smaller or worse property at the last minute is not a formality — it is a different stay from the one you paid for, and it is fair to say so calmly and ask the platform to look at it before you travel. If the answer is vague, or the new address turns out to be a different type of building altogether, that is a case for the platform, not a detail to sort out on the doorstep with your luggage.

The same rule applies to any last-minute change that moves you off the platform: a request to pay in cash, to message on another app, to collect keys from a shop. None of that is automatically dishonest, but all of it removes the record you may need, and the record is the whole of your protection.

Support offers to cancel the booking for me. Should I say yes?

Usually yes, but ask two questions first, in writing: what exactly comes back, and what help you get finding somewhere else. A cancellation the platform makes because the host went quiet is not the same as you cancelling — yours can be judged against the rate's cancellation policy, theirs is the platform recording that the stay was not delivered. Get that difference stated in the chat before you agree, and keep the message.

What to keep, and how to write the refund request

Everything above produces the same small pile of evidence. Gather it while it is easy — most of it stops existing once you have moved on and the host has edited the listing.

• The booking confirmation with the reference number, the address as booked, the dates and the total paid.
• A screenshot of the listing page showing what was promised — including, if that is the case, the empty space where check-in instructions should be.
• The message thread with the host, timestamps visible, showing when you asked and how long the silence lasted.
• Call logs, if you tried the phone. A list of outgoing calls is quietly convincing.
• Photos from the door: the entrance, the street number, the locked key box, and the clock.
• The replacement booking and its receipt, plus any transport the change forced on you.
• The support case reference and a copy of what the platform told you about the booking.

The refund request itself is short and should stay unemotional. Say what you booked and paid. Say what happened, with dates. Say what it cost you. Then name a clear figure and what it is made of — the stay you did not get, the price difference on the replacement booking, the taxi. That is the whole refund request. Building it from your own notes, in the right order and without heat, is exactly the part we made 2refund for: it turns your answers into a clear request that's yours to send.

Can I book a backup place and still get the first booking refunded?

Often, yes — the order is what makes it work. Report the problem first so it is on the record, then book the replacement, and keep the booking you already paid for open until the platform confirms what happens to it. Choose a free-cancellation rate for the backup where you can, so if the original stay is suddenly rescued you are not left holding two bills.

If the money still does not come back

Most of these cases end with the platform, because a booking that plainly never opened its door is not a comfortable thing to defend. When it does not end there, two ordinary routes remain, and neither is dramatic.

If you paid by card, a stay you never received is the sort of thing a chargeback exists for: you ask your bank to review the charge, showing the confirmation, the dated report and the evidence that no service was provided. It works best after you have given the property and the platform a fair chance in writing — the record you built at the door is the same record the bank will read.

Beyond that, the small-claims route that exists for everyday disputes is a real option for a sum worth the effort, and it is designed to be used without a lawyer. It is slow and rarely necessary. The point is that the conversation does not end when a host stops replying.

The host answered an hour before check-in. Is my case gone?

Not gone, but smaller. If the stay then went ahead normally, there is rarely money in it — inconvenience on its own is thin ground. If the late answer forced real spending you cannot undo, like a refundable backup you had to pay for or a taxi across town, those specific costs are still a fair thing to raise with the platform, with the receipts and the message timestamps attached.

Silence from a host is information. Treated as an administrative gap to be sorted out on arrival, it turns into a night on a pavement and a bill for two rooms. Treated as a countdown — a dated message, an early support case, a refundable backup — it usually turns into a stay somewhere else and money that comes back, because at every step you were holding the record of what the host promised and of the moment nobody delivered it.

The cases in this article are illustrative composites, not real client records. We build them from the patterns we see again and again across the disputes we help with, because we can’t share real customers’ booking details. The stories are invented; the way they play out is true to our experience.

This article is general information, not legal advice. We’re a self-help tool, not a law firm. Rules, fees and deadlines change and vary by country, so always check the policy attached to your own booking and your local consumer protections.