From resolutions to ROI, measuring what your agents really do

"The agent resolved 60% of conversations" is a fine sentence for a dashboard and a useless one for a budget meeting. Turning agent performance into ROI means connecting three layers of measurement that most teams keep separate.

Layer one: conversation outcomes

Resolution, containment, escalation quality, CSAT. These are the agent's vital signs: necessary, but not sufficient. Instrument them per workflow, not per agent, so you know which capabilities carry the load.

Layer two: operational impact

Translate outcomes into operations: tickets deflected per week, average handle time saved on escalated conversations that arrive with context, coverage hours added without headcount. This is where support leaders live, and where staffing decisions get made.

Layer three: business value

Multiply operational impact by loaded cost, then add the revenue side, leads qualified, conversions assisted, churn saves. Report a range, not a point estimate, and state your assumptions. Finance trusts a conservative range more than a precise miracle.

One number to watch weekly

If you track only one thing, track cost per resolved conversation: agent and human paths side by side. When the agent's line drops below the human line for a workflow, scale that workflow. When it doesn't, you've found next quarter's iteration target.