30-60-90 day plan for customer service managers
On this page
- What makes a customer service manager's first 90 days different?
- Which rules does a new customer service manager check?
- What does the 30-60-90 day plan look like?
- Which metrics belong in the baseline?
- How should a hiring manager use the plan in the final interview?
- What should each check-in cover?
- A filled example
- What does the hiring manager owe the new customer service manager?
- Common mistakes
- How do you adapt the plan?
- Questions people ask
A 30-60-90 day plan for a customer service manager should spend the first month learning why customers contact the team (by listening to calls, reading tickets and rebuilding the metrics from source data); the second month running the operating rhythm of forecasting, scheduling, quality calibration and coaching through team leads; and the third month delivering one fix that removes a cause of repeat or avoidable contacts, measured against the day-30 baseline. As of October 2026, the plan also checks a few rules that land on the manager: pay for agents' pre-shift system time, call recording consent and card data on calls.
This plan is for the head of customer operations, operations director or founder hiring a manager who leads team leads and agents on phone, chat, email or messaging. The agent's own ramp is in the 30-60-90 day plan for customer service representatives; this page is the manager's side.
What makes a customer service manager's first 90 days different?
A support team's numbers are mostly set by things the team does not control: product defects, billing errors, unclear policies, a website that sends customers to the phone. A new manager who only manages the queue (more agents, shorter handle times) treats symptoms. The useful work is finding which contacts should not happen at all and getting the owning department to fix the cause, while keeping service steady.
The second difference is scale. The manager works through team leads, so coaching quality and consistent quality scoring matter more than the manager's own skill on calls. The plan builds both.
Which rules does a new customer service manager check?
These are federal and industry examples that commonly affect support teams, current as of October 2026 and not legal advice. State wage, recording and consumer rules add more, so check with HR and counsel.
| Area | What it says | What the manager checks |
|---|---|---|
| Agent working time (DOL WHD Fact Sheet #64) | For non-exempt call center staff, the workday generally starts with the first principal activity, such as starting the computer to download work instructions and applications; rest breaks of usually 20 minutes or less count as hours worked; records must include pre-shift and post-shift work | Whether agents clock in before logging into systems, how short breaks are coded, and whether schedule adherence pressure leads to unpaid log-in time |
| Call recording consent | Federal law allows recording with one party's consent (18 U.S.C. 2511(2)(d)); some states require every party's consent | That the recorded-line message plays on every inbound and outbound path, including callbacks and transfers; our one-party consent states page lists the state rules |
| Card payments by phone (PCI DSS) | The PCI Security Standards Council's standard, which does not allow sensitive authentication data such as card verification codes to be stored after authorization | Whether card details are spoken on recorded calls, typed into notes or visible in screen recordings, and how recording is paused or masked |
| Exempt status of team leads (29 CFR 541.600) | The federal salary level for the executive, administrative and professional exemptions is $684 a week, plus a duties test; some states set more | Whether team leads who mostly take contacts are classified correctly; see exempt vs nonexempt for new hires |
What does the 30-60-90 day plan look like?
30-60-90 day plan — [Name], Customer Service Manager, [team]
Reports to: [name] Start date: [date]
Team: [N] team leads, [N] agents Channels: [phone, chat, email, messaging]
Hours: [e.g. 7 a.m.-9 p.m., 7 days] Sites: [office / remote / BPO partner]
Systems: [ticketing / CRM], [telephony], [workforce management], [QA tool]
DAYS 1-30 — Learn why customers contact us
Goals:
- Listen to calls and read tickets on every channel and shift,
including evenings, weekends and any outsourced partner
- Take a sample of contacts and code each by reason and by whether
it could have been avoided
- Reproduce the team's reported metrics from source data and write
down each definition
- Review QA forms and score [10] contacts alongside each team lead
- Compare the last [8] weeks of forecast with actual volume
- Meet team leads one-to-one and hold skip-level groups with agents
- Meet the owners of the top contact reasons (product, billing,
logistics, web)
- Check timekeeping, recording disclosures and payment handling
Deliverables by day 30:
- Metrics baseline with definitions
- Contact-reason breakdown with an owner for each top reason
Check-in: day 30
DAYS 31-60 — Run the rhythm through team leads
Goals:
- Weekly QA calibration with team leads until scores agree
- A coaching cadence for every agent, run by team leads
- A staffing plan built on the forecast, with intraday adjustments
- Choose one avoidable-contact fix with the owning department
- Update the knowledge base articles behind the top contact reasons
Deliverables by day 60:
- Calibration gap between scorers narrowed and tracked
- Fix agreed with an owner, a baseline and a date
Check-in: day 60
DAYS 61-90 — Remove a cause and report
Goals:
- Measure the fix against the day-30 contact-reason baseline
- Present a monthly customer insight report to leadership: what
customers contact us about and what would prevent it
- Plan hiring and training for the next peak
Deliverables by day 90:
- One measured reduction in a contact reason or repeat contacts
- Staffing and hiring plan for the next two quarters
Check-in: day 90 — full reviewWhich metrics belong in the baseline?
The measures below are examples. Each team defines them a little differently, so the first job is writing down how yours are calculated.
| Area | Example measures | What the new manager should be able to explain |
|---|---|---|
| Customer outcome | Customer satisfaction, first-contact resolution, repeat contacts within a set number of days | How resolution is measured and whether survey responses are representative |
| Speed | Service level, average speed of answer, abandonment, backlog age for email and tickets | Which intervals and days miss, and why |
| Efficiency | Average handle time, after-call work, occupancy, transfers | Whether handle time differences reflect skill, contact mix or system steps |
| Quality | QA scores and the spread between scorers | Whether two team leads would score the same contact the same way |
| Team | Schedule adherence, absence, attrition, time to proficiency for new agents | Where attrition clusters by tenure, shift or team lead |
Contact reasons are the measure most teams lack. Coding even a few hundred contacts by reason and by "could this have been prevented?" usually shows where the volume comes from more clearly than any dashboard.
How should a hiring manager use the plan in the final interview?
Give finalists the team size, channels, three months of headline metrics and one known problem, and ask for a short plan. Score it with the rubric in how to evaluate a 30-60-90 day plan in an interview. The call center screening questions cover the earlier screen. Questions that separate managers from senior agents:
- "Handle time is above target and leadership wants it down. What do you look at before you set a new target?"
- "Two team leads score the same call 20 points apart. What do you do?"
- "One contact reason is a product bug that engineering says is low priority. How do you get it fixed?"
- "Service level drops every Monday morning. Where would you start?"
Strong candidates ask about contact reasons and forecasting before they talk about agent performance, and they describe getting other departments to act with data rather than complaints.
What should each check-in cover?
| Checkpoint | Questions to ask | On track | Worth a direct conversation |
|---|---|---|---|
| Day 30 | "Why do customers contact us, and which of those contacts should not exist?" | Contact-reason breakdown with owners; metrics reproduced with definitions; every shift and channel observed | Baseline is a copy of the dashboard; no time spent listening; targets already changed |
| Day 60 | "How far apart are your team leads' QA scores now?" | Calibration running and narrowing; coaching logged; staffing plan built on the forecast | QA unchanged; the manager coaches agents directly and team leads are bypassed |
| Day 90 | "Which contact reason went down, and how do you know?" | One measured reduction; insight report used by another department | Improvements reported only as handle time cuts; no change at the source |
A filled example
Customer service manager: Jordan Reyes (invented), new manager of a subscription company's support team with four team leads and about 45 agents on phone, chat and email, plus an outsourced partner on weekends.
Day 30: Coded a sample of several hundred contacts and found that "where is my refund?" was one of the largest reasons, mostly because the refund email did not say how long processing took. QA scores from two team leads were consistently far apart. Agents on the early shift were logging into four systems before their scheduled start, unpaid.
Day 60: Moved the early shift's clock-in ahead of system log-in with HR's agreement. Ran weekly calibration on recorded contacts until the leads' scores converged. Agreed with billing to add the processing time to the refund email.
Day 90: Refund-status contacts fell against his day-30 sample after the email change, and the knowledge base article was rewritten to match. His first insight report led product to prioritize a fix for a login error behind another top reason.
What does the hiring manager owe the new customer service manager?
- Access in week one to the ticketing system, telephony reports, the workforce management tool and QA records, plus raw data, not only dashboards.
- Introductions to the leaders of product, billing and operations, with an expectation that they act on support's findings.
- The partner contract and service levels if any work is outsourced.
- Agreement on which metrics matter most, so the manager is not judged on handle time alone.
Common mistakes
| Mistake | Result | Fix |
|---|---|---|
| Managing handle time first | Rushed contacts and more repeat contacts | Baseline resolution and repeats before touching handle time |
| Skipping evenings, weekends and partners | The worst experience goes unseen | Observe every shift and partner site by day 30 |
| QA scores nobody trusts | Coaching arguments instead of coaching | Calibrate until scorers agree |
| Fixing only inside support | The same contacts arrive every month | Take the top reason to the department that causes it |
How do you adapt the plan?
- Technical or B2B support: add ticket backlog by severity, escalation to engineering and account-level reporting; the 30-60-90 day plan for customer success managers covers the account side.
- Regulated industries: add complaint handling and logging rules from the industry regulator to the day-30 checks.
- Hiring a training class soon: the interview guide for call center roles covers systems tests and scored call simulations for agent hiring.
Questions people ask
What should a new customer service manager do in the first 30 days?
Listen to calls and read tickets on every channel and shift, reproduce the team's metrics from source data, sample contacts to find the top reasons customers get in touch, review how quality scores are given, compare the staffing forecast with what actually happened, and meet each team lead and the departments that cause the most contacts. Changes to metrics or targets wait until the baseline is done.
Which metrics should a customer service manager own?
Usually a mix of customer outcome measures such as satisfaction and first-contact resolution, speed measures such as service level, abandonment and backlog age, efficiency measures such as handle time and occupancy, quality scores, and team measures such as schedule adherence and attrition. The right set depends on the channels and the business; handle time on its own is a poor target because it rewards rushing.
What employment rules should a customer service manager know?
For hourly agents, the Department of Labor's Fact Sheet #64 on call centers says the workday starts with the first principal activity, such as starting the computer to load work applications, and that short rest breaks of usually 20 minutes or less count as hours worked. Call recording consent rules vary by state, and card payments taken by phone fall under PCI DSS. This is current as of October 2026 and not legal advice.
What should a customer service manager deliver by day 90?
A metrics baseline everyone agrees on, QA scoring that team leads apply the same way, a staffing plan built on the forecast, and one measured fix that removed a cause of repeat or avoidable contacts, agreed with the department that owns the cause.