New Support Agent Onboarding Playbook

The first week is about context, not performance. New agents need to understand your product, your customers, and your culture before they touch a single ticket.

Day 1-2: Product deep dive. New agents should use your product as a customer would. If you sell software, they set up an account and complete onboarding. If you sell physical products, they receive and inspect sample items. First-hand experience creates the empathy that second-hand knowledge never will.

Day 3-4: Support tool training. How to navigate the inbox, assign tickets, use templates, escalate, and add internal notes. Don't rush this. Agents who are slow in the tool are slow with customers. Practice with mock tickets, not real ones.

Day 5: Observation. The new agent shadows an experienced agent for a full shift. They read conversations in real time, see how the experienced agent thinks, and ask questions between tickets. This is the most valuable day of Week 1.

Week 2 is supervised ticket handling. The new agent responds to real tickets, but every response is reviewed before it reaches the customer.

Start with the easiest ticket types: simple questions that have clear template answers. As the agent demonstrates competence, gradually introduce more complex scenarios. By Day 10, they should handle your top 10 ticket types without significant revision.

The buddy system is critical here. Assign one experienced agent as the new hire's buddy. The buddy reviews all responses for the first 3 days, then spot-checks 50% for the remaining 2 days. The buddy is not a manager — they are a peer mentor who provides real-time coaching.

Track metrics from Day 1 but don't evaluate against them yet. You want a baseline, not a judgment. Response quality matters more than speed in Week 2.

Week 3 is when the training wheels come off. The agent handles tickets independently with minimal review.

The buddy checks 20% of tickets randomly instead of reviewing everything. The focus shifts to edge cases and decision-making. When should the agent escalate vs. attempt resolution? When should they offer a discount vs. hold firm? These judgment calls require practice with a safety net.

Introduce the full range of ticket types by Day 12. The agent should encounter (and handle) their first genuinely angry customer, their first technical escalation, and their first policy ambiguity this week. Debrief after each new scenario.

By end of Week 3, the agent should be handling tickets at about 70% of the team's average speed with 90%+ quality. Speed will continue improving through Week 4 and beyond.

Week 4 is about reaching team average performance and integrating into the team's rhythms.

The agent should now participate in team meetings, contribute to template improvement discussions, and take ownership of their performance metrics. Move from buddy review to standard QA processes (same review cadence as any other agent).

Focus on speed optimization. Most quality issues are resolved by Week 3. Speed improves through tool fluency and pattern recognition. Teach keyboard shortcuts, template organization, and workflow tricks that experienced agents use.

Conduct a formal Week 4 review. Compare the agent's metrics against the targets set at hiring. Discuss strengths, areas for improvement, and a 30-60-90 day growth plan. Celebrate wins — getting through the first month of support is genuinely hard.

You need data to know if your onboarding program works. Track these metrics for every cohort:

Time to first independent ticket (target: Day 6-8). Time to team average quality (target: Day 15-20). Time to team average speed (target: Day 20-30). 30-day retention (target: 90%+). 90-day CSAT compared to team average (target: within 5 points).

Compare cohorts to identify trends. If agents consistently struggle with specific ticket types, your training material for those topics needs improvement. If time-to-independence is increasing, your product complexity may have outpaced your training program.

Survey new agents at Day 30: What was most helpful during onboarding? What was missing? What would you change? Their feedback improves onboarding for the next cohort.

If you onboard more than 2-3 agents per quarter, ad-hoc training does not scale. You need a system.

Document everything the buddy teaches verbally. If an experienced agent explains a workflow during a shadow session, that explanation should become a written guide. Over time, your onboarding documentation should be comprehensive enough that a new agent could self-serve 80% of their learning (though the buddy system remains essential for the other 20%).

Create a certification process. Define the 20 ticket types every agent must handle correctly before going independent. New agents work through these as a practical exam during Week 2, with the buddy verifying competence.

Version your onboarding program. When products change, processes change, or new channels are added, the onboarding material must update too. Assign one person to own onboarding content — if everyone owns it, no one updates it.