For most shops, cafés, venues and gift businesses, the run-up to Christmas is not one busy period. It is six weeks of the same fifteen questions, asked at every hour, by people who are more stressed than usual and have less patience for a slow answer.
"Will it arrive by the 24th?" "Can I return it if they do not like it?" "Do you do gift wrapping?" "Are you open on the 27th?" None of these is hard. Together, at volume, they swamp whoever is also packing orders, serving customers and running the till.
Good holiday season customer service is mostly decided in October. By December you are executing a plan or improvising one.
The questions that will come, in roughly the order they arrive
Peak season enquiries follow a fairly predictable arc. Knowing the order lets you prepare answers before each wave rather than during it.
| Period | What people ask | Where the answer should live |
|---|---|---|
| Early to mid November | Gift ideas, stock availability, gift cards, private bookings for parties | Product pages, gift guide, events page |
| Late November | Delivery options, express shipping costs, Black Friday terms | Delivery page, banner on every page |
| First half of December | Last order dates, click and collect, gift wrapping, extended returns | One dedicated "Christmas info" page |
| The last week before | "Will it still arrive?", order changes, where is my parcel | Delivery page plus a person for order-specific issues |
| Christmas to New Year | Opening hours, returns and exchanges, faulty gifts, vouchers | Hours page, returns page |
| Early January | Refund timing, sale items, "you said you were open" | Updated hours and returns content |
Hospitality runs a parallel pattern: party bookings and group menus from October, deposits and dietary questions in November, then opening hours and New Year availability.
Put the answers in one place, then everywhere
The most common failure is not a missing answer. It is five slightly different answers. The banner says order by the 18th, the delivery page still shows last year's 19th, and the email footer says nothing.
Make one page the source of truth for the season: cut-off dates by delivery method, holiday returns window, gift options, and the full list of changed opening hours. Then point everything else at it.
If you run a website assistant, this page is also what it should answer from. SpideyChat can re-crawl your site or take an uploaded document, so update the page first and re-ingest it, rather than typing dates into several places by hand. Keeping your chatbot's knowledge up to date covers the habit that makes this painless.
A worked example for staffing the gaps
Guessing peak volume leads to either a panicked December or a paid temp with nothing to do. A rough calculation is better. Replace these example numbers with your own.
Say a gift shop normally receives 60 enquiries a week across email, social messages and website chat. Last December, looking back through the inbox, it was closer to 180 a week for the three peak weeks.
- Sort a sample. Take 50 of last December's enquiries and tag them. In this example, 34 were questions answered somewhere on the website (delivery dates, returns, hours, wrapping) and 16 needed a person (order problems, custom requests, complaints).
- Scale it up. 180 a week at that ratio is roughly 122 routine and 58 that need a person.
- Time the human share. If each of those 58 takes about six minutes, that is under six hours a week of real customer service work.
- Decide what covers the rest. The 122 routine questions are the ones worth answering automatically from your content, especially the ones that arrive after closing when gift shoppers browse.
The point of the sum is the split. Six hours of human work is a manageable addition to one person's week. Eighteen hours of mixed questions is not. The chatbot ROI calculator lets you run the same arithmetic on your own figures.
The evenings and weekends matter more in December
Gift shoppers browse after work, after the children are in bed, and on Sunday nights. Those are exactly the hours the shop is shut. A customer who cannot find the last order date at 9pm on 15 December will order from whoever shows it clearly.
That is where an always-on assistant earns its keep during peak. It can confirm the cut-off, explain the returns extension, say whether gift receipts are available and capture anything order-specific for the morning. It cannot see your courier's tracking or change an order unless you have connected it to something that can, so be clear in the content about what it will pass on. For the weekend pattern in particular, see the weekend enquiry problem.
Things that go wrong, and simple guards
- Expired dates. Put a reminder in the diary for the day after each cut-off to update the page. "Order by the 18th" on the 20th sends a flood of angry messages.
- Order-specific promises. Neither staff nor an assistant should confirm a parcel will arrive without checking tracking. Content should say "we will check your order and reply" instead.
- Returns confusion. If you extend returns for Christmas gifts, write the exact rule, including the final date and whether a gift receipt is needed.
- Hospitality double bookings. Party booking requests captured in chat are requests, not confirmed tables. Say so in the reply and confirm from your booking system.
- January hangover. Seasonal content that stays live into February makes the business look careless. Schedule the clean-up.
For bank holidays that fall inside the season, bank holiday enquiries has a closure checklist worth borrowing.
What to do in the next fortnight
Open last year's December inbox and tag fifty enquiries. Write the one seasonal information page with every date and rule on it, publish it hidden or as a draft, and get someone who did not write it to find the answers.
Then decide your staffing from the split, not from memory. If the routine share is large and much of it arrives after hours, set up an assistant on that page by October at the latest, so you have November to watch its unanswered questions and fill the gaps before the real surge.