The short answer
To respond to a review about a long wait, apologize for the specific delay and its impact (a missed lunch break, a cold meal, a day off work wasted), explain the cause in one sentence only if it helps, and name what you have changed so it is less likely to happen again. If the wait was outside your control, still own the communication. Silence during a wait is what customers resent most.
- Customers forgive delays more easily than being left uninformed. Most wait reviews are really communication reviews.
- Acknowledge the cost to them in time: a lunch break, a day off, a babysitter.
- One sentence of explanation, maximum. More sounds like an excuse.
- Repeated wait complaints are a scheduling or staffing signal. Count them.
What a wait-time review is really about
"Waited 45 minutes" rarely means the customer timed it with a stopwatch. It means the wait felt longer than it should have and nobody made it feel okay. Two customers can wait the same 30 minutes and leave very different reviews depending on whether someone said "the kitchen is backed up, your food is about ten minutes away" or simply disappeared.
That shapes the reply. If you only apologize for the minutes, you miss the part that made them angry. The best wait-time replies name both: the delay itself, and the lack of an update, an estimate or an apology at the time.
| Business | Typical wait complaint | What usually helps |
|---|---|---|
| Restaurants and cafes | Slow mains, long waits for a table or the bill | Table check-ins, honest quote times at the door |
| Clinics and dentists | Running late past the appointment time | Telling patients on arrival how far behind you are |
| Trades and home services | Technician arrived late or outside the window | Text updates when the previous job runs over |
| Auto repair | Car kept days longer than quoted | A call the moment a part or diagnosis delays the job |
| Retail and pharmacies | Long checkout or pickup queues | Opening another till, a separate pickup line |
| Phone and email support | Slow callbacks or replies | Auto-acknowledgement with a realistic reply time |
How to answer a wait-time complaint
Check what happened that day
Look at the schedule, booking system or order times. Was it a one-off (a staff member off sick, a rush) or the usual Friday? This decides whether you describe a fix or a change of process.
Apologize for the impact, not just the minutes
"We're sorry you spent most of your lunch break waiting" lands harder than "sorry for the wait" because it shows you understand what it cost them.
Own the communication gap
Even when the delay wasn't preventable, not telling them usually was. Say so.
Name one change
A second chef on Saturdays, text alerts when appointments run late, a revised delivery window. Something a reader could picture.
Leave a route back
Invite them to return, or give a contact if the wait caused a real loss (a missed appointment, a ruined event).
Example replies to long-wait reviews
Slow food on a busy night (restaurant)
Waited over an hour for two burgers. Place was packed and understaffed. Food was fine when it came but we were starving.
We're sorry, an hour for two burgers is far too long, and being hungry and left wondering made it worse. Saturday was busier than we planned for. We've added another cook to weekend evenings and asked servers to give an honest time estimate when the kitchen is behind. We'd love to feed you faster next time.
Doctor running very late (medical clinic)
Appointment was at 2pm, wasn't seen until 3:20. No one said anything. I had to leave work for this.
We're very sorry. Waiting over an hour without any update is frustrating, especially when you've taken time off work. We've started telling everyone at check-in if the schedule is running behind and how long the wait is likely to be, with the option to rebook. Please contact our practice manager at [phone] if you'd like to discuss this further.
Contractor missed the arrival window (electrician)
Told me 8-10am. Showed up at 1pm. I took the morning off for nothing.
We're sorry you lost your morning. That's exactly what an arrival window is supposed to prevent. The job before yours ran long, and we should have called you as soon as we knew. We now text customers the moment a technician is running behind. Please call [phone] so we can talk about what we can do to make up for it.
Repair took much longer than quoted (auto repair)
Said 2 days, took 9. Had to keep calling them for updates.
We're sorry. Nine days instead of two is a big disruption, and you shouldn't have had to chase us. A part we ordered was back-ordered, and we should have told you immediately and offered a loan car or alternative. We've changed our process so the service advisor calls whenever an estimate changes.
Long queue at peak time (coffee shop)
Coffee is great but the morning line is ridiculous. 20 minutes for a latte isn't sustainable on a workday.
Thanks for sticking with us, and for the kind words about the coffee. You're right that 20 minutes is too long at rush hour. We've added mobile ordering for pickup so you can skip the line, and a second barista from 7:30 to 9.
Slow delivery (furniture retailer)
Ordered a dining table with 3-week delivery. It's been 7 weeks and every call I get a different answer.
We're sorry. Seven weeks with no clear answer isn't okay, and the mixed messages make it worse. We'd like one person to own your order from here: please email [email] with your order number and our delivery coordinator, Priya, will give you a confirmed date and keep you updated until it arrives.
Hold time on the phone (insurance agency)
Spent 50 minutes on hold. Gave up. Terrible customer service.
We're sorry you spent nearly an hour on hold. That's not acceptable. We've added a callback option so you no longer have to wait on the line, and you can also reach us by email at [email], where we reply within one business day.
Great visit, slow check-in (hotel)
Loved the room and the pool. Check-in took forever though, only one person at the desk.
Thank you, we're glad you loved the room and the pool! Sorry about the check-in wait. We now have two people at the desk during the afternoon arrival rush. Hope to welcome you back quickly next time.
Wait that wasn't the business's fault (restaurant during a power cut)
Waited 40 minutes for food and then were told the kitchen had shut. Shambles.
We're really sorry. A power cut hit the kitchen mid-service that night, and we should have told every table straight away instead of letting people wait. That's on us. Please get in touch at [email]; we'd like to invite you back for the meal you didn't get.
- Slow food on a busy night (restaurant): One sentence of cause, then two concrete changes. The reader sees a business that adjusted, not one making excuses.
- Doctor running very late (medical clinic): Doesn't confirm any medical details. The change (telling patients at check-in) directly addresses 'no one said anything'.
- Contractor missed the arrival window (electrician): Owns the missed call, not just the late arrival. The offer to 'make up for it' is handled privately.
- Repair took much longer than quoted (auto repair): A delay outside your control (parts) becomes a chance to show you've fixed the part you did control (updates).
- Long queue at peak time (coffee shop): Light, practical, and it gives every reader a workaround.
- Slow delivery (furniture retailer): When the wait is still ongoing, the reply's job is to fix it, not explain it. One named owner solves 'a different answer every call'.
- Hold time on the phone (insurance agency): Offers alternatives that work for anyone reading, not just the reviewer.
- Great visit, slow check-in (hotel): On a 4-star, keep the apology proportionate. A short acknowledgement and a fix is enough.
- Wait that wasn't the business's fault (restaurant during a power cut): The outage wasn't their fault, but the 40 minutes of silence was. Owning that part keeps the reply credible.
When the delay genuinely wasn't your fault
Weather, a supplier, a power cut, an emergency patient who needed the doctor first. Some waits are outside your control, and it is tempting to say so firmly. Resist that. Readers are not judging the cause; they are judging how you handled it. A reply that leads with "this was not our fault" loses them, even when it's true.
Instead, state the cause in a neutral half-sentence and move straight to what you could control: telling people, offering to rebook, adjusting the bill. In healthcare, avoid even hinting at another patient's emergency. "An unexpected delay in the clinic" is enough.
Long-wait reply template
Change the bracketed impact every time; it is the part that makes the reply sound human. You can also start from the AI reply generator, which will pick up the wait time and context from the review.
Do and don't
Do
- Repeat the wait or delay they described, so they know you read it.
- Recognize what the wait cost them.
- Mention practical alternatives (booking, callbacks, mobile ordering) that help other readers.
- Track wait-time complaints by day and location.
Don't
- Dispute the number of minutes they claim to have waited.
- Blame "unprecedented demand" or other customers.
- Promise faster service you can't staff for.
- Mention another patient's emergency or another customer's problem.
Replying faster than you served
There is an irony in taking two weeks to reply to a review about slow service. Responsly drafts a reply as soon as a review syncs, and low-rating alerts flag 1 and 2-star reviews in the app and your browser so they don't sit unanswered. Multi-location businesses can filter by branch to see which site keeps drawing wait complaints; see multi-location reputation management for how that works.