The dates, and why support starts now.
Black Friday 2026 falls on 27 November and Cyber Monday on 30 November. Adobe forecasts US online holiday sales of $275.1 billion between 1 November and 31 December, up 6.7% on last year, with $12.9 billion on Black Friday and $15.1 billion on Cyber Monday. It also expects traffic to US retail sites from generative AI tools to rise 130% year over year, so more shoppers will arrive having already asked an AI about your products. Shopify merchants sold $14.6 billion over the 2025 Black Friday–Cyber Monday weekend, up 27% on 2024, and sales peaked at $5.1 million per minute.
More orders mean more questions, and questions don’t stop when the sale does: order-status questions follow the orders into the next week. Work back from the dates. Many stores stop changing their theme and apps weeks before Black Friday, so any new support tool needs to be installed and tested well before then. The week of the sale is for answering customers, not configuring software.
Six weeks out: publish the answers shoppers will ask for.
Before you think about staffing, fix the source of truth. Most Black Friday questions are predictable, and one clear, published answer helps shoppers, your team and any AI agent at the same time. Put each answer on a page you control, give it an owner, and write down the date you will next review it. If an answer changes during the sale, change it in one place.
- Shipping cutoffs for Christmas delivery, by region and shipping method, and the date you will update them.
- Your holiday returns window, stated once, with exact start and end dates.
- How the discount works: excluded products, whether codes stack, and when the sale ends, including the time zone.
- What happens to out-of-stock and preorder items, and whether you split shipments.
- Order changes: until when a shopper can change an address or cancel, and how to ask.
- Gift options: gift receipts, gift messages and shipping to a different address.
- Your contact hours over the holiday weekend, and when someone will reply.
Write macros for the questions you know are coming.
Macros, or saved replies, keep answers consistent when several people reply at speed. Write them now, have the person who owns each policy approve them, and keep each one short enough to read on a phone. Link to the published policy instead of pasting all of it, so there is only one version to update. These are the ones most stores need; publish a matching FAQ entry for each, so shoppers can find the answer without asking.
- Where is my order: ask for the order number and checkout email, share the status and tracking link, and explain what “fulfilled” means for your store.
- My discount code doesn’t work: check expiry, exclusions and minimum spend, then offer the fix or a person.
- Will it arrive by a date: give the cutoff and the shipping options that still make it.
- Change or cancel my order: explain the window, then hand off, because a person needs to act in Shopify.
- It arrived damaged or wrong: apologize, ask for a photo and the order number, and assign it to a person.
- The price dropped after I bought: state your price-adjustment policy plainly, whatever it is.
- Returns and exchanges: link the returns page and explain the holiday window.
Do the staffing math in words, then in numbers.
You don’t need a forecasting tool for a useful estimate. Start with your normal daily conversation volume from a quiet week. Multiply it by how much you expect demand to rise during the sale; your own order forecast is the best guide, and last year’s peak day is the next best. Subtract the share of questions you expect to be answered without a person, but only for question types you have actually tested. Divide what is left by the number of conversations one person handles well in a shift. Round up, then add cover for breaks, sickness and the unexpected.
An example with made-up numbers: a store that usually handles 150 conversations a day expects three times that on Black Friday, or 450. If published answers and order lookup handled 40% of questions in testing, 270 still need a person. If one person handles about 60 conversations in an eight-hour shift, that is 4.5 people, so plan for five, plus one person on call. These figures are an illustration, not a benchmark; use your own.
Then look at timing. Order-status and delivery questions follow the orders, so keep cover in place for the week after Cyber Monday, not just the weekend itself. Decide in advance who can approve a refund or an exception, so a busy teammate isn’t left waiting for an answer.
Where AI helps.
AI is good at answering the same well-defined question many times, quickly, and at two in the morning. It is only as good as what you have published, so point it at questions with a clear, stable answer and check what it says before the sale starts.
- Order status, through a lookup that checks the order number and email, rather than an AI guess.
- Shipping cutoffs, return windows and discount rules, answered from your published policies with a link.
- Product questions such as sizes, materials, ingredients and compatibility, answered from your product pages.
- After-hours cover: answering what it can and collecting contact details for the rest.
- Other languages, if you sell across borders.
Where a person must handle it.
Some requests need judgment, authority or empathy. In a Gartner survey, 87% of customers said companies using generative AI for customer service must provide access to a human agent. Make the route to a person obvious, and make sure that person sees the whole conversation so the shopper doesn’t have to repeat themselves.
- Refunds, cancellations, address changes after fulfillment and any exception to a policy.
- Damaged, missing or wrong items, and anything that might become a chargeback.
- Health, safety or legal questions, such as allergies, ingredients for a medical condition, or product safety.
- Upset customers, and anyone who asks for a person.
- Anything the AI couldn’t answer from published knowledge. Review these daily and publish the missing answer.
Set expectations in the conversation itself.
Shoppers are more patient when they know what is happening. Show your reply hours in the chat, say plainly when a person will reply, and if you fall behind, say so once in a clear note rather than apologizing in every reply. If a carrier delay hits, update the published shipping answer first and the macro second, so the FAQ, the AI and your team all say the same thing. When you promise a follow-up, collect an email address with the shopper’s consent and make sure someone owns that queue the next morning.
The week-by-week checklist.
Use this as a starting point and move the dates to fit your own change freeze.
- By 16 October: choose and install any new support tools, connect Shopify, and publish your holiday policies.
- By 30 October: write and approve macros, test order lookup with a real test order, and test the handoff to a person on a phone.
- By 13 November: confirm the rota from 26 November to 7 December, including who is on call and who can approve refunds.
- By 20 November: freeze changes to your theme, apps and support setup, and only fix what is broken.
- 26–30 November: check unanswered questions twice a day, update published answers as stock and cutoffs change, and post one clear status note if shipping is delayed.
- 1–7 December: expect order-status and delivery questions, and keep cover in place.
- Early December: publish Christmas shipping cutoffs, then returns guidance for January.
After the weekend: keep what worked.
In the first week of December, read a sample of conversations with the people who answered them. Which questions came up that you hadn’t published an answer for? Which handoffs waited too long? Which macros did people rewrite every time? Fix the source, not just the reply, and write down what you would change next year while it is fresh. That list is the start of next year’s checklist.