wowprompt

Sale day live monitoring checklist for an online store

Builds the hour-by-hour checklist a small team follows on the day a big sale goes live: prices and coupons, stock, checkout and payment failures, site speed, ads, courier pickups and support queues, with who watches what and what to do when a number goes wrong. Use it for Diwali, end-of-season or brand anniversary sales, and any flash sale.

A sale day timeline with checks every hour, owners and alert levels, a table of problems with first actions, and a closing report outline
The output this prompt produced, unedited.

The prompt

What to give

  • Sale dates and times with time zone: [e.g. 2026-10-24 00:00 to 2026-10-27 23:59 IST]
  • Team and roles: [names or roles, e.g. owner, catalogue, ads, support, warehouse]
  • Platform and tools: [store platform, payment provider, courier panel, analytics]
  • Normal numbers to compare with: [orders per hour, conversion rate, payment success rate, page load time]
  • Top products and stock: [list with units]
  • Offers and coupons: [details]
  • Ad budgets per day: [amount per channel]

Check every hour

  1. Prices and coupon discounts on the top products match the plan.
  2. Stock on top products; hide or swap anything near zero.
  3. Payment success rate and the most common failure reason.
  4. Orders per hour against the expected number.
  5. Page load time on a phone for the homepage, one product page and checkout.
  6. Ad spend pace against budget; pause anything spending without orders.
  7. Support queue size and the most common question.
  8. Courier pickups booked for the orders of the last few hours.

Output format

  1. Timeline: the hour before launch, launch, the first two hours, then every hour, and closing.
  2. | Check | Owner | Normal | Alert level | First action |
  3. Problem playbook: wrong price live, coupon not working, payment provider down, site slow, stock oversold, courier missed pickup; each with three first actions and who decides.
  4. Messages to have ready: banner for a known issue, support auto-reply, apology for an oversold item.
  5. A closing report outline: orders, revenue, conversion, problems and fixes, what to change next time.

Guardrails

  • Alert levels come from the normal numbers given; do not invent benchmarks.
  • A wrong price that favours the customer is fixed going forward; orders already placed are a decision for the owner, not the checklist.
  • Keep payment and customer data out of shared chat; use order IDs only.
sale day checklistflash sale monitoringecommerce launch checklistonline store salefestive sale operationswar room checklist

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