Customer support metrics for small business: the 6 to track weekly

Short answer: A small business should track six support metrics every week: first response time, resolution time, first contact resolution, customer satisfaction (CSAT), backlog, and reopen rate. Together they show whether customers get fast, correct and complete answers, and whether your team is keeping up. Start with simple targets, such as a first reply within one business hour and a backlog smaller than one day of incoming tickets, and tighten them as you improve.

Big support teams track dozens of numbers. You do not need to. Six well-chosen metrics, reviewed once a week, will catch almost every problem a small team runs into, whether the work is done by you, a hire or AI agents.

Which customer support metrics matter most for a small business?

These six cover speed, quality and capacity without needing a data team.

The targets are starting points for a small email-first team, not industry benchmarks. Set your own after two weeks of measuring, then raise the bar.

What is first response time and how fast should it be?

First response time (FRT) is the time between a customer sending a message and receiving the first real reply. Zendesk, for example, defines first reply time as "the time between ticket creation and the first public agent comment after that," and stores it in both calendar hours and business hours (Zendesk).

Two rules keep this metric honest:

• Do not count auto-replies. "We got your email" is not a response.
• Use the median, not the average. One ticket forgotten over a weekend can wreck the average while most customers had a fine experience.

Customers expect speed. HubSpot reports that 66% of consumers expect a customer service response in five minutes or less (HubSpot). Few small teams can do that with people alone, which is one reason owners hand first replies to AI agents. AI ticket triage shows how to set different response targets by ticket type.

How do you measure resolution time?

Resolution time is the time from the first message to the moment the issue is actually solved. It catches what FRT misses: a quick "we're looking into it" followed by three days of silence.

Track it by category. Tracking questions should resolve in minutes. Refunds that need your approval will take longer, and that is fine, as long as you can see where tickets wait. If most of the delay is "waiting for owner approval", the fix is a clearer refund rule, not faster agents. AI refunds in customer support covers writing those rules.

What is first contact resolution?

First contact resolution (FCR) is the share of tickets solved with a single reply. It is the best quality signal you can get without a survey.

Low FCR usually means one of three things:

1. Replies miss information the customer needs (tracking link, return address, next step).
2. The responder asks for details already in the first email.
3. Policies are unclear, so every case needs a back-and-forth.

All three are fixable with better templates and written policies.

How do you measure customer satisfaction (CSAT)?

CSAT (customer satisfaction score) comes from a one-question survey after a ticket is closed, for example "How satisfied were you with the help you received?" on a 1 to 5 scale. Count 4s and 5s as satisfied, divide by all responses and multiply by 100.

Example: 40 survey responses in a week, 34 of them 4 or 5. CSAT is 34 / 40 x 100 = 85%.

Keep the survey to one question plus an optional comment. Read every low score. On a small volume, the comments matter more than the percentage.

Why does backlog matter more than you think?

Backlog is the number of open, unresolved tickets at a point in time. It is your early warning. Response times can look fine for days while the backlog quietly grows, and then everything gets slow at once.

A simple rule: compare backlog with daily incoming volume. If you receive 50 tickets a day and have 120 open, you are more than two days behind, and next week will be worse unless something changes.

Common causes of a growing backlog:

• A seasonal spike or a promotion
• A product or shipping problem creating a wave of similar tickets
• Approvals piling up while the owner is busy
• Too many categories being escalated instead of handled

What does reopen rate tell you?

Reopen rate is the share of solved tickets that the customer reopens. It is the honesty check on resolution time and FCR. A team that closes tickets too early looks fast and efficient until you look at reopens.

Keep it under about 5% as a starting target, and look at every reopened ticket during the weekly review.

How do you run a weekly support review?

Thirty minutes a week is enough.

1. Pull the six numbers for the week and compare them with the last four weeks.
2. Look at the worst five tickets by resolution time and all reopened tickets.
3. Read every low CSAT comment.
4. Pick one change for next week: a template, a policy line, or a new rule for what can be handled without approval.
5. Write it down so you can see whether it moved the numbers.

If AI agents handle your inbox, this gets easier. In beereau, the Head of Support writes a weekly report, and every task shows who handled it, what they did, what it cost and who approved it. You can add cost per ticket as a seventh number; how to control AI agent costs explains how to track it.

Which metrics should a small business ignore at first?

Skip these until the six above are stable:

• Net Promoter Score, which measures loyalty to the brand more than support quality
• Handle time per agent, which matters for large call centres, not for a team of three
• Tickets per agent leaderboards, which reward speed over correctness
• Channel mix reports, unless you actually run several channels

Next step

Export the last two weeks of support email and calculate the six numbers by hand, even roughly. That baseline tells you where you stand and which one to fix first. If you are setting up a team to hit those targets, how to build an AI customer support team walks through the roles and approvals.