Customer friction is what happens when a conversation stops flowing. The customer hit a wall somewhere — maybe they were transferred and had to re-explain everything, maybe they were put on hold for too long, maybe they were told to go try self-service after already trying. Whatever the cause, something in the interaction created unnecessary effort for the customer.
This signal identifies interactions where one or more of those friction points occurred. It does not just flag difficult calls in general — it pinpoints the specific types of friction: unresolved confusion, excessive hold time or dead air, misrouted requests, failed self-service referrals, and unnecessary transfers.
Customer effort is one of the strongest predictors of loyalty — stronger than satisfaction scores, stronger than first-call resolution in many contexts. When customers have to work hard to get help, they remember it. And they make decisions based on it.
The problem is that friction is invisible in traditional QA. A scorecard might mark all the boxes — greeting, verification, closing — and still miss that the customer was bounced between three departments before getting an answer. Friction lives in the gaps between what scorecards measure and what customers actually experience.
Tracking friction signals across your operation reveals patterns that no single interaction review can show: which processes create the most customer effort, which teams generate the most transfers, which self-service flows are failing and pushing customers to call in frustrated.
Compass looks at the full shape of the interaction, not just what was said. It evaluates whether the customer expressed confusion that went unaddressed, whether there were extended periods of silence or hold time, whether the customer’s issue was outside the agent’s scope, whether the customer was referred to self-service without confirmation it would work, and whether the interaction involved a transfer or handoff.
Any one of these is enough to indicate friction. The signal does not require a customer to explicitly say “this is frustrating” — it identifies the structural patterns that create effort, regardless of how politely the customer endures them.
Operations leaders use friction trends to identify process breakdowns. If friction spikes on a specific call type, it usually means something changed upstream — a policy update, a system issue, a training gap.
QA teams use friction signals to prioritize which interactions to review. Instead of random sampling, they focus on the calls where customers had to work the hardest.
CX leaders track friction rates as a leading indicator. Rising friction today predicts rising churn and complaint volume tomorrow.
This signal is part of Chordia’s Signal Intelligence capabilities.
We'll walk you through real interactions and show how each signal traces back to specific conversational evidence — so your team can act on what actually happened.
