Bubble tea register upsell scripts - speak only when three or fewer are queued, one pitch per customer, one graceful sentence to close after a no

You are a service trainer for a bubble tea shop. Give me
a set of register upsell scripts. When to speak matters
more than what to say.

The switch (fixed - no vague versions):
- Queue of 3 or fewer: one recommendation is allowed -
  one per customer per visit, and after the pitch you
  stop regardless of outcome
- Queue of more than 3: no recommendations, order
  confirmation only (drink / sugar / ice / for here
  or to go)
- Customer staring at the phone menu undecided: do not
  pitch anything new - help them finish ordering first

For each scenario below give one line that can be said
verbatim (one sentence, under ~15 words where possible),
when to use it, and how to close if the customer does
not bite:
1. Topping add-on (pearls, taro balls, paid extras) -
   only to customers who ordered a plain base drink
2. Size upsize (when the large is the better deal per
   ounce) - only when the price difference is simple
   to state; do not recite the price list
3. Second-drink-half-price / BOGO deals - confirm the
   deal actually applies (hours, menu items) first;
   "I think there's a deal" must never appear in the
   script
4. New drink intro - the selling point in two sentences;
   if the customer does not respond, just help them
   order
5. Membership / joining the group - only after payment
   completes, never during ordering
6. "Which one is good?" - answer with one question
   about their taste (sweet or not, want tea flavor?),
   never a tour of the whole menu

Format per scenario:
[Script] the verbatim line
[Switch] what queue length / what kind of customer it
may be said to
[Close] the next sentence if they do not bite or say
no - it must be a natural finish at the level of
"Great, is that everything?", never a re-angled second
pitch

Constraints:
- No "best in the city" / "you'll regret not trying
  it" style claims
- "After a refusal, re-pitching the same customer with
  a different script" is explicitly banned - write that
  as a single rule at the top of the set so I can tape
  it by the register
- No "smile more" / "be enthusiastic" style
  instructions that cannot be followed as written -
  only sentences, switches, and closes

Why it is written this way

The core tension in bubble tea register upselling is average ticket versus queue: the prettiest pitch still costs you the crowd behind it when the line reaches the door. So the first design here is not wording but a switch - "three or fewer in line may get one pitch, more than three gets confirmation only" is a countable rule. A cashier does not have to read the room; a glance at the line decides. Rules that can be counted get followed.

"One pitch per customer per visit" plus the paired [Close] line exists to kill the grind. What ruins the experience is rarely the recommendation itself - it is continuing to push after a no, which annoys the customer, stalls the line, and embarrasses the cashier. Giving a fixed closing sentence ("Great, is that everything?") means the employee knows exactly what to say after a no instead of improvising a second attempt.

The scenario list follows the real order flow: topping and size prompts carry the most direct money (topping lines land best on customers who ordered a plain base), deal prompts require verifying applicability first ("I think there's a deal" is the seed of a future complaint), and membership talk is pushed to after payment because promos that eat ordering time irritate everyone in line. Each scenario restricts its own opening condition because the same sentence lands in opposite ways on different customer states.

Banning exaggeration and "smile more" advice marks the boundary of the set: the former is a food-claim risk, the latter is unactionable fluff - everything a trainer hands to staff must be sayable as written.

Variables