Complaint and refund calls are the highest-stakes calls a restaurant takes and usually the least prepared for. They're also the clearest example of a call that should reach a person quickly. Whatever else you automate, this is the category where speed to a human matters more than efficiency.
The practical framework is short: get the caller to a person fast, give staff authority to resolve small things immediately, listen before solving, and log enough to spot patterns. Most of what goes wrong with these calls is delay and defensiveness, not the refund itself.
Why these calls carry more weight than their volume
A complaint call is a customer who is choosing to give you a chance to fix something instead of just leaving a review and never coming back. That's worth more than it feels like in the moment.
The outcomes fork sharply. Handled fast and generously, a complaint often produces a more loyal customer than a problem-free visit would have. Handled slowly or defensively, it produces a public review, a chargeback, and a permanently lost customer. The variance on these calls is enormous relative to their number, which is why they deserve disproportionate attention.
Get them to a person, fast
The first structural decision is routing. A caller who is already frustrated and has to navigate a menu, wait on hold, or explain the problem twice arrives angrier than they started.
Practical rules:
- Any caller who says they have a problem, wants a refund, or asks for a manager routes to a person immediately.
- No menu navigation for this path, and no repeating the story to a second person if you can avoid it.
- If no manager is available, the person who answers should be able to take the details, commit to a specific callback time, and then actually make it happen.
That last point is where most restaurants fail. A promised callback that doesn't come converts a fixable complaint into a review.
Where automation belongs and where it doesn't
Be honest about this. An automated agent should not be resolving complaints. It can't apologize sincerely, it can't judge how upset someone is, and a scripted response to a genuine grievance lands badly.
What it can do usefully:
- Recognize the intent quickly and route to a person without making the caller navigate anything.
- Answer during hours nobody is available, capture what happened and a callback number, and make sure it lands somewhere a manager sees it in the morning rather than in a voicemail box nobody checks.
- Handle the adjacent, non-emotional calls — order status, "my order is late" — before they become complaints. A lot of complaint volume is really information volume, and proactive status updates prevent it. See restaurant order status text updates.
If you're evaluating a phone system, test this specific path during the demo. Call in and say you have a problem with your order. What happens next tells you more about the system than any feature list. What to ask before buying an AI phone system covers the rest of the demo checklist.
Give staff authority to resolve small things
The most common cause of an escalating complaint is a staff member who wants to help and isn't allowed to. The caller waits for a manager who is on the floor, and the wait does more damage than the original problem.
Set an explicit threshold: under $X, whoever answers can resolve immediately — refund, remake, credit — without approval. Pick a number you're comfortable with and make it real. The savings from denying small refunds is almost always smaller than the cost of the delay it creates.
Above that threshold, a manager gets involved, and staff know exactly where the line is instead of guessing.
The shape of a good complaint call
Nothing exotic, but worth writing down because people under pressure skip steps.
Listen first. Let the caller finish. Interrupting with a solution before someone has described the problem reads as dismissal, even when the solution is right.
Acknowledge specifically. "I'm sorry the order arrived cold" beats "sorry for the inconvenience." Specific acknowledgment proves you were listening.
Don't litigate. Determining whose fault it was is rarely worth the conversation. Even when the restaurant is right, winning the argument loses the customer.
Offer a concrete fix. Refund, remake, credit on the next visit — a specific option, not "what would you like us to do," which puts the work back on the caller.
Confirm and close. State what will happen and when. If a refund takes a few days to appear, say so, because otherwise you get a second call.
Log them, and read the log
Individual complaints are noise. The pattern is signal. Log at minimum: the date, what happened, what you did, who handled it, and the related order.
Then actually read it monthly. Three complaints about the same dish is a kitchen problem. A cluster on the same shift is a staffing problem. A run of late deliveries points at capacity, which connects to order throttling against kitchen capacity. None of that is visible if complaints live only in individual memories, and it's the part that actually reduces future complaints.
Refunds and disputes
If a caller has already disputed a charge with their card issuer, the conversation changes — that process runs through your payment processor, and your records matter. Clean order records and confirmations are what you'll submit as evidence. We cover that in reducing phone-order fraud and chargebacks.
Where possible, resolving a complaint directly before it becomes a formal dispute is better for both sides. A fast refund costs you the order. A chargeback costs you the order, a fee, and the time to contest it.
The bottom line
Complaint and refund calls are low in volume and high in consequence, which is exactly backwards from how most restaurants staff them. Route anyone with a problem to a person immediately and don't make them navigate a menu or repeat themselves. Give whoever answers real authority to resolve small amounts on the spot. Listen fully, acknowledge specifically, and offer a concrete fix rather than an argument. Use automation to prevent complaints — status updates, accurate quotes, after-hours capture — not to handle them. And keep a log you actually read, because the pattern across complaints is worth more than any single call.