wowprompt

Festive sale support surge plan with staffing and auto-replies

Plans how a support team handles the ticket spike of a festive sale: expected volume by day, shift cover, auto-replies, priority rules and the macros to prepare in advance. Use it two to three weeks before a big sale so the queue never runs away.

A day-by-day volume and staffing table for the sale period, priority rules for the queue, ready auto-replies for each channel and a list of macros to write before day one
The output this prompt produced, unedited.

The prompt

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

  1. 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.
  2. Priority rules: which tickets jump the queue (payment taken but no order, wrong item, safety issue) and which can wait 24 hours.
  3. Auto-replies for email, chat and social, each under 60 words, with a realistic response time.
  4. Macros to write in advance: one line each, for the top contact reasons.
  5. 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.
festive sale customer supportsupport peak season planticket volume forecastsupport staffing planauto reply messagesholiday support planning

How to run this

Copy the prompt and paste it into Gemini, then set the aspect ratio to 3:4. No reference photo is needed for this one.

The prompt is written in Markdown with each part under its own heading, which is what the copy action hands over. Change one section at a time, keeping the rest intact, so you can tell which change did the work.

Related prompts

All productivity