Your complaint has gone quiet: what a stalled case actually needs

You did it properly. You reported the problem while you were still there, you put the complaint in writing, you attached the photos and the booking number, and you asked for something reasonable. The first answer was a friendly template that didn't mention a single thing you'd written. Your second email got no answer at all. That was three weeks ago, and the case has simply stopped moving. It's very easy to read that silence as a decision — a quiet no you're expected to accept.

It usually isn't. A stalled complaint is rarely a refused complaint. Far more often the case has lost its shape: it's spread over a phone call, two chat windows and three email addresses, no agent's name is on it, no amount was ever named, and no date was ever set — so there is nothing for anyone to be late for. This guide is about the step between "I complained" and "I gave up": how long to wait, what a polite follow-up email with a deadline looks like, how to fold forty messages into one written record, why the first line of customer support answers in templates, and why the silence itself ends up being useful to you. It's general information to help you decide what to do next, not legal advice.

Why a strong complaint goes quiet

Being ignored feels personal. Almost always the reason the case stopped is mechanical, and the four ordinary ones are worth knowing, because each has a different fix.

• The complaint was passed to the property rather than answered. The platforms are open about this. Booking.com's terms say it may pass messages between you and the property, and that the stay itself is the property's responsibility (A17). Its rules for accommodation partners go further: a complaint about the room or the service must be resolved by the property, and Booking says it will always give the property the chance to resolve the complaint first (2_5_5). So "we've contacted the property for you" is not a brush-off — it's the platform doing a step it has written down. It just leaves the case waiting on the one party with a reason to stay quiet.
• Nothing you sent was ever due. "This wasn't acceptable and I'd like it looked at" is a feeling, not a task. Nobody can be late answering it, so the case sinks. The complaint that names an amount and a date creates something a queue can be behind on.
• The case is scattered. A call on Tuesday, a chat on Thursday, an email on Sunday and a review left in between are four separate objects. Whoever picks up the case sees a fragment, answers the fragment, and closes the ticket.
• Nobody owns the case. Customer support answers, closes the ticket, and your reply opens a new one with a new agent who starts from zero. The property, meanwhile, assumes the platform is handling the complaint. The clock resets each time, which is why the case can be six weeks old and one day old at once.

Read that as information rather than an insult. The case did move — it went to the party the platform's own rules put first. What the complaint lacked was a date to come back on, and a copy sitting with customer support that stayed open while the property thought about it.

How long before a complaint counts as stalled

Nobody owes the case a fixed deadline, and a small family-run property answers more slowly than a chain. But there are ordinary expectations, and once a wait passes them you can stop wondering and treat the complaint as stalled.

How long should I wait before I send a follow-up email?

About three working days for a property, and a couple of days for customer support — then send one follow-up email on the same thread with a date in it. After that, a message a week is plenty. Daily chasing feels productive and does the opposite: it splits the complaint across a dozen half-read messages and makes it easy to file you as noise rather than as a stalled complaint waiting for an answer.

One case file instead of forty messages

This is the single most useful thing you can do for the complaint, and it takes twenty minutes. Stop adding messages to the pile and write the case once, on one page, in the order it happened. Everything that comes afterwards — the follow-up email, the complaint to the platform, a consumer body, a bank — is that same page with a different first line.

A written record that works holds six things:

• The booking reference, the property name and the dates. First line, before anything else, so nobody has to search for the case.
• What you booked against what you got. Two sentences, no adjectives you can't prove. "The listing showed a studio with a sofa bed for four people. There were no linens for the sofa bed and none could be provided that night."
• A dated timeline of contact. Every message, call and reply with its date: what you asked, what came back, and the gaps where nothing came back at all.
• The proof, named and numbered. Photos with the day they were taken, the listing screenshot as it looked when you booked, the confirmation, the receipts for anything the failure cost you.
• The outcome you want, as a figure. "A refund of £210, being two of the four nights" — not "some compensation for the trouble".
• A date by which you'd like an answer. A single line, calm, at the end.

You don't have to guess at that shape, because the platforms publish it. Booking.com's guidance on what to send when something goes wrong asks for exactly this: the confirmation number, your contact details, a summary of the issue, the resolution you're looking for, and supporting documents such as pictures, receipts and statements — and it says every query and complaint is recorded identifiably, so the status of the case can be tracked (A16). The case file built that way isn't extra paperwork. It's the version of the case that customer support can act on without asking you anything.

Two detailed emails often weaken the case rather than strengthen it: detail spread across two messages is detail nobody has read in one sitting. The same facts on one page, with a figure at the bottom, land completely differently.

I sorted most of this out by phone. Does that count?

Only if you write it down afterwards. A call leaves nothing in the written record — nothing for the next agent, a consumer body or your bank to read. The fix takes two minutes: reply on your email thread with "To confirm our call today at 14:10: you said the refund of €180 was approved and would be sent this week." If nobody corrects that summary, it becomes part of the case.

What a polite follow-up email with a date looks like

A follow-up email is not an angry email. It's deliberately boring, and its whole job is to turn the complaint from an open-ended grievance into something with an edge. The tone stays warm; the structure does the work.

The parts, in order:

1. A subject line with the reference in it — "Booking 4231 8890 · unresolved refund request · follow-up 2".
2. One sentence of context — the dates, the property, and that you're writing again about the case.
3. Three lines of timeline — when you complained, what you were told, and what has happened since (often: nothing).
4. The ask, as a figure — the amount, and what it's made of.
5. A date — "I'd be grateful for an answer by 9 September."
6. The calm next line — what you'll do if that date passes, stated as fact rather than as a threat.
7. The attachments, listed — so nobody has to ask for them.

Two of those are worth dwelling on, because they're where most follow-up emails go soft.

The figure. A named amount turns the complaint into a decision someone is allowed to make. Customer support agents usually have a limit they can approve without asking anyone; "some kind of goodwill" fits nobody's limit, while "£210" either fits or goes to someone whose limit it does fit. Keep the figure proportionate to what actually failed — two ruined nights out of four, not the whole stay — because an amount that matches the facts is the hardest kind to argue with.

The date and the line after it. "If I haven't heard back by 9 September, I'll take the complaint to the platform's complaint channel and, if needed, ask my bank to review the charge." That sentence is not a threat; it's a schedule. You're naming ordinary steps that already exist and that you'd genuinely take. It works precisely because it's undramatic — and because it's true. Never name a step you don't intend to use.

Writing that first clear message from a blank page is the part most people put off for weeks, and it's the part we can take off your hands: 2refund turns your answers into a clear request that's yours to send, with the timeline and the amount already in it.

Customer support's first line is a script — and often a bot

It helps to picture what's on the other side. The first layer of customer support on a big platform is built for volume: automated replies, keyword matching, and agents working from short scripts with a small approval limit. It's very good at closing simple complaints and genuinely poor at reading the case behind a complicated stay. That isn't a conspiracy against you, but it does explain the two experiences everyone recognises — an answer that addresses a sentence you never wrote, and a "senior team" whose reply looks exactly like the first.

A few habits make a scripted first line much easier to get past:

• Ask for the case reference number and quote it in every message afterwards. A case with a number can be looked up; without one, the complaint is re-created from scratch by whoever answers next.
• Stay in one written channel. Pick the platform's message thread or email and keep the case there. If you have to call, write the summary afterwards — the call itself adds nothing to the case.
• Ask closed questions. "Please confirm in writing whether the refund of $120 has been approved — yes or no — and the date it will be sent." A template can absorb a paragraph of frustration; it cannot answer a yes-or-no question without saying something.
• Quote what their own side already told you. When one agent has promised something in writing and a second contradicts it, put the first message's date and wording in front of them. A contradiction inside their own record moves the complaint further than your disappointment can.
• Name the specific gap, not the mood. "The listing said two beds; the second bed was unusable" is checkable. "The place was a disgrace" is not.
• Send one follow-up email per stage, not one a day. Volume dilutes the complaint; a single dated message with a case number concentrates the case.

Customer support told me there is no further step above them. Is that true?

Rarely. It's usually true of that one chat window, not of the case. Booking.com's own terms describe a complaint channel where every query is recorded and traceable (A16), and Airbnb's terms say plainly that you may ask customer service to review a decision it has made. Beyond the platform sit your national consumer body, a chargeback if you paid by card, and the small-claims route that exists for everyday disputes. One agent's script is not the end of the case.

Why silence becomes part of the case

Here's the part that changes how the complaint feels once it has stalled. Every unanswered message you sent is not wasted effort — it's the written record that makes the next step obvious to everyone who reads the case later.

Think about what a consumer body, a platform's senior team or a bank actually wants to see. Not outrage: a sequence. You complained promptly, you asked for something proportionate, you gave the property a fair chance and a reasonable date, and nothing came back. That sequence answers the first question each of them asks — "did this person give the seller a chance to put it right?" — before anyone reaches the merits of the case. Silence is what turns the complaint into a documented one.

It also matters inside the platforms' own rules. Booking says it will always give the property the opportunity to resolve the complaint; and where the property fails to resolve something material — facilities that don't match the description, a health or safety issue — Booking may compensate the guest or find alternative accommodation of an equal or better standard, and bill the property for it (2_5_5). Its plain-language summary of how it works adds that a property which gave an inaccurate description and didn't put it right can be removed from the platform (§1K). So the property that never answers you hasn't ended that process. It has finished the first step of the process — the step where the property had its chance.

And a party that stays silent has not disputed anything. When the case file says "on 14 August I asked for two nights back; no reply has been received", nobody has contradicted your version of events. That's an unusually strong position to be in, and it's the exact opposite of how being ignored feels while it's happening.

If a refund you were plainly owed still hasn't landed after all that, a chargeback is the honest continuation of a stalled complaint rather than a separate fight — and the card route works best in exactly these conditions: a real gap, a fair chance given, and a dated trail behind the case. Our companion guide on using the card route in good faith covers when a chargeback fits and when it doesn't.

When a quiet complaint really is a no

The honest other side, because a guide that says "keep pushing" about every case isn't much use. Sometimes silence really is the end of the story, and recognising that saves you weeks:

• The ask is bigger than the failure. A full refund for a stay you used, in a room that was disappointing rather than unusable, tends to be met with nothing at all — a property or a support agent would rather stop replying than argue. Scaling the request down to the part that genuinely failed often revives the complaint.
• A proportionate offer was already made. If they refunded the two bad nights and you're still asking for four, the complaint isn't stalled; it's answered. You can accept and close the case, or take the remaining part somewhere neutral, but more emails won't shift the property.
• You booked through someone else. If a third-party site holds the money, the property genuinely cannot refund what it never received, and the thread with the property will stay quiet however good the case is. That conversation belongs with whoever took the payment.
• The reporting window has genuinely passed. Both platforms weigh heavily on problems reported to the property during the stay, when they could still have been fixed. The complaint that first appears months later is a much harder case, and no amount of chasing changes that.
• The decision was made and just isn't being repeated. A clear written refusal is a decision on the complaint. The next move is outward — a consumer body, the card route, small claims — not another follow-up email to the same inbox.

None of this means dropping the case when the complaint is fair. It means spending your patience where it can still change something.

Restarting a stalled complaint, step by step

If you're reading this with a dead thread open in another tab, this is the order that gets the case moving again. Most revived complaints end at the second or third rung.

The short version

A stalled complaint almost never needs more words. The case needs shape: one thread instead of five, one page instead of forty messages, one amount instead of a feeling, and one date instead of an open ending. Send that to the property, once, politely — then let the calendar do the rest. If the answer still doesn't come, you haven't lost the case; you've finished the step everything after it depends on, and the silence you were dreading is now the clearest thing in the written record.

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.