By SupportHQ Team · October 27, 2026 · Automation

Ecommerce Customer Service: Peak Season Prep for Small Stores

Black Friday is November 27, 2026. Cyber Monday is November 30. For a small store, the sale brings more orders, and the orders bring questions. Good ecommerce customer service in peak season starts a month before the sale, with a forecast, a few updated policy pages, and a clear line between what a bot answers and what a person answers.

This post is a week-by-week plan from the week of October 26 to the first week of January, when the returns arrive.

Week of October 26: forecast your ticket volume

Use one formula:

Expected conversations = expected orders × contact rate

To get your contact rate, export last year’s orders for the two weeks around Black Friday 2025 (November 24 to December 7). Count customer conversations for the same dates across chat, email, and social DMs. Divide conversations by orders.

If you have no clean data, use a published benchmark as a starting assumption. Gorgias publishes tickets per 100 orders by vertical, from its March 2026 platform data for stores at about $10M in sales:

This is March data, and many of these stores already automate. For Black Friday, Gorgias’s own forecasting guide says it typically sees 30 to 50 tickets per 100 orders, and about 20 with automation. Without automation, plan on 30 to 50. Treat the number as an assumption, and replace it with your own rate next year.

A worked example

All inputs below are example assumptions for an apparel store:

• Last year, the store had 900 orders from November 24 to December 7.
• The owner plans for 20% growth: 900 × 1.2 = 1,080 orders.
• With no message count from last year, the owner uses the low end of the Gorgias Black Friday range: 30 per 100 orders.
• Forecast: 1,080 × 0.30 = 324 conversations in two weeks, or about 23 a day on average. At the high end (50 per 100), it is 540.

The average hides the peak. In last year’s export, 40% of the fortnight’s orders came from Black Friday to Cyber Monday. So 1,080 × 0.40 = 432 orders land in four days.

Questions do not arrive at the same time as orders. Pre-purchase questions (codes, stock, shipping times) arrive during the sale. “Where is my order” questions arrive when a parcel is late or the tracking stops moving, often a week later. Plan for two peaks: the sale weekend and the week after it.

Check it against your time

Gorgias cites 40 to 60 tickets per day as a healthy load for a full-time support agent. A store owner who also packs orders does not have a full day. Time your next 10 replies to get your own number. Example: 6 minutes per reply and 90 minutes a day for support gives 15 conversations a day. The forecast above is 23 a day on average. The 432 sale-weekend orders alone bring about 130 conversations (432 × 0.30), spread over the sale and the days after it. The gap is what you automate, or what a helper covers.

The ecommerce customer service questions that spike

Most of the extra volume comes from a short list. The same Gorgias forecasting guide reports that up to 30% of incoming tickets are shipping status requests.

Week of November 2: write or update five policy pages

An AI agent can only give answers that are in your content, so write the pages first. Our post on knowledge base structure covers the format.

1. Holiday shipping cutoff notice

Use this rule: your cutoff = the carrier’s send-by date, minus your processing time, minus one buffer day.

USPS publishes 2026 holiday send-by dates for delivery by December 25 in the contiguous US (checked October 1, 2026): Ground Advantage and First-Class Mail on December 17, Priority Mail on December 18, and Priority Mail Express on December 19. Check your own carrier if you use UPS or FedEx.

Example: the store needs 2 business days to ship and adds 1 buffer day. Ground Advantage is December 17, a Thursday. Three business days earlier is Monday, December 14.

Holiday shipping cutoffs 2026

To receive your order by December 25 (contiguous US), order by:
- Standard shipping: [Monday, December 14], 11:59 p.m. [time zone]
- Priority shipping: [Tuesday, December 15], 11:59 p.m. [time zone]
- Express shipping: [Wednesday, December 16], 11:59 p.m. [time zone]

We ship orders within [2] business days.
Orders placed after these dates still ship, but we cannot promise delivery by December 25.
Alaska, Hawaii, and international orders: [dates, or "message us before you order"].
Carriers set delivery times. After your order ships, the tracking link in your shipping confirmation email shows the latest status.

2. Holiday returns policy

Holiday returns

Orders placed from [November 1] to [December 24, 2026] can be returned until [January 31, 2027].
Items must be [unused, with tags attached, in the original packaging].
Gift recipients can return an item with the order number or the gift receipt. Gift returns get [store credit / a refund to the original payment method].
These items cannot be returned: [final sale items, personalized items].
To start a return: [link to your returns page, or "message us with your order number and email"].
We send the refund within [5] business days after the item reaches us. Your bank can take [3 to 10] more days.

3. Sale terms

List the start and end time with a time zone, excluded products, whether codes stack, whether the discount applies to shipping, and your rule for orders placed before the sale. Write the rule even if the answer is “no”. A written “no” ends the conversation. A missing rule sends it to you.

4. How to track your order

Say where the tracking link is, when it appears, and what “label created” means. Then give one clear trigger: “If your tracking has not changed for [5] business days, message us with your order number.” That sentence is also your handoff rule.

5. Stock and restocks

The agent cannot see live stock. Write what is true for every product: “Stock on each product page is live. We cannot hold items. Restocks are announced [where].” Then the agent can send customers to the product page instead of guessing.

Week of November 9: decide what to automate

Use one rule: if the answer is the same for every customer, the agent answers it. If the answer depends on one order, a person answers it.

SupportHQ, like any chatbot that reads your policy pages, cannot see your orders. It does not look up an order, track a parcel, or change an order in your store. So “where is my order” splits in two. The agent explains how to track. A person handles the order itself. Helpdesks that connect to your store’s order data can show order status in the chat. If most of your volume is about specific orders, that kind of tool fits better.

Add rules like these to the agent’s instructions:

## Orders
- You cannot see orders, tracking, or stock. Never guess an order's status or a delivery date.
- For "where is my order", explain how to find the tracking link and what each tracking status means, using the order tracking page.
- Hand off to the team when the customer:
  - gives an order number and the tracking has not changed for [5] business days
  - says the parcel shows delivered but did not arrive
  - reports a damaged, wrong, or missing item
  - wants to change the address, change the order, or cancel
  - asks for a refund or a price adjustment
- Before you hand off, ask for the order number. If the checkout email may differ from the chat email, ask which email was used at checkout.

Then turn on human transfer in the project’s notification settings. It is off by default, and without it the agent cannot hand off. You can also paste the “Hand off to the team when” list into its Trigger Conditions field.

Here is how the exchange looks:

Customer: Where is my order? I ordered on Black Friday.

Agent: We ship orders within 2 business days. When your order ships, we email you a confirmation with a tracking link. Open that link to see where the parcel is. If you cannot find the email, check your spam folder.

Customer: The tracking says “label created” since Monday. Order #4821.

Agent: “Label created” means the carrier has not scanned the parcel yet. If it has shown “label created” since Monday, that is 5 business days, so I am passing this to our team. Is the email you gave at the start the one you used at checkout?

The person who picks up the handoff sees the order number, the email, and a summary of the thread, so the customer does not repeat the story.

Week of November 16: load, test, and rehearse

• Load the five pages into the agent, plus your existing shipping, returns, and size guide pages.
• Install the widget on every storefront page. On Shopify, that is a snippet in theme.liquid. The Shopify install guide has the steps. The widget does not appear on the checkout page on standard Shopify plans.
• Require an email before the chat starts, so a person can follow up on a handoff.
• Test 20 real questions. Use last year’s messages. Include the hard ones: “Will it arrive by Christmas if I order on December 16?”, “My code SAVE20 does not work”, and “Where is order #1234?”. The last one must hand off.
• Send alerts to your phone. Team alerts go by email, Telegram, or SMS. Pick the one you see while packing.
• Prepare the human replies. Our customer support response templates cover delays, refunds, and handoff replies.

Black Friday to Cyber Monday: the day-of checklist

Each morning:

• Check that the sale times on the banner match the sale terms page.
• Test each discount code at checkout.
• Ask the widget three questions on your phone: one shipping, one code, one order number. Close that test handoff.

During the day:

• Check handoffs at fixed times, for example 10:00, 13:00, 16:00, and 19:00.
• Answer address changes and cancellations first. They expire when the order ships.
• When you reply in a conversation, the agent goes quiet in it. You do not need to stop it.
• If a product sells out, update its page and your restock page.
• If a problem hits many orders (a broken code, a carrier delay), add a short notice to the agent’s content. Then the agent answers it, not you.

Each evening:

• Open the Human support requests card on the Overview page. Each request shows a reason and a summary.
• If the same reason shows up three times, write the missing answer into your content.

December 1 to 18: the cutoff weeks

Keep the cutoff notice at the top of the shipping page and on product pages. If a carrier changes its dates, update the notice the same day.

The day after your last cutoff, change the notice. Example: “Orders placed now ship after December 25. Need a gift today? [Gift cards are delivered by email.]” A clear “no” with an alternative gives the customer a next step.

January 4 to 10: returns season

Gift returns arrive after the holidays. The agent answers the window, the condition rules, and how to start a return, from the policy you wrote in November. A person approves exceptions and sends refunds.

This is also the week to record next year’s forecast inputs. Write down three numbers: orders from November 23 to December 6, conversations for the same dates, and the number of handoffs. Divide conversations by orders. Next October, that is your contact rate, and you will not need a benchmark.

Getting the store ready this year

If you want an agent to answer the policy questions on your store, SupportHQ answers from your pages, replies in the customer’s language, and hands off order questions with a summary. See how it works for ecommerce stores. Starter is $29/month with 2,000 conversations and no fee per resolution, so the 324-conversation example fits with room to spare. The 7-day trial needs a card. Start by November 9 to leave a full week for testing: start your free trial.