A CX metric is any number that describes what happened in your support, such as average response time or how many conversations you handled. A CX KPI is the small subset of those measures you have chosen to steer decisions, with a target attached because it links to a goal you care about. Put simply: every KPI is a metric, but most metrics are not KPIs.
This guide explains the difference for ecommerce and retail teams, then shows how to pick a few useful measures without drowning in dashboards or inventing benchmarks.
The distinction sounds academic, but it changes how you spend your time.
You will track many metrics. You should only elevate a handful to KPIs, because KPIs are what you actively manage against. If everything is a KPI, nothing is.
Enterprise support teams can afford dozens of dashboards and someone to watch them. A small ecommerce or retail team cannot, and does not need to. Tracking too much leads to two problems: you spend time reporting instead of improving, and you lose the signal in the noise.
A lean team is usually better served by three to six measures they actually review, plus a slightly larger set of metrics they can look at when investigating a specific issue. Fewer, well-chosen measures beat a wall of numbers nobody acts on.
These describe how your support operation is running. They are the most actionable measures for a small team because you can usually influence them directly.
These are useful because they point to concrete fixes. A high reopen rate often means answers are incomplete. A slow FRT during certain hours might mean you need coverage or better self-serve content.
These describe how customers felt, not just what happened operationally.
CSAT (customer satisfaction) is the most practical for small teams. It usually asks a customer to rate a resolved conversation. Treat it carefully: response rates are often low, and a handful of ratings can swing the number. Use it to spot patterns over time, not to judge a single week.
NPS (net promoter score) measures likelihood to recommend. It can be useful, but do not invent a target for it. There is no universal "good" NPS, and copying a benchmark you read somewhere will mislead you. If you use it, watch your own trend rather than chasing an external number.
Whatever feedback measure you use, read the comments alongside the score. For a small team, the written reasons are often more useful than the number itself.
These describe how the work flows internally. They matter most as your team grows past one or two people.
You do not need formal reporting for these early on. Even a weekly glance at the inbox can surface workflow problems before they affect customers.
It is important not to blur these two categories.
Support KPIs measure the support operation: response time, resolution, satisfaction. You control these fairly directly.
Business outcomes measure the business: repeat purchase rate, revenue, retention, lifetime value. Support influences these, but so do product, pricing, marketing, and many other factors. Do not claim a single support change "increased retention by X percent" unless you can genuinely isolate it, which small teams rarely can.
The honest approach is to manage your support KPIs, watch business outcomes for direction, and describe the relationship as influence rather than a guaranteed cause.
To keep this concrete, here is one reasonable way a small store might group measures. These are examples, not required targets.
From each group, promote one measure to a KPI once you understand your own baseline. The rest stay as supporting metrics you check when something looks off.
The safest way to set targets is to start from your own data, not from a number you read online. A simple approach:
Avoid publishing or chasing industry "average" figures as if they were laws. Contexts differ enormously between a one-person store and a large brand, and a borrowed benchmark can push you toward the wrong priorities.
Cadence matters more than sophistication. A workable rhythm for a small team:
| Measure | Type | What it tells you | Review cadence |
|---|---|---|---|
| First response time | Operational metric / candidate KPI | How long customers wait for a first reply | Weekly |
| Resolution time | Operational metric | How long until an issue is fully solved | Weekly |
| First contact resolution | Operational metric / candidate KPI | How often you solve it in one reply | Monthly |
| Reopen rate | Quality metric | Whether "resolved" answers actually hold | Monthly |
| CSAT | Feedback metric / candidate KPI | How customers rate resolved conversations | Monthly |
| Conversation volume | Load metric | How much support demand you handle | Weekly |
| Handover rate | Operational metric | How often conversations move to a person | Monthly |
A quick note on tooling: AskDolphin includes a dashboard with lightweight analytics, but it does not automatically report every measure listed here. Treat this table as a measurement plan, and check which numbers your tools can show versus which you track manually.
For an ecommerce or retail team, good measurement is not about more dashboards. It is about separating metrics from KPIs, choosing a few measures you will actually review, and setting targets from your own baseline instead of borrowed benchmarks. Keep operational measures, feedback measures, and business outcomes clearly apart so you never overclaim what support alone caused.
To connect measurement back to the bigger picture, see our overview of customer experience for retail teams and our practical guide to customer experience tools for retail teams. When you are ready to bring chat, email, and QR-code conversations into one workspace you can actually measure, you can create an AskDolphin account.
A metric describes what happened, such as an average response time of four hours last week. A KPI is one of those metrics that you have chosen to steer by, with a target and a reason attached. Every KPI is a metric; most metrics are not KPIs.
A handful. Three to six measures you genuinely review beats a wall of numbers nobody acts on, with a slightly wider set of metrics kept for investigating specific problems. If everything is a KPI, nothing is.
There is no universal answer, and copying a benchmark you read online will mislead you. Measure your own baseline for a few weeks without changing anything, set a modest improvement target from it, and adjust the target if it turns out to be unrealistic.
Not on their own. Support influences business outcomes, but so do product, pricing and marketing. Manage your support KPIs, watch business outcomes for direction, and describe the relationship as influence rather than proven cause.
Most merchants do not need more chat. They need fewer repeat questions after purchase. This article covers what works when merchants add AI chat on Shopify, where it breaks, and how QR support takes pressure off chat and email.
AI support usually fails when the knowledge behind it is messy. This guide shows how ecommerce teams structure shipping, returns, product data, guardrails, and human handoffs so answers stay accurate and policy-safe.
Shoppers rarely abandon because they dislike a product. They leave when delivery, returns, sizing, or compatibility answers are missing. This case study lists 25 sales-blocking questions and how synced knowledge keeps replies accurate.
Post-purchase support often becomes most of the inbox: tracking, delays, returns, and refund follow-ups. This playbook shows the simplest tools retail teams use to deflect repeat tickets and keep expectations clear.
Hard-to-find staff in-store and post-purchase questions flooding email? This playbook shows where to place support QR codes, what scans should open, and how to route chats into one shared inbox with human handover when needed.
Unboxing support breaks when agents cannot tell which variant a customer holds. This guide shows how SKU-level QR codes on packaging open the right help, with placement tips, static vs dynamic choices, and rollout templates.
Which customer experience metrics are worth measuring, what each one tells you, and how to track them across digital, physical and omnichannel touchpoints.
You do not need a forty-tool CXM stack. This guide maps the practical customer experience tools ecommerce and retail teams use for chat, email, QR support, approved knowledge, and human handover.
A case-study style checklist for merchants who need live chat running fast without creating another inbox headache. See the settings, routing choices, and reply habits that improved response quality in real Shopify stores.
Selling across borders should not turn support into chaos. This playbook shows how retail teams handle multilingual chat and email with translation-safe macros, clear escalation rules, and QA habits that protect quality.
Install it in a minute. It starts working on your next visitor.
14 days, every feature.
