How to Measure Customer Service When You're a Small Team
Ask a small business how customer service is going and you'll usually get a feeling, not a number. "Busy." "Pretty good, I think." "Tuesday was rough." Those feelings are often right, but they're hard to act on. They won't tell you whether a part-timer would help, whether the new booking page cut down on calls, or whether customers are waiting longer than they did in the spring.
Large support teams handle this with dashboards full of charts and someone whose job is to read them. You don't need any of that. A small team needs a handful of numbers, checked at the same time each week, and the habit of asking what changed.
Below are the four numbers we set up for almost every small client, what each one tells you, and where to find them if you use Zendesk® help desk software. If you use a different tool, the ideas still apply. Most help desks report on the same basics.
Why gut feel stops working
When one person answers every email, they carry the whole picture in their head. They know it was a heavy week, they know which customer is unhappy, and they know the same question about parking came in four times.
Once two or three people share the work, nobody sees all of it. Sarah remembers the upset customer from Monday, but she was off on Thursday when five people asked about the same late delivery. The numbers fill in what no single person can see.
Measuring also keeps conversations fair. "We're slow" turns into "our typical first reply went from 3 hours to 9 hours the week Mike was on vacation." That points to a fix, like a cover plan, rather than at a person.
Here's the whole approach on one page.
1. Ticket volume: how busy are you, and when?
Volume is the number of new requests in a period: emails, form submissions, chats, whatever comes in. It's the simplest number, and everything else depends on it. If reply times doubled, the first question to ask is whether twice as many tickets arrived.
The weekly total is a start, but the useful part is the shape:
Which day is busiest. Many service businesses get a Monday spike from messages that piled up over the weekend.
Which hours. If half your tickets arrive after 5 p.m., that's a staffing question, or a sign that customers need answers they can find on their own.
Which channel. If most requests come through your website form, that's where your effort should go.
What people are asking about. Even a rough category field (booking, billing, complaint, general question) shows you which topics deserve a help article or a saved reply.
A good habit for a small team: when the same question shows up five times in a week, write the answer once and reuse it.
2. First reply time: how long do customers wait for a person?
First reply time is how long it takes from the moment a customer writes in until someone on your team sends the first public reply. Zendesk defines it as the time between ticket creation and the first public agent reply, so an automatic "we got your message" email doesn't count. That's how it should be. Customers can tell an autoresponder from a person.
Two things to keep in mind when you read this number:
Use the median, not the average. One ticket that sat over a long weekend can drag an average way up. The median is the middle ticket, which is much closer to what a typical customer experienced.
Know whether you're looking at calendar hours or business hours. Zendesk Explore™ reporting has both versions of its time metrics. A ticket that arrives at 9 p.m. on Friday and gets answered at 9 a.m. on Monday waited 60 calendar hours but only a few business hours. Pick the one that matches the promise you make to customers and stick with it.
What's a good target? It depends on what you promise. Zendesk's own guidance on support metrics suggests something like 24 hours for email and web forms. Plenty of small service businesses do far better than that, and if your website says "we reply within one business day," that's your target. Write it down and measure against it.
3. Resolution time: how long until it's actually fixed?
A fast first reply is nice, but what customers care about is the problem being solved. Full resolution time measures from when a ticket was created to when it was last set to Solved.
This number is noisier than first reply time, because some tickets are slow for good reasons: a part on back order, or a customer who takes four days to send the photo you asked for. That's why the Pending status matters. When your team sets a ticket to Pending while waiting on the customer, Zendesk software tracks that time separately from the time the ticket spent waiting on you. Using Pending consistently keeps your numbers honest.
What to look for each week:
Tickets open longer than a week. Open the list and ask why each one is stuck. Often it's a ticket nobody owns.
A median that keeps creeping up. If it rises three weeks in a row, something changed: harder requests, a new team member still learning, or a process with too many hand-offs.
4. Repeat contacts: did you fix it the first time?
Most small teams never look at this one, and it's often the most telling. A repeat contact is a customer coming back about the same issue because the first answer didn't solve it. Each one is extra work for you and a worse experience for them.
There are two easy ways to see it in your Zendesk account:
Reopened tickets. When a customer replies to a solved ticket, it reopens. The prebuilt Zendesk Support™ dashboard shows the percentage of solved tickets that were reopened.
A repeat-contact tag. Reopens miss the customer who sends a brand new email about the same problem. Ask your team to add a tag such as repeat_contact whenever they notice one. It takes two seconds, and a quick search gives you the weekly count.
Paste this into the search box in your Zendesk account to see the last seven days:
type:ticket tags:repeat_contact created>7days
Once a month, read five of those tickets in a row. You'll usually spot a pattern: a confirmation email that leaves out the address, a policy explained two different ways, a how-to article missing a step. Fixing that pattern is worth more than shaving an hour off your reply time.
The same dashboard also shows one-touch tickets, meaning tickets solved with a single reply from your team. If that share grows over time, it's usually a sign your answers are getting more complete.
Where to find these numbers in Zendesk Explore reporting
Zendesk Explore reporting is built into the Zendesk platform. Every current Zendesk Suite™ plan includes it, and so do the Support Team, Professional and Enterprise plans. The Zendesk Suite Team and Growth plans and the Support plans come with the Lite version, which gives you the prebuilt dashboards made by Zendesk but not custom reports. For a team of three, the prebuilt dashboard covers everything in this post. In the product menu it now appears as Analytics, so don't be surprised if you see both names.
Sign in as an admin, click the product tray icon in the top-right corner, and select Analytics. The first time, you may see an activation page. Zendesk notes that activation can take a few hours, so do this a day before you plan your first review.
Click the Dashboard icon in the left sidebar and open the Zendesk Support dashboard from the list.
On the Tickets tab, note Created tickets, Reopened tickets and One-touch tickets. The reports further down show tickets by hour and by day of the week, which answers the "when are we busy" question.
Switch to the Efficiency tab and note First reply time median and Full resolution time median. This tab filters by the date tickets were solved, except for first reply time, which uses the date tickets were created. Zendesk's overview of the dashboard tabs explains every report if you want more detail.
Set the date filter to last week, and use the same range every time so the comparison is fair.
Copy the numbers into a simple spreadsheet with one row per week. After a month you'll have a trend, which is far more useful than any single week.
Two things to check if something looks off. Dashboard data isn't live, it refreshes on a schedule that depends on your plan, so this morning's tickets may not show up yet. And if a teammate can't open the dashboards, Zendesk's guide to giving users access explains the setting for your plan.
A 15-minute weekly review
Numbers only help if someone looks at them. Here's the routine we suggest: same person, same time, every week. Monday morning works well, because last week is complete and this week hasn't picked up speed yet.
The last item matters most. Each week, choose one small fix based on what you saw. Maybe it's a saved reply for the question that came in eight times, a help center article for the step customers keep getting wrong, or a rule that sends billing questions straight to the person who handles them. One small fix a week adds up quickly.
What you can skip for now
There are dozens of support metrics, and larger teams use a lot of them. At your size, most of them are noise:
Agent leaderboards. With three people, ranking who solved the most tickets mostly measures who got the easy ones.
Formal SLA policies. They're useful later. For now, a written target for first reply time does the same job.
Satisfaction scores at low volume. If you only get a handful of survey responses a month, the percentage will swing wildly. If you do turn on surveys, read the comments rather than watching the score.
The short version
You don't need an analyst to know how your customer service is doing. Four numbers, checked once a week, will tell you when you're getting busier, when customers are waiting too long, and when the same problem keeps coming back. Start with what your help desk already shows you, write the numbers down, and let them point you to one improvement at a time.
If you're still answering customers from a shared inbox and want to see what these reports look like with your own tickets, you can start a free Zendesk trial.
Want help setting up support you can actually measure?
Our Small Business Launch Bundle gives you a basic Wix website and a basic Zendesk help desk with a Help Center and email support, set up for you. Every request lands in one place from day one, which is what makes these four numbers possible to track.
Not sure which numbers matter most for your business? Send us a question and we'll be glad to help.
Want more practical guides like this one in your inbox? Subscribe to the blog.
Zendesk®, Zendesk Suite™, Zendesk Support™ and Zendesk Explore™ are trademarks of Zendesk, Inc. This article is written independently by HelpdeskCX and is not sponsored or endorsed by Zendesk, Inc.
Comments