Peak season breaks support in a predictable way. Volume climbs faster than headcount, response times stretch, and the team spends December handling complaints that started as simple questions in November.
The businesses that get through it well are not the ones that hired hardest in October. They are the ones that reduced the questions before the questions arrived.
Start with last year’s tickets
Before planning anything, pull your tickets from the same period last year and sort them into categories. Almost every business finds the same shape: a small number of question types make up the majority of peak volume.
Typically it is some version of these:
- Where is my order, and will it arrive before the holiday
- Can I change or cancel something I just bought
- What is your return window for a gift
- Is this in stock, and which size or variant should I pick
That distribution is your plan. Everything below follows from it.
Remove questions before adding people
Shipping status is usually the single largest category, and most of it is avoidable. Proactive notifications at dispatch and at delivery, with a tracking link that works, remove a large share of it outright. A visible cut-off date for holiday delivery removes much of the rest.
Extend and publish your gift return window before peak rather than negotiating it one ticket at a time in January. Put it where people look: the product page and the checkout, not only the policy page.
Every question you prevent this way is one you do not need to staff for, and prevention scales in a way that headcount does not.
Decide coverage from when people actually buy
Peak buying is concentrated in evenings and weekends. If your support hours are weekdays nine to five, you are absent during your highest-intent traffic, and pre-purchase questions are the ones with direct revenue attached.
Look at your order timestamps by hour and day, then set coverage against that curve rather than against office convention. For most brands this means weekend cover and later evenings from mid-November.
Prepare people early, not in the busiest week
Whoever handles extra volume, in-house or outsourced, needs ramp time. Onboarding someone during the busiest week of the year costs more than it saves, because your experienced people stop answering customers to train the new ones.
- Six weeks out: categorise last year’s tickets, decide coverage hours, line up whoever is helping.
- Four weeks out: update macros and help content for the top question types. Publish cut-off dates and the gift return policy.
- Two weeks out: extra people trained and answering real tickets at normal volume, so peak is not also their first week.
- During: check the queue daily for new question types. A spike in something unexpected usually means a broken page or a shipping delay you have not heard about yet.
Write the escalation rules down
Peak is when edge cases arrive in volume: a parcel lost in transit, a gift needed by a specific date, a duplicate charge. If the rule for each is in one experienced person’s head, that person becomes the bottleneck for the entire queue.
Decide in advance who can issue a refund without approval, up to what value, and what happens when a delivery promise is going to be missed. Written rules let the whole team move at once, which is the entire point of preparation.
The short version
Look at last year’s tickets, remove the top question types at the source, set coverage against when people actually buy, and have any extra help trained and working before the peak rather than during it. Preparation beats headcount, and it is cheaper.
If you want extra coverage through your peak without hiring permanently, tell us your dates and expected volume and we will put a plan together.
