"We Waited Too Long" — How to Reply to a Slow-Service Review

When to use this

When someone complains about the wait. This is the most common kind of bad review, and one of the easiest to answer well — readers generally understand busy, as long as you don't deflect.

The reply (copy it)

Bad review: long wait
[Name], I'm sorry we kept you waiting that long. That day was [honest reason, not an excuse] — but that's not something you should have had to absorb. We've since [specific change]. If you'll give us another go, mention this review and [what you'll do for them].

The most common mistake

Using "we were busy" as the reason. To the customer that isn't an explanation, it's an excuse — you should have been able to serve them when they showed up. You can describe what happened, but follow it with what you changed (more staff, new process, posting wait times). Otherwise you've admitted it will happen again.

When the situation is different

If it genuinely was unusual (equipment failure, someone called in sick), saying so helps — but be specific. "Our oven broke" is more credible than "we were short-staffed," because the first sounds like an accident and the second sounds like a normal Tuesday.

After you reply

If long waits are structural, no reply fixes it. What actually works is telling people in advance: post the wait at the door or mention it when they book. A wait you warned about doesn't become a review. An unannounced one does.

Replies for other review types
This is one of 12 review situations. The full set (filterable by star rating) is here:
See all 12 Google review replies →

Reviews, messages, email — you don't have to watch all of it

makupai reads your messages and email, works out what is urgent, and drafts the reply. You glance and hit send. 14-day free trial, no credit card.

14 days free No card needed 5-minute setup
Start free trial