how to onboard a new support agent in one week

TL;DR

A new support agent can take real tickets by day 3 and work a normal queue by day 5 if the week is structured right. Days 1 to 2: product, tools, and shadowing. Day 3: first real tickets with a buddy reviewing every reply. Days 4 to 5: growing independence with spot checks. The whole plan hinges on two things: a buddy who reviews everything early, and real tickets as soon as possible. Nobody learns support from docs alone.

The query

how to onboard a new support agent in one week

Use this when

• A new agent starts Monday
• Onboarding currently takes a month and you want it faster
• You need a repeatable onboarding checklist
• New agents feel lost or take too long to ramp

Not for

• Engineering or product onboarding
• Hiring managers or team leads
• Training AI support agents
• Part-time or contractor onboarding (compress further)

Steps

1. Day 1: product and tools, no tickets

Morning: the product from a user's perspective, sign up and use it like a customer. Afternoon: the ticketing tool, the knowledge base, macros, and where to ask for help. End of day: they can log in everywhere and know who their buddy is.

Expected output: accounts working, buddy assigned, first shadowing session booked.

2. Day 2: shadow everything

Sit with the buddy (or screen-share) through a full ticket flow: triage, reply, escalation, close. Then reverse: the new agent drives while the buddy watches and narrates. Cover the top 10 ticket types.

Expected output: the new agent has seen the full lifecycle of at least 10 real tickets.

3. Day 3: first real tickets, every reply reviewed

Assign easy, well-documented ticket types. The buddy reviews every reply before it sends. Expect slowness, that is fine, accuracy is the goal.

Expected output: 5 to 10 real tickets handled, zero sent without review.

4. Day 4: wider ticket types, spot-check reviews

Open up the full queue but keep the buddy reviewing a sample, every third reply or the tricky ones. Introduce escalations: how to write one, who to send it to.

Expected output: the agent handles varied tickets with decreasing supervision.

5. Day 5: normal queue, buddy on call

Full queue participation. The buddy is available for questions but not reviewing by default. End of day: a 30-minute retro on the week, what was confusing, what docs were wrong.

Expected output: an agent working the real queue, with a list of onboarding gaps to fix for the next hire.

6. Week 2 safety net

Keep the buddy relationship for two weeks. Daily 10-minute check-ins for the first week, then as needed. Review their CSAT and handle time at day 10 and day 30.

Expected output: a monitored ramp with quality gates, not a cliff.

Variant phrasings

support agent onboarding checklist

Days 1 through 5 above, as a checklist. Print it, check boxes, hand it to the buddy.

how to train a new customer support rep fast

Speed comes from real tickets on day 3, not from more docs. Shadowing plus buddy-reviewed real work beats any training module.

new support hire first week plan

Same schedule. Adjust the ticket difficulty per product complexity, but keep the day-3 first-ticket rule.

Why it happens

Long onboards fail because they front-load information and delay practice. People forget 90 percent of what they read on day 1 and remember what they did on day 3. The one-week plan works because it flips the ratio: just enough context to be safe, then real tickets with a safety net. The buddy is the whole system, without one the week falls apart.

Edge cases

• Complex technical products: extend to two weeks, but keep the structure. Day 3 first tickets still applies, just pick simpler ticket types.
• Remote onboarding: schedule the shadowing explicitly, it wont happen by osmosis. Screen-share sessions, not "ping me if you need anything."
• Experienced hires from other companies: compress days 1 to 2 into one day, they know support, they need your product and your tools.
• The buddy is too busy: then you dont have an onboarding plan, you have a hope. Protect buddy time like any other capacity commitment.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_zs6YkVzieAszbDhyUdHOjg