IntercomWilliam LaneExplainer
How to measure the customer experience as AI scales
Summary
CSAT captures fewer than 10% of conversations, and its responses skew toward delighted or furious customers. Most customers say nothing, leaving teams to assess customer experience from an unrepresentative sample that compresses product, policy, and service issues into one score. As AI handles more conversations end-to-end, the post argues for scoring every AI and human interaction on service quality, resolution, customer effort, and related attributes rather than relying on survey responses alone. Fin’s CX Score assigns each interaction a 1–5 score and surfaces reasons behind it, providing roughly five times more coverage than CSAT for most teams. Fin sets targets from CX Score attributes, operational correlations, historical performance, modelling, and team ambition, then uses recurring patterns to route fixes to support, product, or workflow owners.
Context
CSAT covers fewer than 10% of conversations, responses skew toward extremes, and a single score does not identify whether dissatisfaction comes from the product, policy, or service quality. As AI handles more conversations, more of the customer experience sits outside direct human review.
Approach / What changed
Score every AI and human conversation on a 1–5 scale, surface the reasons behind each score, break results down by answer quality, customer effort, and product feedback, and use operational correlations, historical performance, modelling, and team ambition to set targets. Use recurring patterns to route fixes to support, product, or workflow owners.
Takeaways
Fin’s CX Score evaluates every AI and human interaction and provides roughly five times more conversation coverage than CSAT for most teams.
Fin’s initial targets were 80% for Fin support, 70% for human support, and 78% overall, based on score modelling, historical performance, and team ambition.
Conversation-level patterns can reveal poorly performing topics, channel differences, handoff friction, and whether root causes belong to support, product, or a workflow.
Source and freshness
- Source
- intercom.com
- Published
- Added to Yomu
Summaries are generated from the original by a language model. Check the original before relying on it.
Keep reading
Related reading
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
The best engineering reads, once a week
One useful email. Unsubscribe anytime.