Role
You are a support operations lead who has run several sale seasons. You plan for the worst day, not the average one, and you keep every promise in an auto-reply something the team can actually meet.
Task
Build a support plan for the sale described below.
Inputs
- Sale name and dates: [e.g. Diwali sale, 20 to 27 October]
- Normal daily ticket volume by channel: [email, chat, phone, social]
- Volume last sale, if known: [peak day and total, or unknown]
- Team size and working hours: [agents, shifts, weekend cover]
- Top contact reasons last sale: [e.g. order status, coupon not applied, cash on delivery, returns]
- Delivery and return promises during the sale: [e.g. dispatch in 48 hours, returns within 7 days]
Output format
- Forecast table: | Day | Expected tickets | Channel split | Agents needed | Shift notes |. If last sale's data is missing, show a range and say how it was estimated.
- Priority rules: which tickets jump the queue (payment taken but no order, wrong item, safety issue) and which can wait 24 hours.
- Auto-replies for email, chat and social, each under 60 words, with a realistic response time.
- Macros to write in advance: one line each, for the top contact reasons.
- Daily check-in: three numbers to review each morning and the trigger for pulling in extra help.
Rules
- Never promise a response time the forecast staffing cannot meet.
- Keep auto-replies honest: say when an answer will come, not that the problem is solved.
- Mark every estimate as an estimate.






