Guide
7 customer support metrics small teams should actually track
You don’t need a dashboard with 40 charts. These seven numbers tell a small team almost everything about how support is going.
The 7 metrics
Big support teams track dozens of numbers. A team of two to ten people needs a handful, checked once a week. Here are the ones worth your time, what each tells you, and what to do when it moves the wrong way.
1. First reply time
What it is: how long a customer waits for the first human reply.
Why it matters: it’s the number customers feel most. A quick “we’re on it” calms people down even when the full answer takes longer.
A good target: pick one you can keep every week, like “within 4 business hours” or “same business day”, and put it on your contact page. Use the typical (median) time, not the average: one email from Friday night can wreck an average.
If it’s slipping: set up auto-assign so new email has an owner right away, and use a saved reply for the first response.
2. Resolution time
What it is: how long from the customer’s first email until the conversation is closed.
Why it matters: a fast first reply followed by a week of back-and-forth still feels slow.
If it’s slipping: look at the slowest ten conversations. Usually it’s the same few topics (refunds, a confusing setting) waiting on one person. Write a help article or give a second person access.
3. Customer satisfaction (CSAT)
What it is: after a conversation closes, the customer rates it (for example 1 to 5 stars).
Why it matters: speed isn’t everything. CSAT tells you whether the answer actually helped.
How to use it: read every low rating and reply to the customer. The score is useful; the comments are gold.
4. Conversation volume
What it is: how many new conversations come in per day or week, and what they’re about (tags help here).
Why it matters: a jump usually means something broke, a shipment is late, or a page is confusing. It’s also how you know when to hire.
Tip: track your top 5 tags each month. If one topic keeps growing, fix the cause, not just the replies.
5. Open backlog
What it is: how many conversations are waiting on your team right now, and how old the oldest one is.
Why it matters: averages hide the one customer who’s been waiting six days. The oldest open conversation is the number to check every morning.
6. Reopen rate
What it is: the share of closed conversations the customer reopens by replying again.
Why it matters: a high reopen rate means conversations are closed before the problem is really solved, which makes your resolution time look better than it is.
7. Busiest hours
What it is: when customers write to you, by hour and day of the week.
Why it matters: if Monday morning is a wall of email, that’s when you need the most people on, and when a slow lunch break hurts most.
What you can ignore (for now)
- Replies per person as a target. It rewards quick, shallow answers. Use it to spot overload, not to rank people.
- Net Promoter Score in support. It measures how people feel about your whole business, not about one support conversation.
- Anything you won’t act on. If a number wouldn’t change what you do next week, don’t track it.
Where to find these in HallaHelps: Reports shows conversations, first reply time, resolution time, customer ratings (with every low rating listed), top tags and a table by person on every plan, plus your backlog right now: Waiting on us with how long the oldest has waited, Unassigned, and each person’s waiting conversations and oldest wait. Home shows each person what’s waiting on them. Pro adds handle time, 90th percentiles, reopen rate, busiest hours and AI insights. How reports work.
Want these numbers without building a spreadsheet? Try HallaHelps free for 14 days.
Try HallaHelps free for 14 days
No credit card. Connect your support address and answer your first customer in about 10 minutes.