Bubble tea shift-cover scripts - DM one person by name, ask about time before mentioning compensation, confirm in writing the moment they say yes, and leave the door open when they say no
You are a communication coach for a bubble tea scheduling
supervisor. Scenario: tomorrow's evening peak (or this
afternoon) is short one assembly person, and I need a
part-timer to cover. Give me message scripts I can copy
and send as-is, structured in three fixed steps.
The three steps (fixed order, do not rearrange):
Step 1 - DM one person by name about time. Never broadcast;
one person per message. The first message asks only about
availability: "Can you cover 5-9pm tomorrow?" No
compensation terms in the first message.
Step 2 - if they hesitate, offer a trade within my actual
authority: scheduling priority ("next time you want a
Saturday day shift, you get first pick"), the shift meal,
or travel allowance if the shop provides one. Do not
promise raises, promotion to trainer, or guaranteed weekly
hours - a scheduling supervisor cannot deliver those.
Step 3 - once they say yes, close the loop in writing on
the spot: arrival time, who to report to, what to wear,
confirm it is entered in the schedule ("you're in the
schedule"), and do not touch that commitment again the
same day.
Give me scripts for these moments (messaging-app register,
each message three sentences or fewer):
1. The opening DM - two versions: a reliably cooperative
part-timer, and one who started recently
2. The follow-up after "let me check / let me ask at
home" followed by two hours of silence - exactly one
nudge, phrased so it does not read as pressure
3. The rejection exit - no asking why, one sentence that
leaves the door open for next time, then I move to the
next person (give me the actual "got it, no problem"
level wording)
4. The confirmation message after they agree (arrival
details plus "you're in the schedule")
5. The morning-of reminder - one short message, no
lecture
After each script add one line labeled [rule]: which of
the three steps it belongs to and why it is phrased that
way.
Constraints:
- Everything stays in natural chat register - no one
finishes a wall of text
- No guilt-trip openers ("we really need you," "the shop
can't run without you") and no hint of "miss this and
don't expect shifts"
- No grand words like "the company needs you" - a
part-timer owes the shop no loyalty; time, role, and
trade are enough
- Do not give performative advice like "be sincere" -
only sentences and the order to send them in
Why it is written this way
DM-by-name instead of broadcasting is the first design decision, and it is about channel, not wording. A group chat lowers the cost of not responding to zero, and it lets the whole crew watch you be declined once - after which nobody volunteers. A named DM turns it into a one-to-one personal decision, and answer rates change accordingly.
"Ask about time before mentioning compensation" is an ordering rule that cannot be flipped. Leading with the offer announces "this shift is hard to fill," and the reader either raises the price or starts wondering what is wrong with the shift. Asked about time first, a yes is a relational yes, and the trade merely confirms it - flip the order and the whole cost structure changes. The authority boundary (no promises about raises or promotion) marks the most common line schedulers cross: a promise you cannot keep teaches the entire crew to wait for your next bid.
The rejection exit and the "one nudge only" rule are the least glamorous and most consequential parts. A part-timer declining a cover is routine; probing why or letting irritation show converts a neutral no into a damaged relationship with someone you will schedule again next week. Keeping the door open is worth more than this one shift.
Closing in writing the moment they agree prevents the classic drift of verbal arrangements - covers get forgotten under "I didn't think it was settled." Entering it into the schedule and saying so, then not touching it again that day, is both basic respect and the reason the commitment holds.
Variables
| Variable | Notes |
|---|---|
| Gap and role | Exact window and role (assembly / register / prep) - the first message must state both precisely; vague windows are the top cause of cover no-shows |
| Trades you can offer | What the shop actually has: shift meal, travel allowance, scheduling priority - list only what is real and within your authority; delete anything that is a promise you cannot keep |