How to Respond to a Review About Long Wait Times (10 Examples)
Across almost every local industry, waiting is the number one thing people complain about. Here's the reply structure that turns it into a strength.
Read enough negative reviews across restaurants, clinics, salons, garages and shops and one complaint appears more than any other: they waited.
It's also the complaint businesses answer worst, because there is almost always a genuine reason — someone called in sick, an earlier appointment overran, the kitchen got hit all at once — and explaining it feels like the honest thing to do.
It isn't. Here's why, and what works instead.
Why waiting makes people so angry
Research on queuing consistently finds that the felt length of a wait has less to do with the clock than with three other things: whether the wait was explained, whether it felt fair, and whether the person had anything to do.
Which means most wait complaints are not really about time. They're about being left in the dark. "We waited forty minutes" usually means "we waited forty minutes and nobody told us anything."
People forgive a long wait they were warned about. They don't forgive a short wait that nobody acknowledged.
That's the key to both the reply and the fix.
The structure
- Concede the number. Repeat their figure and agree it's too long. "Forty minutes is too long" is a far stronger opening than "we're sorry for any delay."
- One sentence of context — maximum. Any more and you are making excuses. Zero is also fine.
- Say what changed. This is the part that matters most to the next reader, and the part almost everyone omits.
- Invite them back with something concrete.
10 examples
1. Restaurant, food took too long
Forty-five minutes for mains is too long and I'm sorry. We were down a chef that night — an explanation, not an excuse. We've changed how we cover Saturdays since. Email me at [email] before you next come in and I'll look after your table.
2. Nobody acknowledged them while they waited
You're right, and the waiting is only half of it — being left without an update is the part that makes it worse. We've told the team that anyone waiting more than ten minutes gets spoken to, not ignored. Thank you for saying it plainly.
3. Appointment ran late
You booked a time and we didn't honour it. That's a fair criticism and I'm sorry. We've reduced how many appointments we take in that slot so it stops happening. If you'd like to rebook, ask for me directly on [phone].
4. Long wait on the phone
Sorry you were left holding — that's an easy way to lose someone and we should do better. We've added a callback option and a second person on the phones at peak times. If you still need help, [email] comes straight to me.
5. Waiting for a quote or callback
Chasing us for a quote shouldn't be part of the job. Sorry. We now confirm every enquiry the same day and send the quote within 48 hours — that came directly from feedback like yours. Happy to pick it up now if you're still interested: [phone].
6. Waiting for a repair or delivery
Three weeks with no update isn't acceptable, whatever the supply situation. I'm sorry. We've started sending a status message every Friday on open jobs so nobody's left guessing. Please email [email] with your job number and I'll check where yours is.
7. Queue at the counter
Sorry about the queue — the lunchtime rush caught us out. We've put a second till on between 12 and 2 since. Thanks for your patience, and sorry it was needed.
8. Waiting after checking in
Being checked in and then forgotten is the worst version of waiting, and I'm sorry. Anyone waiting more than fifteen minutes past their slot now gets an update from reception rather than being left. Thank you for telling us.
9. They mentioned the wait but still gave 4 stars
Thank you — and noted on the wait. Generous of you to give four stars given it. We're working on the [specific stage] that causes the bottleneck. Hope it's quicker next time.
10. When the wait was genuinely unavoidable
Sorry for the wait — we had an emergency case in that morning which pushed everything back. I know that's little comfort when it's your afternoon. We should have told you what was happening rather than leaving you wondering, and that part is on us.
Number ten is worth studying. Even when the delay was genuinely unavoidable, there is almost always a communication failure you can own. Owning that keeps you accountable without pretending you could have prevented an emergency.
What not to say
- "We were very busy." To a customer this reads as "we were making money from other people, so your time didn't matter."
- "Everyone had to wait." Fairness doesn't make a wait shorter.
- "It was only twenty minutes." Never dispute the number. Nobody has ever been argued out of how long something felt.
- "You should have booked." Blame, in public.
- Three sentences of staffing detail. Length reads as defensiveness — here's why.
When it's a pattern, fix the communication first
If waiting comes up repeatedly, you probably can't solve it by getting faster — most businesses are already going as fast as they can.
What you can almost always change is what happens during the wait:
- Tell people the realistic wait up front, and slightly over-estimate it
- Update anyone waiting past that estimate, before they have to ask
- Give a rough queue position where you can
- Make the waiting area not miserable
- Warn about known busy periods when they book
Businesses that do this see wait complaints fall sharply without actually getting any faster — because the complaint was never really about the minutes.
Reploi spots when the same complaint keeps recurring across your reviews and drafts replies that own it without making excuses. Start free — 5 replies/month →