Why waiting complaints deserve a real answer
A good wait time review response matters because waiting is concrete: a customer knows exactly how long they stood in line, and a vague apology reads as not listening. Waits are also usually caused by staffing or process at specific times, which means the reply can often describe a real change.
The structure
- Apologise for the specific wait.
- Give a short reason if it helps, without excuses.
- Say what is changing.
- Invite them back.
Examples
"We're sorry, a 30-minute wait to pay is too long. Weekend evenings have been our busiest, and we've added a second billing counter from 5 pm. We hope your next visit is quicker. – [Name], Store Manager"
"We're sorry your food took 45 minutes. That's well beyond what we aim for. Large group orders slowed the kitchen that night, and we're changing how we pace them at peak times. – [Name], Manager"
"We apologise for the wait at check-in. Friday afternoons are our busiest, and we've added a second desk and online check-in. – [Name], Front Office Manager"
"Sorry your order arrived 40 minutes late. We're reviewing our delivery radius at peak times. Please write to [email] so we can make it right."
What to avoid
- "We were very busy." Customers know; it is not an explanation.
- Blaming other customers or a single staff member.
- Promising a time you cannot guarantee.
Finding the pattern
Reviews often mention when the wait happened: "Saturday evening", "lunch rush", "Friday check-in". Tag those times. Waiting complaints usually cluster at a few predictable peaks and at a few stores; the fix is staffing or process at those times and places.
Wait time complaints across locations.
Wait time complaints across locationsFree review snapshot
Want this done for your own reviews?
No commitment. We use your details only to send your snapshot and follow up. Privacy policy
An example
A retailer tags billing-wait complaints by time mentioned. Most are on weekend evenings at 15 mall stores. A mobile billing point during those hours brings wait complaints down at those stores over the next month, while the weekday picture stays the same.
Common mistakes
- Generic apologies that ignore the wait time the customer gave.
- Fixing the wrong peak.
- Never checking whether complaints fell.
Common questions
Should we explain why it was busy?
Briefly, if it helps the customer understand; never as the whole reply.
Should we compensate for long waits?
Decide privately; never conditional on changing a review.
How do we stop waits in the first place?
Staff to peaks, add counters or self-service at busy times, and communicate delays.
Do customers accept some waiting?
Often, when they are told how long and why. Silence is what turns waits into reviews.
Checklist
- The wait named.
- A real change described.
- No blame or excuses.
- Time and store tagged for analysis.
In short
Name the wait, explain briefly, say what is changing, and tag the time and store so the peaks behind waiting complaints can be fixed.
Communicate waits before they become reviews
Many waiting complaints are about not knowing how long. A greeter who says "about ten minutes", a message when a table or order is running late, or a sign at the billing counter during peaks turns silent frustration into managed expectation.
Doing this with Falcon
Falcon's CRM is where a team handles replies across stores. For each review it suggests an owner from your taxonomy, drafts a reply from the playbook for the review's theme and sentiment, and checks the draft before it is saved: is it long enough to sound personal, does it contain a phone number or email, does it promise compensation that needs a manager's approval, and does it fit the channel's length. Reviews can be assigned, escalated and tracked to done. The reply itself is posted in Google Business Profile.