Fast food restaurant server - in-the-moment complaint scripts - the first line restates the facts, remedies only from the authorized menu, and food-safety or injury scenes get stabilized, not adjudicated

You are a frontline service coach for a fast food
restaurant. Write a set of complaint-handling scripts
for counter and floor servers - scripts they can read
aloud verbatim without sounding like they're reading.

Five fixed scenes:
1. Long wait (the guest is pushing; their number long
   past)
2. Wrong or missing items
3. Food problems (foreign object, undercooked, off
   taste, wrong temperature)
4. Cleanliness (tables, floors, restrooms)
5. Attitude clash (guest and staff arguing on the
  spot)

Each scene gets three parts:
- The opener (say it within 10 seconds): restate the
  facts + own it. The restatement carries specifics -
  how many minutes waited, which item was wrong.
  "Sorry for the inconvenience" is banned as an
  opener; it contains no facts
- The remedy: offer [2] options for the guest to pick
  from, every option drawn from this store's
  authorization [per store policy: e.g. remake, refund
  the item, small complimentary drink], phrased as an
  either/or question ("Should we remake this one, or
  refund the item first?") - never "what would you
  like us to do?", which hands the decision to someone
  running hot
- The closer: one line proving the issue is caught -
  the remake's ticket number, the refund's arrival
  route. No promises of extra compensation

Red-line scenes (the script stabilizes; it does not
resolve):
- Food safety: foreign object, spoilage, guest feeling
  unwell after eating
- Personal injury: burns, slips, allergic reaction
- Threats to post publicly or report to authorities
These get the "hold three lines": say a manager is
coming now, invite the guest to sit somewhere quieter,
commit to the manager arriving within [N] minutes. 
Beyond that, the server makes no factual judgment
("that's impossible, not from us") and no compensation
promise ("we'll pay for it")

Two attachments after the scripts:
- A quick-reference card: five scenes by three parts,
  two lines per cell, printable, taped under the
  register
- A "never say" list: ten banned lines (e.g. "no way",
  "nobody else complained", "that's how it's always
  been", "you need to understand us")

Constraints:
- No specific amounts or discount percentages - every
  remedy option stays [per store policy]
- The register is calm and concrete; no exclamation-
  mark enthusiasm
- Every line is speakable in one breath
- No "raise service awareness" conclusions

Why it is written this way

The opener restates facts before any apology because "sorry for the inconvenience" carries zero information - a guest hears it three times a day everywhere. "You've waited 18 minutes, 8 past what we promised - that's on us" is what being caught actually feels like, and the feeling comes entirely from the numbers. Restating has a second job: confirming you understood the complaint, since half of all escalations start with an employee processing before listening finished.

The remedy is forced into either/or rather than open-ended out of consideration for someone running hot: asked to "make a demand", an angry guest produces an emotional price; offered two dignified options, almost everyone picks one and steps down. Either/or also fences the server's authority structurally - the option list is the authority list, and unauthorized promises have no slot in the script to occupy.

Red-line scenes exist to stop well-meant improvisation. "We'll pay for it" and "that's impossible" are the two sentences that drag the store into the worst position - the first an unauthorized commitment, the second a declaration of war. In food-safety and injury scenes the script does exactly three things: call the manager, seat the guest, give an arrival time. Judgment and promises belong to the manager entirely - that is division of labor, not evasion.

The quick-reference card is the real deliverable. Nobody memorizes five scenes by three parts; the version that gets used at rush is two lines per cell, taped under the register, readable in one glance down.

Variables