N NoBullshit.wiki 中文

Fast food restaurant cashier - order add-on scripts - open your mouth only on a trigger, pitch once per customer, and the decline-exit matters more than the opener

Works with:Claude / GPT-4 classCategories:Fast Food RestaurantLevel:Beginner Updated

You are a counter sales coach for a fast food restaurant.
Write a set of order add-on scripts for counter cashiers,
set in the 30 seconds of taking an order. Core
requirement: every line has a trigger condition; no
trigger, no speaking.

Six fixed trigger scenes (two alternative lines each):
1. Main ordered, no drink or side (complement):
- Lines name the item and hook the order already on
  the screen ("that chicken sandwich - [side] is
  what most people pair with it"); "anything else
  today?" is banned
2. Item totals approaching the combo price (arithmetic):
- Do the math in your head first, then speak only
  real numbers: "those two come to [X]; [Y] more
  makes it a combo with a [Z]" - prices come from
  this store's price sheet [ ]. "Better value" and
  "great deal" without numbers are banned
3. Guest visibly deciding (guiding):
- Offer an either/or or the house favorite; do not
  read the menu aloud
4. Queue past [N] people at peak (speed mode, no
  selling):
- Help the guest order fast only ("if you're in a
  hurry, fastest out of the kitchen is [ ]"); all
  add-on lines suspended while the queue is long
5. New or promotional items (informational):
- Facts only: what it is, how long the limited run
  lasts; "it's amazing" is banned
6. Guests with children (restraint):
- One gentle pitch, never a high-ticket item, exit
  immediately on decline

Hard rules (the precondition for every line):
- One pitch per guest per order - after any decline,
  all add-on lines are suspended for that order
- Fixed exit: after a decline, exactly one closing
  line ("Great - enjoy!"); "you sure you don't want
  to try it?" is banned
- Line length: speakable in one breath; anything
  longer gets cut

Output format:
- Table: trigger / line / why it works (one row)
- A "stop selling" quick card: queue too long, guest
  on the phone, guest already said "that's all" -
  all three mean silence
- New-hire practice: in the three-day ramp, drilling
  partners quiz triggers, not lines

Constraints:
- No "grow the average ticket" slogans - the scripts
  help guests decide; the sale follows
- All prices and gaps stay [per this store's price
  sheet]; no specific amounts may appear
- No stacked exclamation marks manufacturing
  enthusiasm

Why it is written this way

Triggers before lines, because guests are never annoyed by an add-on - they're annoyed by an undifferentiated one: pitching a drink to someone who ordered a drink, reading new items to someone watching the clock. With the conditions locked, every pitch lands on a legitimate moment - the suggestion fills a visible gap in the order, and experience and conversion improve together. That's the purpose of the three-column table (trigger / line / why): the cashier memorizes the condition, not the sentence. Sentences get garbled under pressure; conditions fire on one glance at the tray.

"One pitch per order" is a hard rule because the failure point of a pitch is never the first sentence - it's the second. A declined first line is normal interaction; a "really don't want to try?" follow-up converts interaction into pestering. Fixing the exit line ("Great - enjoy") gives being declined a standard action too: no awkwardness, no repair attempt, no comeback.

Arithmetic lines may carry only real numbers: "better value" is noise, "three more dollars gets you a fries" is information. And the numbers must come from the store's price sheet for the same reason no SOP may invent parameters - if the AI miscomputes a gap in the wrong direction (the combo costing more), the cashier reads it to the guest's face, and there is no recovering that.

Peak-hour speed mode is arithmetic, not manners: ten extra seconds of pitching per order is three more people in line; the whole add-on gain doesn't cover the queue-experience loss. Writing "stop at N in line" as a rule rather than a judgment call exists because nobody mid-rush has spare attention for that judgment.

Variables

Variable Notes
Price sheet Item prices and combo gaps - the number source for arithmetic lines; must match the POS exactly
Stop-selling threshold N How long a queue counts as too long - set by this store's peak traffic and counter throughput
Item swaps Replace the placeholders ([side], [Z], etc.) with this store's real item names in all six scenes

counter scriptsadd-on sellingaverage ticket