The short answer on customer support dashboard metrics is that five to seven numbers, split between leading indicators you act on this week and lagging indicators you learn from next quarter, will do more than a screen of twenty tiles. Track CSAT, first response time, first contact resolution, backlog age, and AI-vs-human split as the daily view. Keep NPS, cost per resolution, and churn on a monthly page. Everything else is noise you review when a number moves.
Why most support dashboards fail
A support dashboard fails in one of two ways. The first is that it shows so many tiles no one reads any of them. The second is that every tile is a lagging indicator, so by the time the numbers move the customers who caused the move have already left. Both problems have the same fix: fewer metrics, chosen deliberately, split between what you can act on today and what you review at cadence.
Industry guidance for 2026 is converging on a small-dashboard rule. Kaizo's recent write-up puts it simply: "start with 5 to 7 core KPIs aligned to your business stage and goals, rather than tracking excessive metrics that lead to analysis paralysis." That is the target. Five to seven tiles a duty support lead reads over coffee.
Leading vs lagging: why the split matters
Leading indicators move first. If backlog age creeps up on a Monday, CSAT drops the following week. If refusal rate spikes on the AI agent, reopens follow inside seven days. If a lint bot flags a broken help article, the first ticket about it lands two days later. A leading indicator gives you a chance to act before the customer notices.
Lagging indicators confirm what already happened. CSAT week over week, cost per resolution, monthly churn: these are honest scoreboards. They cannot be gamed short term because they take time to move, and that same property makes them useless for tactical response. Kaizo's rule reads well: "use leading indicators to manage operations, and lagging indicators to improve the system." The daily view is leading. The monthly view is lagging.
Most SMB dashboards invert that split without meaning to. They put NPS on the main screen because a stakeholder asked for it, and hide backlog age three clicks deep because it was hard to plumb. That is the wrong way round.
The seven-tile daily view for a small team
Pick five to seven of these for the main screen. The exact set depends on your channel mix and whether you run an AI agent, but the shortlist below is a safe default for a five-to-fifty-person team.
CSAT (rolling 7 days). The honest quality signal. Anything under 80% is a warning; 85% and up is the working target across most 2026 benchmarks; 90% plus is best-in-class.
First response time by channel. Live chat under one minute, email under one hour, WhatsApp under two minutes. The benchmarks from Kayako's 2026 write-up put email best-in-class at "under 1 hour" and live chat "under 1 minute." Show each channel as its own tile if you serve more than two.
First contact resolution. Roughly 30% of customers are still returning about the same issue at the industry average, per SQM Group's benchmark: "SQM Group's current benchmark puts average call-center FCR at about 70%, which means roughly 30% of customers need another call about the same issue." Aim for 75% or higher; ecommerce commonly sits in the 75 to 85% band, per Stealth Agents' 2026 review.
Backlog age (oldest ticket in the queue). Not backlog size. Age. A backlog of 200 with the oldest ticket at four hours is fine. A backlog of 40 with the oldest at four days is a problem. Set an alert at 24 hours.
Handoff and reopen rate. Together these tell you whether the frontline is doing the right work. A handoff rate that drops without CSAT rising means the AI is guessing. A reopen rate above 10% means the resolutions are shallow.
AI-handled share and refusal rate. If you run an AI agent, this pair is the daily read on whether it is holding its ground. AI-handled share drifting down without a policy change is drift. Refusal rate spiking is a stale source. Lorikeet's summary is blunt: the dashboard should "always include an AI-handled toggle to properly measure AI vs. human performance separately."
One channel-specific tile. Whichever is your busiest. For an ecommerce team, WISMO volume as a share of tickets. For SaaS, log-in-related tickets. For services, appointment-change tickets. Track the biggest bucket you have the power to shrink.
The monthly page: numbers you cannot game short term
The daily view is for shift decisions. The monthly view is for direction changes.
CSAT trend. Twelve weeks in a line chart, not one number.
NPS. Runs quarterly at most, plotted against the last four quarters.
Cost per resolution. Fully loaded, including tooling and overhead. It is the honest number your finance team wants. For the calculation approach see our note on cost per ticket.
Deflection and resolution together. Deflection alone misleads; the pairing is the honest story. Details are in deflection vs resolution rate.
AI ROI year-to-date. Not just savings. Also errors, escalations that came back, and the cost of any incident. Framework in measuring AI support ROI honestly.
The tiles safe to cut
Ticket volume by tag as a headline number. Useful in analytics, distracting on a dashboard. If a tag matters enough to headline, promote it to its own volume tile with a target.
Average handle time as a main tile. AHT is an efficiency number for the leadership review, not for a duty lead. Optimising for AHT by itself trains agents to close fast rather than solve. Keep it on the monthly page. See the AHT glossary entry for the fuller argument.
Sentiment scores from automated tone analysis. Interesting, but noisy. Read at the sample level, not the aggregate.
A recommended two-view layout
| View | Cadence | Tiles | Owner | | --- | --- | --- | --- | | Daily | Read at 9am | CSAT (7d), FRT by channel, FCR, backlog age, handoff+reopen, AI-handled share, one channel-specific tile | Duty support lead | | Monthly | Reviewed in the ops meeting | CSAT trend (12w), NPS, cost per resolution, deflection and resolution, AI ROI YTD | Head of support |
Two views. Two owners. Twelve numbers in total, not forty.
Alerts, not staring
A good dashboard is read once a day for a minute and pinged when something moves. Set thresholds on the daily tiles and route the alerts to the on-call support channel. Backlog age over 24 hours: alert. CSAT dropping more than 5 points week over week: alert. Refusal rate up 20% in a day: alert. Anything else is noise; you can catch it in the weekly review.
How Keloa approaches support dashboards
The Keloa unified inbox exposes the daily-view metrics without an export step: CSAT per conversation, first response time by channel, and the handoff and reopen rates for AI agents sit in the same place the tickets are worked. Because the AI cites its sources on every reply, per our note on reducing AI hallucinations, refusal rate and citation coverage are honest signals, not derived guesses. For SLA framing see SLA design for small teams.
We keep the default dashboard to seven tiles and a monthly page. Teams add more only when a specific decision requires them.
Frequently asked questions
How many metrics should a support dashboard show? Five to seven on the main daily view, and roughly five more on a separate monthly page. Any more than that and no one reads it. Any fewer and you miss category-specific drift.
Which single metric matters most for a small team? First contact resolution. SQM Group's longitudinal data has it as the strongest single predictor of customer satisfaction, and every 1% improvement in FCR is roughly a 1% cut in operating cost because fewer tickets return to the queue.
Should AI-handled tickets be measured the same way as human-handled ones? Same metrics, separate segment. Split the dashboard by an AI-vs-human toggle. Averaging them hides both stories. CSAT for an AI reply that resolved instantly is a different number from CSAT for a human reply that took two hours; you need to see both.
How often should the main dashboard be reviewed? Once a day by the duty lead, once a week in the support standup, once a month in the ops meeting. The alerts do the rest. If the team is staring at the dashboard mid-shift, the alerts are set too loose.
What is a good first response time for live chat? Under one minute is the widely-cited 2026 benchmark for live chat. Email best-in-class sits under one hour, and social under one hour. WhatsApp customers now expect a first response inside two minutes.
Do we need a separate dashboard per channel? No. One dashboard, filtered by channel via a toggle. Separate dashboards drift out of sync and hide comparisons. If two channels genuinely have different owners, split the alerts, not the screens.
Want a working seven-tile setup? Book a demo and we will walk through the daily view, the alerts, and the monthly page against your own ticket data.