How to Reply to Reviews About Slow Service or Long Wait Times

"We waited forever." "Took three weeks to get a call back." "Sat in the lobby for an hour past my appointment." Complaints about waiting show up in reviews for almost every kind of local business, and they're tricky to answer. The wait already happened, the customer is annoyed, and the real reason (short staffing, a rush, an emergency patient) can sound like an excuse. Here's how to reply in a way that respects the customer's time and reassures the people reading.

Why wait-time reviews matter more than they look

Time is the thing people can't get back. A cold dish can be remade. A lost afternoon can't. That's why these reviews often feel angrier than the problem seems to deserve, and why a brush-off reply lands badly.

Readers use them to set expectations. Someone deciding whether to book with you will read "long wait" reviews and your replies to judge whether it's a pattern or a bad day. Your reply is the one place you get to answer that question.

They're usually specific and fixable. "Only one person at the counter on a Saturday" is operational feedback you'd otherwise pay a consultant to tell you.

A simple structure: own it, explain briefly, say what changes, invite back

Acknowledge the wait in plain words. "You waited too long for your food" is better than "we're sorry for any inconvenience." Use their details if they gave them.
Explain in one sentence, or not at all. A short, true reason can help ("we were down two staff that evening"). A long one sounds defensive. Never blame the customer, other customers, or a named employee.
Say what's changing, only if it's true. Added a person on weekends, started texting patients when the doctor is running behind, changed how call-backs are tracked. If nothing has changed yet, say you've shared it with the team.
Invite them back or offline. Give a real contact: a phone number, an email, or a manager's name. Don't promise a freebie in public.

Keep it to three to five sentences. Long replies to short complaints read like arguments.

Examples you can adapt

Restaurant, long wait for food:

Hi Dana, thank you for telling us, and I'm sorry you waited so long for your meal on Friday. We were short in the kitchen that night, and that's on us, not you. We've since added a second line cook on weekend evenings. If you'd give us another try, ask for me (Marco, the manager) and I'll look after your table.

Medical or dental office, appointment running late:

Thank you for your feedback, and we're sorry you waited well past your appointment time. Delays sometimes happen when an earlier visit runs long, but you should have been told what was going on. Our front desk now updates patients in the waiting room when we're running more than 15 minutes behind. Please call our office manager at (555) 010-2040 if you'd like to talk about your visit.

(Health practices: never confirm in a public reply that the reviewer is a patient or mention anything about their care. Keep it general, as above.)

Home service or contractor, slow to call back:

Hi James, you're right that it took us too long to get back to you about your estimate, and I'm sorry. We missed your message during a very busy week, which isn't a good enough reason. We've changed how we track incoming requests so nothing sits for more than one business day. If you still need the work done, I'd be glad to call you directly; you can reach me at [email protected].

Retail or counter service, long line:

Thanks for the honest review, Priya. Saturday lunch is our busiest time, and one register clearly wasn't enough. We've started opening a second register from 11 to 2 on weekends. We hope your next visit is a lot quicker.

What to avoid

Arguing with the timeline. "Our records show you waited 20 minutes, not 45" may be accurate, but it makes you look petty to everyone reading. If the numbers matter, discuss them privately.
Blaming staff by name. Naming an employee in public is unfair to them and rarely helps you. See our guide on replying to reviews that mention an employee.
Excuse stacking. "We were busy, two people called in sick, and the system went down" reads as a list of reasons it wasn't your fault. Pick one true reason, or skip the reason.
Promising what you can't keep. "This will never happen again" invites the next reviewer to prove you wrong. Describe the actual change instead.
Offering refunds or discounts publicly. It can look like you're paying for a better review and encourage copycat complaints. Make offers privately.
Copy-pasting the same reply. If five reviews mention waiting and all get identical replies, readers notice. Vary the wording and reference each person's details.

When wait complaints are a pattern

One review about a long wait is a bad day. Several in a month is a signal. Before you reply, look for what they have in common: the same day of the week, the same time slot, the same service. Fix that first if you can, then mention the fix in your replies. A reply that says "we've added staff on Saturday mornings" is far more convincing when three reviewers all mentioned Saturday mornings.

It's also worth replying to the good reviews that mention speed ("in and out in 20 minutes!"). Thanking those customers shows readers that quick service is the norm, not the exception. Our guide to replying to positive reviews has examples.

Short on time to reply yourself?

Ironically, slow replies to slow-service reviews make the problem look worse. If reviews are piling up, ReplyRight writes personalized, on-brand replies to your Google reviews for you to approve and post. You can also start with our free guide to responding to a negative Google review.