Onboarding that gets a new rep to competent in 30 days
The easy tickets new reps used to learn on are gone — here's a week-by-week ramp that gets a hire to competent on the hard stuff in 30 days.
The two-week-old rep who's been left to sink
Your newest hire finished the induction slides on Friday, shadowed a senior rep for three days, and on Monday she has her own queue. By Wednesday she is drowning — reopening her own tickets, escalating things she should be able to close, and quietly deciding this job might not be for her. Nobody planned for her to fail. There just wasn't a plan at all past week one.
Onboarding is the part of the job most teams improvise, and it's the part with the least room to. The ramp is where a rep decides whether to stay, and it's where the easy version of the job has quietly disappeared.
Why 30 days is harder than it used to be
The old ramp had a grace period baked in: a new rep could spend a month on password resets and "where's my order" while the muscle memory formed. Automation ate that runway. The routine contacts a beginner used to cut their teeth on now get deflected before a human sees them, and what reaches the queue is the residue — the ambiguous, multi-system, already-annoyed cases.
So the target hasn't just moved, it's moved uphill. "Competent in 30 days" now means competent at the hard stuff, because the easy stuff isn't there to practise on. A ramp built for 2018's ticket mix will produce a rep who can handle a queue that no longer exists.
And the clock matters, because the ramp window is also the walk-out window.
The people you are onboarding are, statistically, the ones most likely to be gone by spring. A vague, sink-or-swim ramp doesn't just slow them down; it's the single most controllable reason they leave.
A 30-day structure that actually ramps
The fix isn't more content. It's a curve — a deliberate, week-by-week increase in what the rep owns, with the safety net removed one strand at a time.
Week 1 — Foundations, on real tickets. Product, tools, and where the answers live. But not in the abstract: from day two, have the new rep resolve real, already-closed tickets as exercises, then compare their answer to what actually happened. Reading closed tickets is the fastest way to absorb how your team actually talks and what "good" looks like. A strong knowledge base carries this week; a bad one leaves them memorising instead of finding.
Week 2 — Supervised live. They take real contacts, but every response is reviewed before it sends, and a named buddy — one person, not "the team" — is on the hook for their questions. The goal is volume of reps at bat, not volume of tickets closed. Expect handle times to be terrible. That's the point.
Week 3 — Owning the queue, net still up. They run their own queue at reduced volume, sending without pre-review but with same-day feedback on a sample. This is where a QA rubric earns its keep: it turns "you're doing fine" into specific, repeatable behaviours the rep can actually practise.
Week 4 — Competent, sustainably. Full ownership of a normal queue for their tenure, coached on outcomes rather than speed. Competent doesn't mean fast; it means resolving the ordinary case without help and knowing which rare one to escalate.
Competent doesn't mean fast. It means resolving the ordinary case without help, and knowing which rare one to escalate.
What shortens the ramp — and what quietly lengthens it
The accelerators are boring and reliable: a genuinely usable knowledge base, one named buddy instead of a diffuse "ask anyone," feedback measured in hours not weeks, and practice on real cases from day two. None of it is expensive. All of it is skippable under queue pressure, which is exactly why it gets skipped.
The thing that lengthens the ramp is the one most managers reach for first — an aggressive ramp target that treats week two like week ten.
Set a fake curve and you teach the rep to fake the numbers: rushed closes, premature escalations, tickets marked resolved that boomerang next week. You get a worse ramp and a rep who has learned that the metric matters more than the customer.
The other silent tax is stress. The job is heavy before you add the disorientation of being new.
A rep white-knuckling through week two isn't learning; they're surviving, and survival doesn't compound into competence. Protecting the ramp — realistic targets, a real buddy, permission to be slow — isn't a perk. It's the difference between a rep who's productive in a month and a seat you're rehiring in six.
Thirty days to competent is achievable, but only as a designed curve, not an induction packet and a shrug. Define "competent" with a QA rubric that predicts outcomes, and make sure the knowledge base your new reps lean on isn't where answers go to die.