How to Handle Restaurant Customer Complaints During Service

Let the guest explain what went wrong. Then restate the facts: "You asked for the sauce on the side, and it came on the plate." If it isn't clear what they want now, ask. Don't dispute their version until you've checked what the server entered and what the kitchen received.

Tell them who's taking care of it and give a realistic time to come back to the table. Even if the fix takes longer, check in when you said you would. No guest should have to ask three times what's happening with their complaint.

Compare what the guest asked for, what the server confirmed and what the kitchen or bar made. If you use Zeat for ordering, walk your team through what's visible at each step. Check how this tracking works in a demo. If the disagreement is about a modifier, also check the item name and price on the mobile menu.

It could be an instruction that got lost, an unclear menu or a last-minute change in availability. Write down what happened without pinning it on someone's memory. The goal is a fix during the meal first, then the root cause before the next shift.

Before service, spell out what servers can fix on their own and what needs a manager's OK: remaking a dish, offering an alternative, explaining a delay or correcting a check. If a request involves an ingredient or a declared allergy, have the kitchen confirm what it can safely prepare before anyone makes a promise.

Any comp follows your house rules and what actually happened. It shouldn't paper over a mistake that keeps happening. Once the decision is made, explain it to the guest in plain language and make sure the kitchen, the bar and whoever runs the register are all working from the same version.

Keep a short service log: date, table or order, the issue, who's handling it, the response given and how it was resolved. If the guest wants a follow-up after they leave, agree on how and when you'll contact them. Don't leave contact details or personal information in a notebook the whole team can read.

This log isn't a loyalty program. It's there to close out a request and hand it over between shifts. Zeat isn't a complaint ticketing tool or a guest messaging tool. Use whatever system your manager actually checks.

In the post-shift debrief, group similar complaints together: an upcharge nobody explained, a dish 86'd too late, a wait time quoted too short. Pick one fix, one owner and a time to check it's working. A problem solved at one table can come back tomorrow if the menu or the instruction hasn't changed.

If the menu is the issue, update it in Zeat and check what guests see on their phones. If orders aren't getting through correctly, walk through the flow again with front and back of house. The goal is a clearer answer for the next guest, not just one more entry in a logbook.