30-60-90 day plan for customer service representatives
On this page
- The order of metrics matters
- Days 1-30: Training and nesting
- Days 31-60: Full queue, ramped targets
- Days 61-90: Consistency and a first contribution
- What "on track" looks like
- A filled example
- Running the weekly check-in
- What the team owes the new rep
- Common mistakes
- Adapting the plan
- Questions people ask
A customer service representative's ramp is shorter and more structured than most roles, which is exactly why a 30-60-90 day plan helps. The metrics already exist: quality scores, handle time, first-contact resolution, customer satisfaction, schedule adherence. What is often missing is a written ramp schedule that says which of those matter in which week, so the new rep is not held to a full-floor handle-time target while still learning the refund policy.
This plan is for a team lead or support manager bringing on a phone, chat or email representative in a contact center or support team. For a lighter, general example of a support hire, see the filled example in the 30-60-90 day plan template for new hires; this page goes further into the contact-center mechanics: training, nesting, QA and ramp targets.
The order of metrics matters
The most common mistake in a customer service rep's first 90 days is measuring speed before quality. A new rep who is pushed on average handle time in week three learns to shorten contacts: skipping verification, transferring early, promising a callback that nobody makes. The numbers look better and customers are worse off. The plan below introduces metrics in this order:
- Accuracy and compliance (QA score, verification steps, correct policy applied) from the first live contact.
- Resolution (first-contact resolution, reopen rate, escalation rate) from nesting onward.
- Customer experience (CSAT or post-contact survey scores) once the rep has enough contacts for the number to mean something.
- Efficiency (handle time, contacts per hour, after-contact work time, adherence) last, with a ramped target.
Days 1-30: Training and nesting
| Week | Focus | Checkable by end of week |
|---|---|---|
| 1 | Product, policies, systems (CRM, ticketing or telephony platform, knowledge base), security and privacy rules | Can find the answer to ten sample questions in the knowledge base unaided; passed any required compliance modules |
| 2 | Side-by-side listening or reading with experienced reps; role plays of the top contact types; practice in the system's training environment | Has observed at least a full shift of contacts; completed role plays for the five most common contact reasons |
| 3 | Nesting: live contacts on simple types only, coach nearby, reviewed often | QA scores on reviewed contacts at or near the passing mark; knows when and how to escalate |
| 4 | Nesting continues with more contact types added; first QA calibration with the lead | Handles the simple contact types without help; can explain the reason behind each QA deduction they received |
Day-30 bar: passing QA scores on a set number of reviewed contacts (for example, the last ten), correct verification on every contact, and escalations that are appropriate rather than a way to avoid difficult customers. Handle time is tracked but not targeted.
Days 31-60: Full queue, ramped targets
- Move to the full queue for the rep's assigned channels, with a named lead still reviewing a sample of contacts each week.
- Introduce ramp targets for handle time and contacts per hour, set at a written percentage of the team standard that rises every two weeks.
- Track first-contact resolution and reopen rate weekly; review every reopened contact with the rep.
- Add a second channel if the team is multichannel, such as chat after phone.
- Start schedule adherence tracking: logged in on time, breaks taken as scheduled.
Day-60 bar: QA scores stable at or above passing across all contact types, first-contact resolution close to team average, efficiency at the ramp target for the week, and adherence in line with team norms.
Days 61-90: Consistency and a first contribution
- Meet full team targets for quality, resolution and efficiency for at least two consecutive weeks.
- Handle the harder contact types: complaints, billing disputes, account security issues or whatever the team treats as tier two.
- Submit at least one improvement: a knowledge base article that was missing or wrong, a macro, or a pattern of contacts that points to a product or policy problem.
- Receive customer feedback directly: read their own survey comments with the lead and pick one behavior to change.
Day-90 bar: performing at team standard on the core metrics without extra supervision, handling tier-two contact types, and one knowledge base or process contribution accepted.
What "on track" looks like
| Checkpoint | On track | Worth a direct conversation |
|---|---|---|
| Day 30 | Passing QA on reviewed contacts; verification always done; asks for help at the right moments | Skipped verification steps; guesses at policy rather than checking; avoids live contacts |
| Day 60 | Meeting ramp targets; low reopen rate; adherence steady | Low handle time with high reopen or transfer rate, which usually means contacts are being cut short |
| Day 90 | At team standard for two weeks; handling tier-two contacts; a contribution accepted | Quality drops as speed rises; the rep still needs a lead to join most difficult contacts |
A filled example
Rep: Aisha Mensah (invented), phone and chat representative for an internet and TV provider's billing and account team.
Day 30: Finished two weeks of training and two weeks of nesting on bill explanations and payment arrangements. Passed QA on nine of her last ten reviewed calls; the miss was a skipped verification question, corrected the same day. Handle time was well above team average, as expected.
Day 60: On the full billing queue, meeting the week-eight ramp target for handle time. First-contact resolution close to team average. Her reopen rate was higher on promotional credits, and review showed she was applying an outdated credit rule from an old knowledge base article.
Day 90: At team standard for three weeks. Handling service-cancellation contacts. Rewrote the outdated credit article with the knowledge base owner, which removed a source of repeat calls for the whole team.
Running the weekly check-in
For customer service reps, weekly beats monthly. A 15-minute weekly check-in with the lead works best when it looks at real contacts, not just the dashboard:
- Listen to or read one contact the rep chose and one the lead chose.
- Look at the week's numbers against the ramp target for that week.
- Agree one specific behavior to work on next week, such as "summarize the resolution before ending the call."
Contacts chosen by the rep show what they think good looks like. Contacts chosen by the lead show what the rep has not noticed yet. Both matter.
What the team owes the new rep
- System access, headset and training environment working on day one.
- A written ramp schedule with the target for each week, shared before the first live contact.
- A knowledge base that is current, or a clear way to flag articles that are wrong.
- QA scoring that is calibrated across reviewers, so the rep's score depends on the contact, not on who reviewed it.
- Protection from overtime and schedule changes during nesting where possible.
Common mistakes
- Targeting handle time in the first month. It trains the wrong habits and hides quality problems.
- Skipping nesting when the queue is busy. Putting new reps straight onto a full queue usually costs more in repeat contacts and escalations than it saves.
- Giving feedback from the dashboard only. A number tells the rep something is wrong but not what to change. Use real contacts.
- No path beyond the queue. Reps who show skill by day 90 and see no route to tier two, quality or training roles are more likely to leave early.
Adapting the plan
- Technical support: lengthen training and nesting, add a troubleshooting certification or a set of solved practice cases before live contacts, and delay efficiency targets until day 60 or later. Resolution and escalation quality matter far more than speed.
- Regulated contacts such as insurance, banking or healthcare: make the compliance and verification steps a pass-or-fail gate on every reviewed contact, not one line in a QA score, and keep a higher review sample for the full 90 days.
- Chat and email only: replace handle time with concurrency and response time, and review written tone and accuracy closely in nesting, since mistakes are saved and forwarded.
- Seasonal or peak hiring: compress the plan to 30 or 45 days, and be explicit about which tier-two contact types the rep will not be trained on before peak.
If you are hiring for these roles in volume, the high-volume hiring process covers how to keep screening consistent across many candidates, and the call center screening questions and interview questions for customer service mindset test for the patience and accuracy this plan measures once the rep starts.
Questions people ask
What is nesting for a customer service representative?
Nesting is the period after classroom training when a new representative handles real customer contacts in a protected setting: a smaller queue, simpler contact types, a coach or experienced agent nearby, and relaxed productivity targets. It bridges training and the live floor, and it is where most early quality problems show up and get fixed.
Should a new customer service rep be measured on handle time in the first 30 days?
Track it but do not target it. Pushing handle time down early teaches new reps to rush, transfer or end contacts before the problem is solved. Quality and resolution should come first; handle time usually falls on its own as product knowledge grows.
When should a new rep reach full targets?
That depends on the complexity of your contacts. Simple, high-volume queues may reach full targets within six to eight weeks, while technical or regulated support can take the full 90 days or longer. Write the ramp schedule into the plan so the rep knows the target for each week in advance.
Is a 90-day plan overkill for a customer service role?
For simple queues a 30-day plan may be enough to see whether the hire works out. A full 90-day plan earns its place where contacts are varied or technical, where reps handle several channels, or where the company wants reps to grow into escalations, quality or training roles.