← Blog

Playbook 3 min read

Black Friday for support teams: the playbook for 2–4× ticket volume

Every Black Friday guide talks about ads, offers and site speed. Almost none talk about the department that actually absorbs the aftermath. The numbers are blunt: across the Black Friday/Cyber Monday window, support ticket volume typically runs 80–200% above a normal week (some stores see several times their daily load compressed into 72 hours), while customer patience shrinks: during peak events, most shoppers expect answers within minutes, not hours.

And here’s the part that catches merchants every year:

Support’s Black Friday isn’t in November

The order spike hits support with a lag, in three waves:

  1. Sale weekend: pre-purchase questions (“does the code work?”, “can I change the address?”), payment issues, instant cancellations. Smallest wave, highest urgency.
  2. Late November–December: the WISMO flood. Every carrier network in Europe runs beyond capacity; parcels genuinely slow down, tracking gaps widen, and “where is my order?” arrives in bulk, right when the answer changes daily (the WISMO playbook). Lost-parcel cases peak here too (that process).
  3. January: the returns wave. Return requests spike sharply in the weeks after Christmas: wrong-size gifts, duplicates, “checking where my refund is”. Merchants who staffed up for November and relaxed in January get hit twice.

Plan for a ten-week marathon, not a weekend sprint.

The policies to decide by September

Peak-season tickets multiply when policy is unclear. Decide these before the first banner goes live, write them on the site, and make them one-line-answerable:

  • Gift returns. Extend the return window through end of January and say so loudly. It’s a conversion argument in November and it spreads the January wave. (Remember the floor: the statutory 14 days are yours to extend, never to shrink, the legal baseline.)
  • Price adjustments. The classic peak ticket nobody prepares for: “I bought this three days ago and now it’s 30% off.” Decide your answer once (e.g. goodwill credit within 7 days) and template it. Improvised answers here create precedents and forum screenshots.
  • Delivery promises and cutoffs. Publish honest “order by X for Christmas” dates per carrier and stop promising what December logistics can’t deliver. Every optimistic promise is a December ticket.
  • Out-of-stock handling. Backorder, refund, or substitute: decided, written, templated.

Cut standard cases before the flood, don’t staff for them

The instinct is seasonal hires. The math rarely works: temps for six weeks spend two of them learning, peak at mediocre accuracy on your policies, and leave before January’s returns wave. The hard part of support is knowing your catalog and rules, not typing.

The volume that actually threatens you is standard cases (WISMO, returns, address changes, cancellations), which are exactly the automatable ones:

  • Proactive shipping communication at scale: shipped / delay / stuck- parcel notices sent before the customer writes. In carrier chaos, this is the single biggest ticket killer.
  • Automated resolution for the standard categories, with live tracking and order data. Answers that hold at 11pm on Cyber Sunday, when most of the revenue happens and nobody is on shift. If you’re evaluating tooling for this, here’s what to look for, and do it in October, not mid-November: automation needs its draft-mode trust-building phase before the flood.
  • Templates for the seasonal specials (price adjustment, cutoff missed, gift receipt) ready in the drawer (the standard seven).
  • Humans reserved for judgment: escalations, VIPs, goodwill calls, angry cases, with a weekend on-call plan for the sale window itself.

Watch three numbers weekly through the peak

  1. First reply time, including weekends: the metric that decides whether frustration stays private or goes public (reviews) or expensive (chargebacks). Both spike in December for exactly this reason.
  2. Ticket-per-order rate: volume alone misleads when orders triple; the rate tells you whether your prevention is holding.
  3. Backlog age: a ticket older than 48 hours in December is a chargeback or one-star review in incubation.

The January dividend

Done right, peak season is where post-purchase automation pays for its whole year: the categories you automated for Black Friday keep running in the January returns wave, and in the quiet of February you’re reading a cost-per-ticket number that no seasonal-hiring plan reaches. If you want to see what the automated version looks like on your own store’s cases before Q4: the live demo takes a minute, no signup.

What can we help with?

How many support tickets a month?

What powers your store?

Great, who should we reply to?

Last step, a bit about your store.

Free & no obligation · reply within one business day

Thanks, message received.

We’ll get back within one business day. Want to talk sooner?