CSAT Driver Analysis

What this capability handles

How it works in detail.

CSAT Driver Analysis answers the question every leader asks when the score moves: why. CSAT goes up or down, but the number alone does not say what caused it, so teams react to symptoms and invest in the wrong fixes. This capability decomposes the movement into its actual drivers. It is for support and operations leaders who need to know which segments, themes, capabilities, and rep cohorts are moving the score, so program investment targets causes instead of guesses. The outcome is CSAT clarity that steers where time and money go, backed by enough confidence to defend the call. It works through five stages: pull, decompose, score, report, alert. It runs inside your CSAT platform and your help desk. Each cycle it pulls CSAT scores, segment tags, theme links, and capability tags, then decomposes CSAT movement across segment, theme, capability, and rep cohort. It scores each segment so the contribution of each driver is visible, then reports the shifts with statistical confidence and alerts on the ones that matter. For each movement it produces an attributed breakdown: what shifted, by how much, in which segment, and with what confidence, so the decision targets the driver rather than the surface symptom. The decision logic uses driver decomposition and segment analysis to attribute CSAT shifts to operational causes, which is what turns a moving number into something a leader can act on. It is careful where the data is ambiguous. Driver conflicts, where signals point in different directions, route to the support leader. Novel segment shifts and conflicting signal route to a person as well, with the analysis attached. Every action is logged and reviewable, so each attribution can be traced back to the scores and tags behind it. Findings are directional with confidence bands, presented as such so leaders weigh them accordingly rather than treating soft signal as certainty. This capability fits teams whose CSAT feed is wired in and whose segment tagging is consistent; without consistent tags, segment attribution is not reliable. It carries 15-25% of the role's volume and contributes 15-20% of role impact through CSAT-driver clarity that steers program investment. Its primary measure is driver identification: naming what is actually moving the score.