Training Staff to Handle Peak Trading Periods

Start Earlier Than Feels Comfortable

For most independent online retailers in the UK, peak trading isn't a single day. It's a rolling stretch that runs from the Black Friday weekend through to the January sales, with bank holiday weekends and flash promotions scattered along the way. If you're bringing in temporary staff, the training that saves you happens ten to fourteen days before the first spike, not on the morning it arrives.

The reason is simple: most peak problems aren't caused by workload, they're caused by indecision. A temp doesn't know whether to refund a £6 delivery charge, replace a missing item without asking, or promise a pre-Christmas arrival date. Every one of those hesitations creates a queue, and the queue creates a frustrated customer who emails again. Your training goal isn't to teach people everything about your business. It's to help them make safe decisions without hunting for someone to ask.

Write One Page Per Role, Not a Manual

Nobody reads a forty-page handbook during a busy shift. Build a single-page playbook for each role you're filling — customer service, pick and pack, dispatch admin — and shape it around the three questions that role will actually face that week.

• Write in short, direct sentences: "Check the order number, then open the order in the admin panel."
• Use a three-column layout headed Do this, Ask first and Never do this. This gives people a fast answer about their own boundaries.
• Include screenshots of the screens they'll use, with the exact buttons highlighted.
• State the current dispatch cut-off time and the delivery promise you're making to customers — and update it the day before launch if anything changes.
• Print and laminate it, pin a copy by each workstation, and post the same page in your team messaging channel so it's findable on a phone.

Rehearse the Awkward Conversations

New team members rarely struggle with "thank you for your order". They struggle with the difficult ones. Set aside fifteen minutes in pairs and run through five scenarios out loud: where is my order, an item arrived damaged, the customer typed the wrong address, a discount code didn't apply, and a return arriving outside the stated window.

Teach a four-step pattern they can lean on: acknowledge, explain, act, give a timescale. Then give them the exact wording for the things they can't do. "I'm not able to approve that refund myself, but I've passed it to Priya, who will reply before 5pm today" is far better than a vague promise or silence. Ask them to log the outcome on the order record so the next person doesn't start from scratch.

Give Every Temp a Named Contact

"Email the team inbox if you're stuck" is not support. Every temporary team member should know one person by name for their first three shifts, plus a named shift lead for every hour you're trading.

• Post a simple rota on the wall: name, role, hours, and who covers lunch and the late shift.
• Build an escalation ladder with clear colours. Green means decide alone — resending a tracking number, correcting a typo in an address. Amber means check with the shift lead — replacement items, partial refunds under a set limit. Red means the lead handles it — chargebacks, threats of legal action, suspected data issues, anything involving the press.
• Agree a response time for escalations, and stick to it. Twenty minutes of silence during peak feels like an hour to someone under pressure.
• Cover gaps before they open: who is the named contact between 6pm and 9pm, and at the weekend?

Hold the Standard When the Queue Is Longest

Service standards don't hold because people care more in December — they hold because you've made the standard achievable and visible. Publish a peak service promise on your site, such as a 24-hour reply window, and make sure the whole team knows it. A realistic promise kept beats an ambitious one broken.

Run a ten-minute huddle at the start of each shift: yesterday's volume, today's blockers, one thing that went well. Spot-check around ten customer conversations a day and feed back quickly, praising specifically — "the way you explained the courier delay and gave a new date was exactly right" teaches far more than "good job". And protect breaks. Tired people approve refunds they shouldn't and miss details on addresses, which costs you twice.

Keep What Worked

In the second week of January, sit down with your temporary team while the memory is still fresh. Ask which parts of the playbook were wrong, which scenarios actually came up, and which contacts they never managed to reach. Then update the documents and file the scripts, escalation names and practised scenarios into a single peak folder.

Do that once and next year's preparation becomes a matter of refreshing dates and volumes rather than rebuilding from nothing. Your returning temps will recognise the playbook, your regulars will trust the process, and your customers will never know how close to the edge you came.