Most support teams should track five customer service metrics: CSAT (or DSAT for negative-only routing), first response time, first contact resolution, conversation volume, and a quality score that covers unrated threads. Everything else (NPS, CES, backlog age, deflection rate) becomes useful once you have a stable weekly rhythm on those five.
Intercom ships dozens of report tiles. The trap is tracking all of them and reviewing none. This guide cuts the list to what support leads actually act on, grouped by team size, with Intercom paths for each number.
The hard part is not picking metrics; it is making someone look at them every Friday. Supportman posts volume, response times, and a seven-day ratings summary to Slack automatically, plus per-agent DMs so reps see their own trends without anyone exporting a report.
Which five metrics should you track?
| Team stage | Track these five | Why this set |
|---|---|---|
| 1–5 agents (founder-led) | CSAT, volume, median first response time, reopen rate, DSAT count | Small teams feel every bad rating. DSAT routing matters more than NPS surveys you will never send. |
| 6–15 agents (first lead hire) | CSAT, first response time, FCR, volume per agent, QA sample rate | Consistency breaks here. You need per-agent visibility and a rubric before scaling headcount. |
| 16–50 agents (ops function) | CSAT, FRT by channel, FCR, backlog, IQS or predicted CSAT on unrated threads | Survey response rates collapse below 20%. Quality scoring fills the coverage gap CSAT leaves. |
| 50+ agents (multi-tier) | CSAT by tier, SLA adherence, FCR, escalation rate, cost per contact | Segment by L1/L2 and channel. Executive metrics join the weekly ops review. |
If you run Intercom + Slack, pair this table with every Intercom metric explained for definitions, Intercom CSAT benchmarks for targets, and what Intercom Reports cannot show before you wire a weekly review.
The core five explained
1. CSAT and DSAT
CSAT measures satisfaction on a specific conversation. Intercom uses five emoji choices, from Amazing and Great through Okay, Bad, and Terrible. It is immediate and actionable, but it only represents customers who respond. DSAT is the negative tail you route to a dedicated channel while recovery is still possible. See CSAT vs DSAT for formulas.
Do not treat CSAT as a loyalty metric. A customer can love your product and rate support poorly because of a policy outside the agent's control. Always read the remark field.
2. First response time
Median first response time (FRT) tells you whether customers wait too long for a human reply. Track median, not average: one outlier skews the mean. Split by channel (chat vs email) because expectations differ.
3. First contact resolution
FCR is the share of conversations resolved without reopening within a set window (often 24–72 hours). Intercom does not label this metric directly; you infer it from reopen rate and snooze patterns. High reopen rate usually means knowledge gaps, not lazy agents. Full guide: what first contact resolution is and how to measure it in Intercom.
4. Conversation volume
Raw ticket count, new vs closed, and volume per agent. Volume spikes before you feel them in CSAT. Compare week-over-week and flag product launches, billing cycles, or outage windows.
5. Quality beyond surveys
When response rates drop, CSAT becomes a sample of your happiest and angriest customers. Add a quality layer: manual QA on a sample, or AI scoring on every closed conversation against a rubric. Start with building a QA rubric agents can actually use.
Where to find each metric in Intercom
| Metric | Intercom path | Caveat |
|---|---|---|
| CSAT / DSAT | Reports → Satisfaction, or Inbox → conversation rating filter | Filter by teammate, tag, and Fin vs human |
| First response time | Reports → Response and wait times | Use median; exclude bots if Fin inflates speed |
| Reopen / resolution proxy | Reports → Conversation volume + custom reopen tags | Define "resolved" consistently across the team |
| Volume | Reports → Inbound volume | Segment by channel and priority |
| Per-agent breakdown | Reports → Teammate performance | Pair with QA scores, not CSAT alone |
Intercom's native Slack app does not push these numbers to channels. If your team lives in Slack, connect Intercom and Slack with a reporting layer (Supportman for Friday summaries and real-time ratings) so metrics get seen without a dashboard login.
Weekly review cadence
Pick one 30-minute slot (Friday works for most B2B teams) and stick to this agenda:
- Headline numbers: CSAT, DSAT count, median FRT, volume vs last week.
- One conversation deep-dive: lowest DSAT or lowest QA score from the week.
- One process fix: macro gap, help article update, or routing rule — not a vague "coach harder."
- Per-agent DMs: send individual trends so reps see their own FRT and ratings before Monday.
Use the weekly customer support report template for the exact sections that belong in Slack vs a live meeting.
Metrics you can skip until later
NPS measures loyalty, not conversation quality. Useful for product and marketing; rarely actionable for a support lead on Monday morning. See NPS explained when you are ready.
CES (Customer Effort Score) matters for complex B2B workflows but duplicates what a good FCR + reopen analysis already tells you.
Deflection rate and help-centre search success are valuable once self-service is a deliberate programme, not a side project.
Average handle time incentivises rushed replies in async channels. Prefer time-to-resolution and reopen rate instead.
Customer service metrics FAQ
How many customer service metrics should I track?
Five core metrics weekly: CSAT (or DSAT), first response time, first contact resolution (or reopen rate), volume, and a quality score. Add NPS, CES, or deflection only after those five have a stable review cadence.
What is the most important customer service metric?
CSAT is the most actionable for day-to-day coaching because it ties to specific conversations. It is not the most complete: low survey response rates mean you need QA scoring or predicted satisfaction on unrated threads too.
Where do I find customer service metrics in Intercom?
Reports → Satisfaction for CSAT, Reports → Response and wait times for FRT, Reports → Inbound volume for ticket count, and Reports → Teammate performance for per-agent breakdowns. Export or automate to Slack if your team does not live in the Intercom dashboard.
What is a good CSAT score for customer support?
For Intercom teams, 80%+ is a healthy baseline and 85%+ is strong. Benchmark against your own trend and channel mix, not a generic industry average. See Intercom CSAT benchmarks for a practical framework.
Should I track KPIs or metrics?
They are the same thing in practice: measurable indicators of support performance. Pick five, assign an owner for the weekly review, and link each to a specific action (coaching, macro update, staffing) rather than a dashboard tile nobody opens.