Support load during peak, and the content that reduces it

Pull last year's peak tickets and sort them by what the customer was actually asking. The distribution is unglamorous and consistent: where is my order, will it arrive by a particular date, can I change or cancel it, can I return or exchange it and by when, and why is the amount I paid different from what I expected. A long tail of product-specific questions sits underneath, but the top of the list is the same across almost every store we see.

That consistency is the opportunity. A volume you can predict is a volume you can design against, and the design work is content rather than headcount. The question to ask of each category is not "how do we answer this faster" but "why did this person have to ask".

Usually the answer is that the information exists somewhere — in a policy page, in a carrier's system, in the order record — and was not present at the moment the customer needed it.

A help centre is where answers go to be filed, not where they go to be read. A customer deciding whether to order a gift on the 19th is on a product page, and that is where the delivery cut-off has to appear. A customer worried about sizing is on a product page too, not searching your knowledge base for a size guide.

So the deflection work is mostly relocation. The delivery promise belongs on the product page, with the date stated rather than a shipping speed the customer has to convert into one. The returns window belongs next to the add-to-cart button during gifting season, not solely on a policy page in the footer. The cut-off dates belong in a site-wide banner from the point they become urgent, and in the confirmation email of every order placed near them.

The test is blunt: for each of your top five ticket categories, name the page where the customer is standing when the question occurs, and check whether the answer is visible on it without a click. Most stores fail that test on four out of five.

"Where is my order" is usually the largest category by some distance, and it is generated by silence. Between dispatch and delivery, the customer knows nothing unless you tell them, and during peak that gap is longer and more anxious than usual.

Three things close it. A tracking link that is present in the dispatch notification and on the order status page, rather than only in an email somebody has to find. Proactive messaging when something slips — a delay email you send first is a fraction of the cost of the ticket the customer raises second, and it reads as competence rather than failure. And a realistic promise at the point of purchase, because most WISMO tickets are really "this is later than I was led to expect", which is a promise problem wearing a logistics costume.

If you are going to add one thing this year, make it the proactive delay email. It requires no new tooling in most stacks, it is written once, and it converts an angry inbound contact into an informed customer.

Two platform details decide how much January support work your November creates.

The first is timing. Shopify documents that changes to return rules apply only to future orders, so that they do not affect customers who have already ordered. An extended festive returns window therefore has to exist before the gift orders are placed. Decide it in October, publish it, and it answers itself; decide it in January and every affected customer has to ask.

The second is availability. Shopify documents return and cancellation rules covering the return window and its start point, return shipping costs and an optional restocking fee, plus the ability to mark items final sale — but self-serve returns and cancellations need to be turned on for customers to raise them from their accounts. Left off, every return is a conversation. Turned on, with a policy stated in the same words on the product page, the confirmation email and the returns flow, most of them are not.

Write the policy in plain language and repeat it verbatim in all three places. Half the returns tickets we see are not requests at all — they are customers asking you to confirm what your own policy means, because two pages on the site word it differently.

Content removes the avoidable contacts. What remains still needs handling, and two hours of preparation makes the rest of the season cheaper.

Update your auto-reply so it states current dispatch times and links the cut-off page — it is read by everyone who contacts you and is usually still describing October. Rewrite the top ten macros in the same voice and with this year's dates, since stale macros are how a template ends up telling a customer about last season's window. Put the three most common questions directly above the contact form, where they are read by exactly the people about to ask them. And agree in advance which categories get triaged first when the queue is long: anything affecting an order that can still be stopped, anything involving money already taken, everything else after.

Buying a chatbot in November. It needs the same content you have not written yet, plus configuration and tuning, and the version that ships under time pressure typically adds a step in front of the queue rather than shortening it. If you want one, buy it in the spring and feed it the answers you wrote this autumn.

And deflection that hides the way through. Removing the contact link, burying the email address, forcing a form nobody can complete — these reduce ticket counts and increase refunds, chargebacks and public reviews, all of which cost more than the conversation. The aim is that fewer people need to contact you, not that fewer people can. Keep the route visible; make it unnecessary.

• Shopify support and store management
• Support volume as a product signal
• The delivery promise, and the date that changes conversion