Why vanity metrics mislead merchants
It is easy to track total tickets closed and call it a support dashboard, but that number rewards busywork as much as good outcomes. A rep who closes twenty simple tracking tickets looks more productive on paper than one who spends the same hour resolving a single complex dispute — even though the second hour was arguably worth more to the business.
The goal of measurement is not a bigger number, it is visibility into where support time goes and whether customers are actually being served well. A handful of the right metrics does that; a dashboard full of vanity counts does not.
First response time
First response time is how long a customer waits between sending a message and getting any reply, not necessarily a resolution. It is one of the strongest predictors of customer satisfaction because uncertainty, not the wait itself, is what frustrates people — an acknowledgment within minutes changes how a customer experiences even a slow resolution.
For order-support email specifically, a reasonable target is under a few hours during business days, and under a few minutes for the subset of tickets that can be answered automatically.
WISMO ratio
WISMO ratio is the share of total support volume made up of order-status questions. Tracking it monthly tells you two things: how much of your team's time is spent on the most automatable ticket type, and whether changes to your shipping communication — better tracking emails, a visible order-status page — are actually reducing the questions that prompted them.
A rising WISMO ratio during a specific week is usually a signal worth investigating on its own — it often means a carrier delay or a fulfillment backlog, not a support problem.
Ticket deflection rate
Deflection rate measures how many potential tickets never get created because a customer found the answer elsewhere — a tracking page, an FAQ, a proactive shipping email. It is the hardest of these metrics to measure precisely, since a deflected ticket is invisible by definition, but a rough proxy works: compare WISMO volume before and after a change like adding tracking links to shipping confirmation emails.
For merchants using automated replies rather than self-service pages, the equivalent number is auto-resolution rate: the share of WISMO tickets answered without a human touching them, which is a direct, measurable version of deflection.
Customer satisfaction for support replies
CSAT for a tracking reply specifically, not your whole support operation, tells you whether automation or templates are actually landing well, separate from your team's overall reputation. A short one-question survey attached to tracking replies is enough; anything more elaborate gets ignored on a message this routine.
Watch for a CSAT gap between automated and manually-handled tracking replies. A meaningful gap usually points to either overly generic template language or cases being auto-answered that should have been escalated.
Resolution time vs. first response time
These get conflated but measure different things: first response time is how fast you acknowledge, resolution time is how long until the issue is actually closed. For a clean tracking reply, both should be nearly the same number — anything else suggests replies are being sent without actually answering the question, which shows up later as a repeat contact.
How to track these without a full helpdesk
None of these require enterprise-grade reporting. A shared inbox with timestamps, a simple spreadsheet log of ticket type and response time for a sample week each month, and a lightweight automation dashboard if you use one cover all five metrics above for most stores under a few thousand orders a month.
- First response time: timestamp gap between received and first reply.
- WISMO ratio: tag a week's worth of tickets by type, then divide.
- Auto-resolution rate: automated replies sent divided by total WISMO tickets.
- CSAT: one-question survey attached to the reply itself.
Setting realistic targets
Set targets from your own baseline, not an industry benchmark pulled from a much larger company. A two-person team with a three-hour first response time that improves to 45 minutes has made real progress even if a benchmark says 15 minutes is best in class — the number that matters is the trend for your store, measured consistently month over month.