A guest had a disappointing dinner at your restaurant last night. The food was cold, the service was slow, and nobody seemed to notice. They open your website to complain. If the reply is a generic "thank you for your feedback," they leave a public review instead. If they are heard quickly and personally, they might come back.
Restaurant complaint handling through the website is a moment of truth. Guests who complain directly are giving you a chance to fix things before they tell everyone else.
Step 1: acknowledge immediately
The first reply should acknowledge the problem without defending or explaining:
Guest: My meal last night was cold and we waited 40 minutes for mains. Assistant: I'm sorry to hear that, it's not the experience we want anyone to have. I'll pass this straight to the restaurant manager. Could you share the date, the name the booking was under and the best way to reach you?
Step 2: capture the details once
The manager needs the date, time, booking name, what went wrong and contact details. Capturing these in the first exchange means the guest never has to repeat the story.
Step 3: hand it to a person
Complaints should always be resolved by a manager, not an automated reply. SpideyChat for restaurants captures the complaint and passes the full conversation to your team. The setup is covered in the installation guide and training guide.
Step 4: respond personally within a day
The manager's reply should be personal: apologise, explain what happened if you know, and offer something to put it right. Avoid templated language.
Step 5: fix the cause
A single complaint may be bad luck. Several about the same thing, like slow service on Friday nights, point to a problem to fix. Track complaints by type. Software companies do the same with feedback, as described in handling feature requests that arrive through chat.
Step 6: follow up
After resolving the complaint, a short follow-up when the guest returns, or a note after their next visit, shows you remembered. Guests who see a complaint handled well often become loyal.
Keep complaints separate from bookings
Complaints mixed in with booking requests can wait too long. Routing them straight to a manager keeps them visible. Busy periods make this harder, especially when calls go unanswered, as covered in what happens to restaurant enquiries when the phone rings out.
Trust starts with the first message
How you reply to a complaint sets the tone for everything after. The importance of the first reply is explored in building trust in the first message. Catering customers who have problems need the same care, as covered in catering and takeaway enquiries from your website.
Responding to public reviews
Some unhappy guests go straight to a public review. Reply to those too, calmly and personally, and invite the guest to get in touch directly. Other readers judge the restaurant partly by how it responds to criticism. A thoughtful reply can reassure future guests even when the original experience was poor. Keep it short and never argue.
What good looks like
The guest is acknowledged in seconds, a manager replies personally the same day, the problem is put right, and the restaurant learns something. A complaint handled this way can end with a returning guest rather than a one-star review.