Breakfast shop kitchen helper - scripts for the moment you're drowning: the three-step status-not-emotion call for help, and two answers for customers pressing at the window

Write a set of rush-hour scripts for a breakfast shop kitchen helper,
for the moment I'm covering several stations alone and starting to
drown. For each script give: the situation / the line to say verbatim /
why it works / the version that must never be said.

Set 1 - Calling for help (to the manager / head chef / coworkers;
use in order, escalate one level at a time)

Step 1 - Report status (not an SOS):
Line: "Three trays not out, two vats of soy milk to go, two tickets
  on the griddle - I'm holding three things."
Why: the listener receives a list and can instantly pick what to
  take; "I can't keep up" carries only emotion, and now they have
  to ask what's wrong first - nobody has time to ask at 7 a.m.
Forbidden version: "I'm dying over here!" (zero information, and
  it invites the "who isn't busy?" resentment)

Step 2 - Name the ask:
Line: "Ms. Zhang - watch my steamer for ten minutes, just watch
  the clock and lift the lid on time."
Why: a request has to land on a named person with a named action.
  "Can somebody help?" ends with everyone assuming somebody else
  went.
Forbidden version: "Anyone going to give me a hand?" (unclaimed
  equals unshouted)

Step 3 - Set the deadline and the fallback:
Line: "If nobody takes the steamer in two minutes, I'm shutting
  the griddle and watching it myself - say so if you can take it."
Why: the call now ships with a default plan, so even with no
  response nothing waits to fail; and the response window kills
  the "hang in there" deferral.
Forbidden version: (saying nothing, spinning through it alone -
  when a tray is ruined, nobody even knows you were past your
  limit)

Set 2 - Being pressed at the window (to customers)

Customer asks "how much longer for mine?":
Line: "It's this next round out of the steamer - I'll let these
  two behind you order first, and yours comes out right as they're
  done."
Why: no minutes promised (promise three minutes, miss it, and
  you've handed them the bad-review receipt); what's offered is
  sequence and events (this round, after these two, out of the
  steamer) - things the customer can verify themselves.
Forbidden version: "Any second now!" (said three times in a row,
  every word is escalating the anger)

Customer clearly impatient, tapping the window:
Line: "Sorry - yours is marked down separately, first one out of
  this pot. If you could wait just to the side here so the folks
  behind can order."
Why: first confirm "you are not forgotten" (the root of pressing
  is fear of being skipped), then give a position instruction -
  waiting becomes a bounded action instead of standing in place
  accumulating heat.
Forbidden version: "There's a line, what's the rush?" (one
  sentence converts an order problem into a conflict)

Constraints:
- Every script must be a complete sentence speakable verbatim -
  no stage directions like "explain sincerely"
- No version may promise a specific number of wait minutes
- No "keep smiling" or "stay calm" filler - the sentences
  themselves should already be calm and non-escalating

Why it is written this way

A helper breaking down mid-rush is almost never about finishing the work - it's about severed information: nobody knows he's past his limit, and he knows but can't say it, and the one thing he does say, "I can't keep up," lands in listeners' ears as complaint, not distress call. The three-step call turns distress into an information flow: status (so others can judge), a named ask (so someone can claim it), deadline-and-fallback (so non-response still has a floor). Step 3 is the actual insurance: it assumes nobody is coming and pre-announces a degradation move (drop the griddle, save the steamer) - and that sentence is paradoxically the one most likely to be caught, because now everyone hears what happens if they don't.

The two customer scripts share one core: never promise minutes. Every rush estimate is wrong, and "any second now" on its third repetition has become a lie. Swap in sequence and events - this round, after these two, out of this pot - and the customer verifies progress themselves; the promise shifts from "my time forecast" to "a process fact," and the bad-review receipt disappears. In the window-tapping script, "yours is marked down separately" does the heavy lifting: ninety percent of pressing comes from fear of being forgotten, and confirmation of being remembered beats any apology - followed immediately by a position instruction that translates an emotion problem into a floor-plan problem.

The forbidden versions matter as much as the scripts: they're not comic relief, they're negative instruction. A helper's default output under pressure is exactly those forbidden lines - "any second now," "can somebody help" - and writing the wrong version out in daylight is what lets someone recognize, mid-crisis, the sentence they were just about to say. That's also the line between a scripts entry and an article about communication principles: principles say "communicate effectively"; scripts hand you the sentence.

Variables