N NoBullshit.wiki 中文

Full-service restaurant complaint escalation checklist - foreign objects, burns, and large billing disputes, with per-level time limits and actions; what happens in the first minute of a red-line complaint decides how it ends

Works with:Claude / GPT-4 classCategories:Full-Service RestaurantLevel:Intermediate Updated

You are a complaint-handling coach for a full-service restaurant. Produce a Complaint Escalation Checklist for use from floor staff up to the GM, printable and postable. Organize by the three levels; each level has five columns: who handles / arrival deadline / must do on the spot / strictly forbidden / escalation trigger. Write actions, not principles.

Three fixed levels:
- Red line: foreign object in food, suspected spoilage, burns or falls, fights, guest medical emergency
- Major: billing dispute above [X], service confrontation (staff and guest at odds), property damage (clothing, belongings)
- Ordinary: slow food, attitude, ambiance issues, small billing errors

Red-line requirements (write this level in the most detail):
- First employee on scene (any role), within 2 minutes: isolate the dish in question (remove the whole plate and preserve it with its utensils - do not wash it, do not touch it), admit nothing and deny nothing, call the duty manager immediately, and for any injury assist with medical care first (call a car, accompany - settle costs later)
- Duty manager, on scene within 5 minutes to take over: log the incident (time / table / those present / what happened / actions already taken), photograph the evidence, decide whether to hold the rest of that batch
- Strictly forbidden: arguing liability on the spot, grabbing at or blocking the guest's phone, promising any compensation amount, asking the guest to delete photos
- Escalation triggers: injury needing medical care, a minor involved, or the guest threatening a regulator complaint - notify the GM immediately; the GM owns all further external communication

Major and ordinary levels get the same five columns, less detail. Ordinary level essentials: resolved on the same shift, never overnight; the handler signs; a follow-up contact within 24 hours.

Append a "log sheet fields" section: the columns a complaint log needs (date and daypart / table / level / what happened / handler / actions taken / outcome / follow-up done or not), so every level of handling leaves a record.

Constraints:
- Medical, police, and regulator procedures say "per local requirements" - invent no legal provisions and no liability rules
- No de-escalation scripts - scripts are a separate document; this checklist covers actions, deadlines, and escalation lines only
- No "raise service awareness" principles - every line must be an observable action

Why it is written this way

The red-line level gets the most detail because a slow response to an ordinary complaint costs an experience, while a wrong first two minutes on a red-line complaint costs an incident. The server who clears and scraps the offending dish, the instinctive "that's impossible," the burn that turns into a whose-fault debate first - once these happen, everything after is played uphill. The checklist treats "first employee on scene" as its own tier because the person fastest to arrive is usually the most junior, and conventional complaint procedures were never written for them.

"Isolate the dish - do not wash it, do not touch it" is the single most valuable line on the sheet. Everything downstream of a foreign-object or spoilage complaint - what the guest is told, what the supplier is charged - depends on the physical evidence, and the most natural on-the-spot reflex is to hustle the offending thing away. Writing preservation into the first-minute actions protects the restaurant's and the guest's shared ability to establish what happened.

"Admit nothing, deny nothing" pairs with "no compensation promises." An on-the-spot admission locks the resolution to the most emotional moment; a denial pushes the guest toward public escalation. Similarly, cashiers and floor staff lack the authority to name compensation figures not out of stinginess but so that someone with authority can decide on complete facts - medical care and safety come first, money gets discussed at the table, calmly.

Appending the log sheet fields makes the whole process auditable. "Resolved same shift" is easy to promise, but without a log, the month-end review of which complaints resolved and which guests came back is all memory. With every tier leaving a record, this checklist doubles as a management report - escalation triggers and follow-up entries sit side by side, and complaint recurrence becomes something you can actually see.

Variables

Variable Notes
Billing dispute amount X Above what value an ordinary complaint becomes major - set against the house average check, commonly two checks and up
Arrival deadlines Staff in 2 minutes, duty manager in 5 assumes a typical floor layout - larger or multi-story houses should adjust to real walking distances and write the numbers down
Batch-hold authority Whether the duty manager may pull the implicated batch immediately - recommended yes with GM sign-off after; if the hold waits for the GM, red-line response slips a full beat

complaintsescalationon-floor response