New support agent onboarding is one of the most consequential processes a support organization runs, and one of the most often left to chance. A new agent thrown into the queue on day two with a “just watch what the veterans do” approach might eventually become effective — or might develop bad habits, burn out from the uncertainty, and churn within six months. Both outcomes cost significantly more than an investment in structured onboarding.

A 30-60-90 day framework breaks the complexity into manageable phases with clear milestones.

What “full productivity” means

Before designing an onboarding program, define what it’s building toward. “Full productivity” should be a specific set of measurable criteria, not a vague sense that someone is “performing well.”

Reasonable full-productivity targets for a support agent at 90 days:

  • Handling 85% of the team’s average daily ticket volume independently
  • First Contact Resolution rate within 10 percentage points of team average
  • QA score at or above the team’s minimum threshold
  • Escalation rate within 20% of veteran agent rate
  • CSAT score within team range (requires sufficient ticket volume to be meaningful)

These targets give both the agent and their manager a clear picture of progress. They’re not ceilings — they’re the baseline the onboarding program is designed to reach.

Days 1–30: Foundation

The first month is not about tickets. It’s about giving the agent the foundation they need to handle tickets effectively.

Week 1 — Orientation and product immersion:

  • Company orientation (HR, tools, communication norms)
  • Full walkthrough of the product — not a sales demo, a hands-on tour from the agent’s perspective: what features exist, what they do, what commonly goes wrong
  • Introduction to the helpdesk platform: how to navigate, find tickets, use macros
  • Introduction to the knowledge base and internal documentation
  • Shadow 2–3 experienced agents, observing ticket handling in real time

Weeks 2–3 — Guided ticket handling:

  • Agent handles tickets independently but with a designated mentor reviewing every response before it’s sent
  • Focus on the top 20 ticket categories that make up 80% of volume
  • Daily 15-minute debrief with the mentor: what went well, what was uncertain, what should be done differently
  • Introduction to SLA policies, escalation criteria, and quality standards

Week 4 — Supervised independence:

  • Agent handles tickets independently; mentor reviews a sample (3–5 per day) rather than every ticket
  • Agent begins handling the most common ticket types without review
  • First formal QA review at end of week 4, reviewed with the team lead

End of month 1 checkpoint: Can the agent independently handle the top 5 ticket categories? Are they using macros effectively? Is their escalation rate within a reasonable range?

Days 31–60: Expanding capability

The second month builds breadth and confidence.

Weeks 5–7 — Expanding ticket types:

  • Gradually introduce more complex ticket categories: technical troubleshooting, billing disputes, account changes
  • Agent continues with mentor support but at a lighter touch — review happens after sending, not before
  • Specific coaching sessions on areas where QA revealed gaps
  • Introduction to escalation workflow: when to escalate, how to write a good escalation note, what the receiving team needs

Weeks 7–8 — Handling moderate complexity:

  • Agent handles all standard ticket types independently
  • Complex or unusual tickets get mentored review
  • Agent participates in team meetings and QA calibration sessions
  • Introduction to customer context on key accounts (if your org maintains account briefs)

End of month 2 checkpoint: Is the agent meeting first response SLA consistently? Is FCR trending upward? Are QA scores improving from month 1? Any specific knowledge gaps that need targeted coaching?

Days 61–90: Independence and refinement

The third month is about reaching full productivity and beginning the feedback-driven improvement cycle that will continue throughout the agent’s tenure.

Weeks 9–11 — Full independence:

  • Agent handles all ticket types independently, with standard QA review process (no special monitoring)
  • Weekly 1:1 with team lead focuses on performance data and development goals
  • Agent joins any specialist or product-area rotation they’ll be part of
  • First formal 90-day performance review against the full-productivity criteria defined at the start

Week 12 — Calibration and development planning:

  • Full 90-day review: performance vs. targets, specific strengths, specific development areas
  • Development plan for months 4–6: what will the agent focus on improving?
  • Transition from “onboarding” to “ongoing development” — the agent is now a full team member with the same feedback cadence as everyone else

Building the support materials

Effective onboarding requires materials that exist and are current:

  • Product tour guide: A self-paced walkthrough document covering the product from a support perspective, including common failure modes
  • Top 20 ticket type playbooks: One-page guides for each high-volume ticket type covering diagnosis, resolution steps, and escalation criteria
  • Escalation decision tree: Visual guide to when and where to escalate
  • QA scorecard and examples: The scoring criteria with annotated example tickets — one excellent example and one below-standard example for each key criterion

These materials serve double duty: they support new agent onboarding and they capture institutional knowledge for every subsequent hire.

Why the mentor relationship matters

Formal onboarding programs without a mentorship component produce agents who know the policy but not the judgment. A mentor provides:

  • A safe place to ask questions that feel “too basic” to ask the whole team
  • Real-time feedback that connects general principles to specific situations
  • An introduction to the team’s culture and norms that documentation can’t convey

The mentor should be a senior agent, not the team lead. Team leads carry a management dynamic that can inhibit honest questions from a new hire who’s trying to make a good impression.

Investing 90 days in structured onboarding, when done right, returns multiple years of productive performance. The agent who reaches full productivity in 10 weeks instead of 20 delivers 10 additional weeks of full-capacity work in their first year alone — and is significantly more likely to still be on the team at year two. AI-first support platforms like AItocha CX can accelerate ramp time by surfacing similar past tickets and suggested responses during an agent’s first weeks.