DEV Community

Rickard Collander
Rickard Collander

Posted on Originally published at supportifier.se

Onboarding Seasonal Support Staff Before Black Week

Black Friday falls on 27 November this year. If you're bringing in seasonal staff for customer service, they need to be ready well before then. Hiring is rarely the hard part. The hard part is that new people have to answer customers within a couple of weeks, in an inbox where the easy questions are already gone.

Why training is harder than it used to be

Self-service and AI have taken away the easy tickets new agents used to learn on. A few years ago a newcomer started with order status and opening hours and built confidence on a hundred simple tickets. Today those are resolved in the help centre and the chat, and what reaches the inbox is mostly exceptions. Gartner reports that 85 percent of service and support leaders are expanding agent responsibilities. The role is getting harder, even for someone who's only there for eight weeks.

So the goal can't be for a new person to know everything. They need to be able to find the right answer, recognise what kind of ticket it is, and know when to hand it on.

Day one: three things, the rest later

  1. Finding the answer. Searching the knowledge base, understanding how an article is built, and trusting that it's current.
  2. Recognising the ticket type. The five to ten types that make up most of the inflow, and which article goes with each.
  3. Knowing when to hand over. A short, concrete list: complaints, compensation, threatening language, money above a set limit.

Product range, every system feature, policy exceptions and the phone can wait. The most common mistake is a week of sessions on everything, followed by the queue. Nobody remembers a policy they haven't used yet.

Make the knowledge base the working tool

New people should use the articles while answering, not read them in advance. Learning to find things takes a day. Memorising takes weeks. Four things make this work:

  • Reviewed, current answers to the most common questions: short answers, steps and exceptions, ideally in a searchable help centre your agents use too.
  • AI drafts they review and edit. The draft shows what a good answer looks like, and correcting it is the training.
  • Limited rights at first. Knowledge-Centered Service gives new colleagues a candidate role with limited rights until they're judged competent. Apply the same idea to replies, and let the first days' answers go via a colleague.
  • A clear way out. Say on day one that handing over isn't failing.

Coaching: short and often

The Consortium for Service Innovation links training plus coaching to large productivity gains. For a season, that might mean fifteen minutes every morning in week one, twenty minutes at the end of the day going through two real tickets, then half an hour a week. Give each new person a named coach, and take tickets off the coach's schedule. Coaching squeezed on top of a full queue doesn't happen.

Tickets a new person shouldn't take

The rule is about consequence, not difficulty:

Ticket type Who takes it
Complaints and faulty goods Experienced agent
Compensation and goodwill Experienced agent or team lead
Unhappy customer threatening to escalate Team lead
Contracts, invoices and payment Whoever owns the subject
Personal data and erasure A designated person

A technically fiddly ticket is fine for a newcomer. An easy-looking one where the answer binds the company for three years isn't.

How to tell they're self-sufficient

Track four numbers per person for the first weeks:

  • Share of tickets handed on. It should fall week by week. If it levels off high, you're probably missing an article, not a capable person.
  • Time to first reply, compared with the team average.
  • Share of AI drafts sent without changes. A steady rise means they trust the source material.
  • Customer satisfaction, read together with the comments, never as a ranking.

If the hand-on rate stalls on a few ticket types, a knowledge analysis of recurring questions and gaps can show which articles to write first.

Checklist

  • Count back from 27 November: two weeks of training plus a supported week puts the start in early November at the latest
  • Pick the five to ten ticket types they'll own, each with a reviewed article
  • Write a handover list of under ten lines
  • Name a coach per person and book the time
  • Let them answer for real on day two, with replies reviewed at first
  • Fix articles, not people, when the numbers stall
  • Ask the newcomers what was missing. They see the gaps more clearly than anyone

Originally published at https://www.supportifier.se/en/blog/seasonal-customer-service-staff-onboarding

Top comments (0)