You Got the Job. Now What?

Whether you were promoted from within or hired from outside, the first 90 days as a support manager determine whether your team trusts you. Not whether they like you. Trust.

I've watched new managers make the same mistakes: they either change everything in week one (alienating the team) or change nothing for six months (losing credibility). The right pace is somewhere in between, and the sequence matters.

Days 1-30: Listen and Measure

Your only job in the first month is to understand the current state. You're not here to fix things yet. You're here to figure out what's actually broken versus what people just complain about.

Sit in the queue

Spend at least 10 hours in the first two weeks handling tickets yourself. Not watching. Handling. You need to feel the friction firsthand. Which ticket types are easy? Which ones require hunting through five different tools? Where do agents get stuck?

This also earns you credibility with the team. Nothing kills trust faster than a manager who's never touched the queue.

One-on-ones with every agent

Schedule 30-minute conversations with each person. Ask these questions: What's the most frustrating part of your day? What's one thing you'd change if you could? What's working well that you're afraid a new manager will break?

That last question is the most important one. It tells you what to protect.

Pull the baseline metrics

You need numbers before you can show improvement. Get these:

First response time (median, not average, because averages are skewed by outliers). Resolution time (same, use median). CSAT score. Ticket volume by channel. Volume by category or intent. Agent utilization rate. Backlog size.

If your tools can't give you these numbers easily, that's your first finding.

Map the tool stack

List every tool your team uses. Helpdesk, knowledge base, internal wiki, CRM, communication tools, monitoring tools. For each one, note: who owns it, what it costs, and whether agents actually use it or just have access to it. You'll find at least one tool nobody uses and at least one critical function held together by a spreadsheet.

Document what you find

Write it down. A simple doc with "Current State" sections for metrics, tools, team structure, and known pain points. You'll reference this at day 90 to show what changed.

Days 31-60: Quick Wins and Priorities

You've listened. You have data. Now pick the two or four things that will have the biggest impact with the least disruption.

Fix one workflow that everyone hates

Every team has one. Maybe it's the escalation process that requires filling out a form in triplicate. Maybe it's a macro that hasn't been updated in a year. Pick the most universally annoying one and fix it. This builds momentum and shows the team you listened.

Evaluate your automation gap

Look at your ticket categories. What percentage are repetitive questions with known answers? Password resets, order status, "how do I cancel?" For most teams, 50-70% of volume falls into categories that could be automated or deflected.

This is where tools like Supp come in. At $0.20 per classification, you can route or auto-resolve the high-volume, low-complexity tickets and let your agents focus on the stuff that actually requires judgment. But don't buy anything yet. Just quantify the opportunity.

Set two goals for the quarter

Not five. Not ten. Two. Make them specific and measurable. "Reduce median first response time from 4 hours to 2 hours" is a goal. "Improve customer experience" is not a goal, it's a wish.

Share these goals with the team and your boss. Alignment now prevents conflict later.

Start a weekly team meeting (if there isn't one)

Keep it short: 20 minutes max. Share key metrics, highlight one good customer interaction, discuss one process question. The goal is rhythm, not reporting.

Days 61-90: Build the System

By now you know the team, you have baseline metrics, and you've shipped a couple of quick wins. Time to build something that lasts.

Create (or rewrite) the team handbook

Document how your team works. Escalation rules, schedule expectations, quality standards, tool guides. This isn't bureaucracy. It's equity. When the rules are written down, everyone gets the same information regardless of who they sit next to or how long they've been around.

Implement one automation

Take that automation gap analysis from month two and implement the highest-impact, lowest-risk automation. Maybe it's auto-routing tickets by intent. Maybe it's a chatbot that handles order status lookups. Start small, measure the impact, and expand from there.

Build your reporting cadence

Set up a weekly dashboard you actually look at and a monthly report for leadership. The monthly report should connect support metrics to business outcomes. Don't just report "we handled 2,000 tickets." Report "we handled 2,000 tickets, 60% were resolved in under 2 hours, and our top issue was billing confusion from the new pricing page."

Have the hard conversations

By day 90, you know who your top performers are and who's struggling. If someone needs coaching, start now. If there's a performance issue, address it directly. Waiting doesn't make these conversations easier. It makes them worse.

The 90-Day Check-in

At day 90, pull your metrics again. Compare them to the baseline from day 30. Write a brief summary: here's where we were, here's where we are, here's what we're doing next quarter.

Share it with your team and your boss. Transparency builds trust in both directions.

The biggest mistake new managers make isn't picking the wrong priorities. It's skipping the listening phase. Month one feels slow. It's supposed to. The patience pays off in months two and three, when every decision you make is grounded in reality instead of assumption.