Slow Service Review Response Template
Slow service complaints are among the most common review types for restaurants, cafes, and service businesses — and they're often written when a customer is still frustrated. The challenge is that "we were busy" is never a satisfying answer, and future customers reading your response know it. This template acknowledges the wait directly, takes ownership without over-explaining, and pivots to what you're doing about it. That combination — honesty + accountability — is the only thing that converts a frustrated reviewer into a return visit.
THE TEMPLATE
Ready to Copy
Copy, customize, and use it as-is — or make it your own.
Hi [REVIEWER NAME],
Thank you for your feedback — and we're sorry you had to wait. A wait like that is never acceptable, regardless of how busy we were, and we understand the frustration.
[OPTIONAL: We've [taken action: reviewed our staffing / adjusted our processes / spoken with the team] as a result of your feedback.]
We'd love the chance to show you a much better experience. Please reach out to us at [CONTACT] — we'd genuinely like to make it right.
[YOUR NAME]
[BUSINESS NAME]
TEMPLATE VARIATIONS
More Ways to Use It
Same structure, different tone. Pick the one that fits the situation.
Version 1 — Restaurant wait time (food delay)
Hi [REVIEWER NAME], we're really sorry about the wait for your food — that's not the experience we aim for and we hear you. A [X] minute wait for [dish] isn't right. We've spoken with our kitchen team about service times. If you're willing to give us another chance, please reach out — we'd love to change your experience.
Version 2 — Service business wait (appointment delay)
Hi [REVIEWER NAME], we sincerely apologise for keeping you waiting. Your time is valuable and we fell short on that. We've reviewed our scheduling process as a result. Please contact us at [CONTACT] — we'd like to make up for the inconvenience.
WHEN TO USE
Use for any review that mentions wait time, slow service, long queues, delayed food, or appointments running late. This is one of the most common complaint types across restaurants, cafes, healthcare, and service businesses. For more general negative review responses, see the negative review response template.
CUSTOMIZATION TIPS
Never say "we were short-staffed" or "it was an unusually busy night" — these are excuses that every reviewer has heard before and they don't reduce frustration. Acknowledge the wait, take ownership, describe action taken.
If you know the specific wait time from the review, acknowledge it specifically: "A 45-minute wait for a table is too long" reads as genuine accountability. Vague acknowledgements feel defensive.
"Regardless of how busy we were" is a powerful phrase — it proactively kills the "we were slammed" excuse before it's needed and signals real accountability.
For restaurants: consider whether a system change is worth mentioning (new kitchen workflow, added staff, reservation system updates) — concrete actions signal that the feedback produced real change.
How do I respond if the slow service was truly exceptional circumstances?
You can provide brief, honest context without making it an excuse: "On this particular evening, we were dealing with [brief context], which affected service times more than we would ever want." The key is that you acknowledge it as a valid complaint first, then provide context, and end with an invitation to return. Context as a trailing note lands better than context as an opening defence.
Should I offer compensation in the response?
Don't offer it publicly — it can look like you're buying the review and may encourage others to complain for the same reward. If you reach out privately (which your response invites), you can offer something there. The private resolution is more genuine and doesn't incentivise public negative reviews.
What if slow service is a recurring theme in our reviews?
Treat it as a product problem, not a PR problem. Multiple reviews mentioning the same issue signal a systemic issue — staffing, kitchen flow, booking system, or capacity management. Your response template handles the public perception; the actual fix requires operational change.
