Black Friday Customer Support Playbook: How to Prepare for BFCM 2026

Black Friday 2026 is Friday 27 November and Cyber Monday is Monday 30 November (Klaviyo BFCM calendar). To prepare customer support, forecast BFCM volume from last year by topic, publish your promo code, shipping cutoff and returns answers by early November, automate order tracking and policy questions, write macros for everything else, build a rota with protected breaks, and plan now for the returns wave in December. Today is seven weeks out, which is enough time if you start this week.

This playbook is the BFCM-specific version of our general seasonal support spikes playbook. It is written for a small ecommerce team, the kind handling 80 to 100 tickets on a normal day in Shopify and a helpdesk like Gorgias, trying to keep CSAT above 4.5 without burning people out.

Key BFCM 2026 dates

Carriers publish holiday shipping deadlines each autumn. Check your carriers’ official pages for the 2026 dates and put them in your FAQs as soon as they are announced.

What are the most common BFCM support tickets?

Peak volume is more repetitive than normal volume, not less. Most of the increase comes from a short list of questions.

The “Yes” rows are where an AI layer or self-service earns its keep. Our order status tickets and refund request volume pages go deeper on the two biggest categories.

Week-by-week BFCM support countdown

Week of 12 October: forecast and decide (T minus 7 weeks)

• Pull last year’s tickets from 1 November to 31 December by day and by tag
• Note the peak day, the topic mix, and how long the returns tail lasted
• Adjust for growth: this year’s order forecast against last year’s
• Decide what to automate, using the table above
• Decide on any temporary help now, because training takes weeks

A quick capacity check, with illustrative numbers. If your team handles 90 tickets a day comfortably and last year’s peak day was three times normal, you need capacity for about 270. If half of those are order status, cutoffs, promo rules and returns policy, automating them well brings the human load closer to 135 to 160, which a small team with extended hours can absorb. Use your own history, not these figures.

Week of 19 October: write the policies (T minus 6 weeks)

Policy questions during a sale have to be answered the same way every time. Write them down before anyone asks.

• Promo rules: which products, stacking with other codes, minimum spend, start and end time with time zone
• Price adjustment policy: what happens if a customer bought last week
• Shipping cutoffs by method and region, once carriers publish theirs
• Holiday returns window and exchange rules
• Order change and cancellation window after checkout
• Gift options and gift receipts

Week of 26 October: publish and connect (T minus 5 weeks)

• Publish a BFCM FAQ page with the answers above, one question per section
• Update the returns and shipping pages with explicit dates
• Connect your help content and store to any AI or self-service layer
• Remove or update last year’s BFCM pages so old dates are not found

Week of 2 November: macros and routing (T minus 4 weeks)

• Write macros for every “Partly” and “No” row in the ticket table
• Set tags and routing so damaged or wrong item tickets jump the queue
• Create a priority view for payment problems
• Decide what agents can approve without asking: a discount, a reship, a refund up to a set amount

Week of 9 November: test everything (T minus 3 weeks)

• Ask your AI or self-service layer 30 real questions from last year’s peak and check the answers
• Test the handoff to a person on a damaged item and a payment problem
• Place a test order and track it through to confirm order status answers work
• Fix anything that failed, then test again

Week of 16 November: rota and rehearsal (T minus 2 weeks)

• Publish the rota from 26 November to 4 December, with breaks named in it
• Assign one person each shift as queue lead, watching for spikes and new problems
• Agree an incident plan: who posts a site banner if a carrier delays or the promo breaks

Week of 23 November: BFCM week

• Daily 10-minute stand-up: volume, new issues, any policy clarifications
• Watch for a new question appearing repeatedly, and publish an answer the same day
• Keep breaks. A tired team writes worse replies

Week of 30 November: Cyber Monday and after

• Same routine through Cyber Monday
• Recovery days for the people who worked the weekend
• Switch focus to delivery questions and the returns wave

BFCM macros worth writing now

Short, specific, and with a clear next step. Adapt the wording to your brand. For more patterns, see our canned response examples.

Promo code did not apply

Thanks for letting us know. The code [CODE] applies to [eligible items] until [end time and time zone]. I have checked your order [number] and [applied the difference as a refund / confirmed it was not eligible because …]. You will see it on your statement within [x] business days.

Delivery before a date

Orders placed by [cutoff date and time] with [shipping method] are expected to arrive before [date]. Your order [number] was placed on [date], so it [is / is not] within that window. Here is your tracking link: [link].

Damaged or wrong item

I am sorry that arrived [damaged / wrong]. Could you send a photo of the item and the packing slip? As soon as I have it, I will [send a replacement / refund you] and you will not need to return the original.

What staffing does a small team need for Black Friday?

You cannot hire your way through a peak in seven weeks without training landing in the busiest fortnight. More useful levers:

• Extend hours rather than headcount. Stagger shifts so the busiest hours have the most people.
• Separate queues. One person on problem tickets (damaged, wrong, payment) and the rest on everything else.
• Pre-approve decisions. If every refund needs a manager, the manager becomes the bottleneck.
• Borrow carefully. Colleagues from other teams can handle tagged, macro-driven tickets with a short brief. Keep them off complaints.

Our ecommerce industry page covers the wider support pattern for online stores.

How do you prevent agent burnout during BFCM?

Burnout in peak season usually comes from relentless repetition and from feeling unable to help. Address both.

• Remove the repetitive tickets from the human queue, so people spend their time on problems they can actually solve.
• Cap shifts and protect breaks. Write breaks into the rota, not into good intentions.
• Rotate people off the problem-ticket queue every few hours.
• Give agents authority to fix common problems on the spot.
• Schedule recovery time after Cyber Monday, not after the returns wave.

See support agent burnout for longer-term fixes.

Plan for the post-BFCM returns wave

The second peak arrives when gifts are opened and sale purchases are reconsidered. It is mostly policy questions and exchange requests.

• Publish the holiday returns window clearly, with the exact last date.
• Automate “how do I return this” and “what is the window” questions.
• Prepare an exchange macro and a store-credit macro.
• Tag returns by reason, so January’s product and sizing fixes are based on data.

Which tools do you need for BFCM?

For most stores, the right answer is the helpdesk you already have, connected to your store, plus automation for the repetitive topics. Switching helpdesks in October adds risk without solving volume. If you are reviewing options anyway, our guide to the best tools for ecommerce and Shopify support compares the main choices, and the Shopify and Gorgias integration pages show how an AI layer sits alongside them.

Where Fidiora fits

Fidiora answers order status, shipping, promo and returns questions from your store content and help docs, with cited sources, and hands damaged items, payment problems and complaints to your team with the conversation attached. It works alongside your existing helpdesk, goes live in under an hour, and costs $0.69 per genuine resolution, dropping to $0.45 above 1,000 a month, with no seat fees. Handoffs are always free and abandoned chats are never billed, and a monthly spend cap keeps a big BFCM month predictable. See pricing to model your peak.

The one thing to do this week

Pull last year’s BFCM tickets by topic. Everything else in this playbook, what to automate, which macros to write, how many people to roster, follows from that one export.