CSAT and CES for planners: what outcome metrics can and can’t tell you
The metrics the board actually cares about
Service level and average speed of answer are operational metrics — they describe how the queue behaved. CSAT (customer satisfaction), CES (customer effort) and their cousins are outcome metrics: they describe how the customer felt about the result. The board cares far more about the second kind, which is why planners increasingly find these numbers landing on their dashboard. The trouble is that outcome metrics behave nothing like operational ones, and a planner who treats a CSAT score the way they treat a service level will draw confident conclusions that the data can’t support.
A loose, lagged, noisy link
Staffing and service level are tightly coupled: add agents, the wait falls, almost immediately and almost mechanically. Staffing and CSAT are coupled too, but loosely. A customer’s satisfaction is driven mostly by whether their problem got solved, by the agent’s manner, by the product and the policy — and only partly by how long they waited. The link is also lagged (today’s short-staffing shows up in next week’s survey), noisy (small samples, response bias, mood), and non-linear (beyond a point, faster answers don’t raise satisfaction at all). So you can pour staff at a queue and watch service level leap while CSAT barely twitches — not because staffing doesn’t matter, but because it was never the binding constraint on how the customer felt.
Using them without fooling yourself
Hold outcome metrics at the right altitude. Use CSAT and CES to challenge the operational target — if satisfaction is flat while you chase an ever-tighter service level, that’s a sign you’ve passed the point where speed buys anything and the money belongs elsewhere (resolution, skills, the product). Don’t use a weekly CSAT wobble to justify a staffing change; the sample is too small and the lag too long, and you’ll be chasing noise. Pair the outcome number with an operational one that does respond to staffing, so you can tell a service problem from a resolution problem. And be honest with stakeholders about what the planner controls: you can defend the wait, but satisfaction is a team sport. Treated as a compass rather than a dial, outcome metrics make the planner’s case sharper — misread as a control knob, they send you chasing ghosts.
Pair this with is service level a dead KPI?, leading vs lagging indicators, and how composite metrics hide the truth.