Support Agent Onboarding Checklist
A support agent onboarding checklist: helpdesk access, product training, tone and macros, shadowing, first tickets with review, and a 30-day quality check.
- Typical schedule per new support agent
- The checklist 5 sections, 19 items
- Variables
{{agent_name}}{{mentor}}
Use this checklist when a new person joins the support team, whether full-time, part-time or as an outsourced agent. It covers the first weeks: tools, product knowledge, how the team writes, and a controlled path to handling tickets alone. General company onboarding and IT setup happen in their own checklists.
Who owns it
The support lead owns the run. A named mentor, an experienced agent, handles the shadowing and reviews the first replies. The new agent completes the items marked for them, so the run doubles as their personal onboarding plan.
Common pitfalls
- Straight into the queue. Agents who answer tickets before they know the product guess, and customers notice. Shadow first, then draft replies for review, then go solo.
- Training on features, not on problems. Customers write about problems, not features. Train with real, recent tickets grouped by the most common issues.
- No written tone guide. "Just be friendly" produces wildly different replies. Share examples of good replies and the team's macros.
- Hiding the escalation path. New agents either escalate everything or nothing. Show them exactly when and how to escalate, and to whom.
- Admin rights too early. Helpdesk admin, refund and account deletion rights should come after the first weeks, not on day one.
Starting one run per new agent makes onboarding consistent. Each mentor follows the same plan, and the lead can see where every new hire stands.
The checklist: Onboard support agent {{agent_name}}
Before day one
-
Mentor
{{mentor}}assigned, with time blocked for shadowing and reviews -
Helpdesk account created with an agent role, not admin
-
Access to the knowledge base, internal docs and the team chat channels
-
Demo or test account in the product created for
{{agent_name}}
Week one: learn
-
Product walkthrough completed, using the demo account to do what customers do
-
Top ticket categories reviewed with real examples from the last months
-
Tone and style guide read, with examples of good and poor replies
-
Macros and saved replies reviewed, including when not to use them
-
Escalation path explained: triggers, owners and how to hand over a ticket
-
Data protection basics covered: identity checks and what never to share by email
Week two: practise
-
Shadowed
{{mentor}}for at least two full shifts -
Drafted replies to real tickets for
{{mentor}}to review before sending -
Handled live chat or phone with
{{mentor}}listening in optional -
Fixed or flagged one outdated knowledge base article
Go solo
-
Handling a normal ticket load, with a sample of replies reviewed each day for the first week
-
Added to the shift schedule and the on-call or weekend rotation optional
-
Refund, credit or account change permissions granted where the role needs them optional
30-day check
-
Quality review of a sample of tickets done with the support lead
-
Feedback on onboarding collected from
{{agent_name}}and this template updated
Checklist as Markdown
Frequently asked questions
How long does it take to onboard a customer support agent?
For most SaaS products, plan a week of learning and a week of supervised practice before an agent handles tickets alone. Complex or technical products take longer. Use a quality review of real tickets, not a date, to decide when someone is ready.
What should customer service training include?
The product, the most common customer problems, the team's tone and macros, the escalation path, and data protection basics such as identity checks. Practise on real tickets with a mentor reviewing the replies. Shadowing an experienced agent teaches more than any slide deck.
Should new support agents use macros?
Yes, but as a starting point. Macros keep answers accurate and consistent, but customers notice when a reply does not address their actual question. Teach new agents to personalise each macro and to flag macros that are outdated.
Updated