Most MSP owners know, at some level, that their service team could be performing better. Tickets take longer than they should. Certain clients seem to call more than others. A technician is always busy but never seems to make a dent in the queue. Client satisfaction feels fine until it isn’t, and the first sign is a cancellation conversation.
The reason these problems are hard to address is not that the data doesn’t exist. It’s that no one is pulling it, organizing it, and presenting it in a format that makes the cause visible.
Service teams that run without monthly KPI reporting aren’t flying blind by choice. They’re flying blind because tracking metrics requires someone whose job it is to track them — and in most MSPs under $5M, that role doesn’t exist yet. The service manager hat is worn by the owner, a senior tech, or no one in particular.
The cost of that gap compounds quietly. Small problems that metrics would catch early — a technician struggling with a specific ticket type, a client whose volume is spiking, an agreement that’s consuming far more labor than it should — stay invisible until they become expensive.
This post covers the five metrics that matter most for MSP service teams, what each one actually measures, what good looks like, and why running a service department without them is harder than it needs to be.
Why MSP Service Teams Run Without Metrics
There’s a pattern that shows up in nearly every growing MSP. The owner builds the service function based on instinct and experience. They hire good technicians. They set up a PSA. They work hard to deliver good service. And for a while, that’s enough.
Then the client count crosses a certain threshold. The ticket volume reaches a point where the owner can no longer personally see everything that’s happening. The PSA has data in it — closed tickets, time entries, survey responses — but it’s not being looked at systematically. The team is working hard, clients seem generally satisfied, and the financial statements show revenue going up, so the assumption is that service delivery must be working.
That assumption breaks at the worst moments: a client escalation that reveals a pattern of missed SLAs, a renewal negotiation that surfaces CSAT data the owner had never reviewed, a quarterly P&L that shows the service department is consuming far more labor cost than the gross profit it’s generating.
None of these are surprises to the data. They were visible in the metrics for months before they became visible to the owner. The problem wasn’t performance — it was the absence of a reporting structure that would have made the trend actionable earlier.
Five metrics, tracked monthly and reviewed consistently, close most of that gap.
KPI #1: First Time Resolution Rate (FTR)
What it measures: The percentage of tickets that are fully resolved on the first contact — no callbacks, no follow-up visits, no escalations to a senior tech.
How to calculate it: Divide the number of tickets closed without a follow-up action by total tickets closed in the period. Express it as a percentage.
What a healthy benchmark looks like: Industry benchmarks for MSP FTR typically fall in the 70–85% range. Top-performing service teams push above 85%. Below 65% warrants investigation.
Why it matters: FTR is a leading indicator for multiple things at once. Low FTR means clients are contacting support more than once for the same issue — which increases ticket volume, consumes more labor hours per resolution, and degrades client experience simultaneously. It also frequently signals a training gap: certain ticket types or client environments are generating repeat contacts because techs aren’t equipped to resolve them completely on the first attempt.
A technician with a low FTR rate on a specific ticket category is not necessarily underperforming across the board. They may need a process change, documentation, or targeted coaching on that category. Without FTR data broken out at the technician and ticket-type level, that’s invisible. With it, it’s a 15-minute conversation.
Improving FTR by 10 percentage points on a team handling 400 tickets per month means 40 fewer follow-up tickets. At an average of 45 minutes per ticket, that’s 30 hours of labor recovered — labor that was already being paid for and can now be applied to new work rather than rework.
KPI #2: Customer Satisfaction Score (CSAT)
What it measures: How satisfied a client is with the outcome and experience of a specific ticket, typically collected via a short post-resolution survey.
How to collect it: Most PSA platforms support automated CSAT surveys sent at ticket close. The standard format is a 1–5 or 1–10 rating, often with an optional comment field. CSAT is typically reported as a percentage of responses rated at the top tier (4–5 out of 5, or 9–10 out of 10).
What a healthy benchmark looks like: A well-run MSP service team should be targeting a CSAT score in the 85–95% range on a consistent basis. Below 80% is a signal that client experience has a structural problem, not just occasional bad days.
Why it matters: CSAT is the metric that connects internal operational performance to the client relationship. A service team can be hitting its SLAs on paper while still delivering a poor client experience slow communication, impersonal interactions, resolutions that technically closed the ticket but left the client confused or unsatisfied. CSAT captures what SLA data doesn’t.
It’s also the metric that has the most direct relationship to retention and referrals. Clients who consistently rate service at 4 or 5 out of 5 renew. Clients who consistently rate service at 3 out of 5 start taking calls from competitors. The difference between those two outcomes often comes down to whether someone at the MSP was looking at the CSAT data and acting on it.
CSAT data is most valuable at the individual technician level. An overall score of 88% across the team looks healthy. But if one technician is consistently at 70% while others are at 92%, the aggregate hides a meaningful problem. Monthly CSAT reporting by technician makes that visible and makes the coaching conversation concrete rather than subjective.
KPI #3: Average Resolution Time by Priority Tier
What it measures: The average elapsed time from ticket creation to ticket close, broken out by priority level (P1, P2, P3, etc.).
How to track it: PSA platforms log ticket open and close timestamps. Average resolution time can be pulled by priority tier and compared against the SLA thresholds defined in client agreements.
What a healthy benchmark looks like: Benchmarks vary by agreement type and client segment. What matters more than an industry number is whether your team is consistently meeting the resolution time commitments in your own agreements and whether average resolution time is trending in the right direction month over month.
Why it matters: Average resolution time by priority is where SLA compliance becomes visible at scale. Looking at individual tickets tells you whether a specific ticket breached. Looking at average resolution time by tier tells you whether the system is producing SLA compliance reliably or just accidentally.
A team that closes 90% of P2 tickets within SLA might look compliant. But if average P2 resolution time is drifting upward month over month from 4.2 hours to 4.8 hours to 5.5 hours that trend is heading toward systematic SLA failure. Catching it at 4.8 hours is a dispatching or workload conversation. Catching it at 7 hours is a client escalation conversation.
Breaking resolution time out by priority also reveals where bottlenecks live. If P1 resolution is on target but P3 average resolution time is three times longer than it should be, that’s not a capacity problem, it’s a prioritization problem. Low-priority tickets are getting deprioritized past their SLA thresholds while the team focuses on urgent work. Structured dispatching and queue monitoring are the fix, but you need the metric to see the problem first.
KPI #4: Effective Hourly Rate (EHR)
What it measures: The revenue generated per hour of labor actually worked not billed, but worked. EHR is calculated by dividing total service revenue by total labor hours in the period.
How to calculate it: Take total service revenue for the month. Divide by total technician hours worked (including non-billable time). The result is your effective hourly rate.
What a healthy benchmark looks like: EHR benchmarks vary by market and service model, but most MSP peer groups treat EHR as one of the clearest indicators of whether the service department is operating efficiently. An EHR trending upward over time indicates improving margin efficiency. An EHR trending downward or sitting significantly below what blended labor rates would suggest it should be indicates a structural problem.
Why it matters: EHR is the most honest profitability metric for a service department. It accounts for all the labor that goes into service delivery not just the hours logged on tickets, but the time spent in meetings, on non-billable internal work, on rework, on queue management, and on everything else that consumes technician capacity without generating revenue.
This is why EHR diverges from blended rate. A technician billing $150 per hour produces an EHR well below $150 if significant portions of their time are going to non-billable activity. The higher the non-billable overhead, the lower the EHR and the lower the actual return on the payroll being spent to employ that technician.
For MSPs on managed agreements, EHR is also the metric that reveals whether flat-fee clients are being serviced efficiently. A client generating high ticket volume relative to their agreement value will compress EHR. That’s a pricing and scope conversation but only if someone is running the number.
KPI #5: Ticket Volume Trend
What it measures: Month-over-month change in total incoming tickets per client.
How to track it: Pull ticket counts by client for each month. Compare current month to prior month and to the 3-month rolling average for that client.
What a healthy benchmark looks like: Ticket volume for a managed client should be relatively stable or declining over time as the environment matures and known issues are resolved. A sudden spike — or a gradual sustained increase over multiple months — is a flag.
Why it matters: Ticket volume trend is an early warning system for client health. When a client’s monthly ticket count starts climbing, it usually means one of three things: something in their environment has changed (new software, new users, infrastructure problem), the service team is not resolving root causes (fixing symptoms repeatedly rather than addressing the underlying issue), or the relationship is under stress (clients who are frustrated submit more tickets as they lose confidence in informal resolution).
All three of those are addressable — but only if the trend is caught early. A client whose ticket volume doubled over three months and whose CSAT dropped from 88% to 74% in the same period is a client at risk of cancellation. Catching that pattern at month two is a retention conversation. Catching it after the cancellation call is a postmortem.
Ticket volume trend also informs staffing and capacity planning. If aggregate volume is increasing 8% month over month, the team’s current headcount will hit its ceiling within a predictable timeframe. That’s a hiring conversation that can be planned rather than reacted to.
Tracking All Five, Plus the Ones That Reveal Department Profitability
The five metrics above cover the performance of the service team from the client’s perspective and from the efficiency perspective. But service department leadership requires two additional financial metrics that sit above the operational data: Agreement Gross Profit and Service Department Gross Profit.
Agreement GP measures how much gross profit each managed services agreement is generating after accounting for all direct costs labor, vendor, software. Service Department GP measures the overall profitability of the service function as a standalone business unit, after direct compensation and COGS but before allocating overhead.
These numbers don’t come from the PSA. They come from the intersection of operational data and financial data and producing them requires both accurate bookkeeping and consistent service reporting in the same place at the same time.
A BMK Ops service manager tracks and reports all five operational KPIs monthly, alongside Agreement GP and Service Department GP delivered to ownership. The reporting isn’t a dashboard to be interpreted, it’s a structured monthly review that connects what the service team is doing to what the service department is producing financially.
That reporting is what makes the coaching conversations with technicians concrete, what makes the pricing and renewal conversations with clients data-driven, and what gives ownership a clear picture of service department performance instead of a set of assumptions.
Talk to a BMK Ops Service Manager →
Book a free consultation to see exactly what monthly service reporting looks like for an MSP at your stage — and what decisions become possible when these numbers are on the table every month.
BMK Ops provides outsourced bookkeeping, dispatcher, and service manager services exclusively for MSPs. Based in Washington, DC — serving managed service providers across the United States.
