Service Recovery Script Kit

Ready-to-use short, medium, and in-person scripts for common guest complaints (taste, temperature, wait time, order mistake), clear escalation thresholds, comping rules with financial caps, required documentation fields, and follow-up templates to recover trust and turn problems into repeat visits.

Service Recovery Script Kit

Purpose: Give front-of-house teams simple, consistent words and decision rules to resolve common guest complaints quickly, protect reputation, and convert a poor experience into a repeat visit. Use these scripts as training aids and role-play prompts. Keep the language natural—encourage staff to adapt phrasing while keeping the intent and steps.

How to use this kit

  1. Start with the short script to acknowledge and stabilize the situation.
  2. If the guest remains dissatisfied, move to the medium script and offer an immediate remedy (replace, remake, comp small item, etc.).
  3. Escalate to the in-person/manager script when thresholds are met (see Escalation Rules).
  4. Record the incident using the Documentation Fields below and follow the Follow-up Protocol.

General principles (train these briefly)

  • Listen first. Let the guest speak without interruption.
  • Empathize: name the issue and apologize for the experience (not for the guest's feelings).
  • Act quickly: people judge recovery by speed and sincerity.
  • Keep language positive and specific: say what you will do, not what you won’t.
  • Document every recovery so managers can spot patterns.

Scripts by complaint category

Taste (food not as expected)

Short (server): "I'm sorry that isn't tasting right for you. Would you like me to have the kitchen remake it or bring you something else?"

Medium (server): "Thank you for telling me. I can have the chef remake it to the way you prefer, or I can bring a different dish right away. Which would you prefer?"

In-person / Manager: "I'm sorry we missed the mark. I’m the manager — we want you to enjoy your meal. I can ask the chef to remake this, or I can comp this item and bring you something else on the house. What would make this right for you?"

Temperature (too cold or too hot)

Short (server): "I'm sorry—I'll replace that right away and make sure it's at the right temperature."

Medium (server): "I'll take that back and have it adjusted for you. I'll come check back in a few minutes to make sure it's right."

In-person / Manager: "I apologize that this arrived at the wrong temperature. I can send a fresh one out and offer a complimentary appetizer/dessert while you wait, or take the item off the bill—what would you prefer?"

Wait time / slow service

Short (server): "I'm so sorry for the delay. Your food is on its way — can I bring you a complimentary drink while you wait?"

Medium (server): "We’re behind right now and I’m sorry for the inconvenience. I can comp a starter or dessert and check with the kitchen to prioritize your order. Would you like that?"

In-person / Manager: "We didn’t meet your expectations tonight. I apologize. I’d like to offer a comp on part of your bill and a complimentary dessert/next-visit coupon. Would that be acceptable?"

Mistake / wrong order

Short (server): "I’m sorry—that was our mistake. I’ll replace it right away."

Medium (server): "I apologize for the error. We’ll have the correct item out immediately and you may keep what you received, or I can remove it from the bill—what would you prefer?"

In-person / Manager: "This is unacceptable and I apologize on behalf of the team. I’ll personally make sure the correct item is prepared and I’d like to offer a partial comp or a free item while you wait. Can I make that up to you now?"

Escalation thresholds (when to involve manager)

  • Manager should be called when the guest asks for a manager, or when a short/medium script fails to calm the guest.
  • Call manager for severe food safety concerns, visible illness, or serious allergy issues immediately.
  • Call manager when the value of the remedy requested exceeds the server's comping limit (see Comping Rules).
  • Manager should review any incident that results in a full-check comp, social media complaint, or written complaint.

Comping rules (examples — adapt to local costs)

  • Server discretion: comp appetizers/drinks up to $10 without manager approval.
  • Manager discretion: comp entree items or discounts up to $25 for immediate recovery.
  • General manager approval: comps over $25 or when multiple items or entire checks are affected.
  • Always document comps with reason, amount, and manager initials.

Documentation fields (record every incident)

Required minimum fields to capture in a log or POS note:

  • Date/time
  • Server name and table number
  • Complaint category (taste, temperature, wait, mistake, safety, allergy, other)
  • Brief guest words (quote, 10–20 words)
  • Action taken (remade, replaced, comped item, discount % or $)
  • Manager involved (name) and escalation time
  • Follow-up planned (call, email, coupon) and due date

Follow-up protocol

  1. If manager involved: call the guest within 24 hours if contact info is available for severe complaints or full-check comps.
  2. Send a short apology email or text (template below) and offer a tangible next-step (discount, complimentary item, invitation to return) when appropriate.
  3. Log follow-up completion in the incident record and close the incident when follow-up is done.

Sample follow-up message (email/text): "Hi [Name], this is [Manager] from [Restaurant]. I'm sorry about your experience on [date]. We'd like to make it right—please call me at [phone] or use this code [CODE] for [offer]. Thank you for giving us the chance to improve."

Do / Don't quick tips

  • Do: Use the guest’s name when possible, offer clear choices, be decisive.
  • Do: Follow through immediately and communicate back to the guest on progress.
  • Don't: Argue or blame the kitchen or policies—own the response and be solution-focused.
  • Don't: Promise things you can’t control (e.g., “we’ll fire someone”); promise the action you'll take instead.

Training and adoption suggestions

  • Run 10–15 minute role-play drills during weekly huddles using these scripts.
  • Give servers a one-page card with short scripts and comping limits.
  • Review logged incidents weekly to spot repeat problems and adjust SOPs or menu items.

Useful metrics to track

  • Number of service recovery incidents per week (by category)
  • Average comp amount and frequency
  • Repeat visit rate of guests who received follow-up
  • Time to manager escalation

Template customization notes

Adapt comping caps, escalation names, and follow-up offers to local margins and brand voice. Keep the core steps consistent: acknowledge, empathize, remedy, document, follow-up.


Discussion

Comments and conversation will live here.