azyware
Maintenance & AI operationsMetric

Cost per resolved conversation

Also: Cost per resolution, CPRC

In one sentence

What is Cost per resolved conversation?

Cost per resolved conversation is the total cost of running an AI support agent, including inference, tooling and human escalation, divided by the number of customer conversations it fully resolved without reopening.

What Cost per resolved conversation means

Cost per resolved conversation measures what an AI support agent actually costs for each problem it genuinely solves. The numerator includes model inference, retrieval and vector-store costs, telephony minutes for voice, platform fees, and the human time spent on conversations the agent escalated or that were reopened. The denominator counts only conversations the customer did not need to raise again within a defined window, typically seven days.

It is deliberately stricter than cost per conversation or cost per deflected ticket. Deflection counts a customer who gave up; resolution counts one whose issue ended. Including escalation cost in the numerator prevents a cheap agent that hands everything to humans from looking efficient.

The metric is usually compared against the fully loaded cost of a human-handled resolution on the same ticket types. The comparison must use like-for-like categories; an agent that resolves only simple queries will look cheap against a human average that includes complex cases.

Who it really matters to

  • Support manager: the number that shows whether the agent reduces cost while keeping customers satisfied, rather than just shifting work.
  • CFO: allows a direct comparison between AI-handled and human-handled resolutions and a credible business case for expanding scope.
  • Product manager: reveals which intents are cheap to resolve and which drive cost through escalation, guiding what to automate next.
  • CTO / Head of Engineering: exposes inference and retrieval cost inefficiencies, such as oversized prompts or unnecessary model calls, per resolution.

Why it exists

The metric exists because the common alternatives mislead. Ticket deflection rewards agents that make customers give up. Cost per conversation rewards agents that end conversations quickly regardless of outcome. Both can improve while customer satisfaction and total support cost get worse. Cost per resolved conversation ties spend to genuine outcomes and includes the human cost the agent generates, so it cannot be gamed by pushing work elsewhere. The trade-off is measurement effort: you need reopen tracking, escalation time logging and per-conversation cost attribution. That instrumentation is also what lets you improve the agent, so it pays for itself.

Where it is applied

  • A SaaS company comparing the cost of AI-resolved billing questions with the human cost for the same category before expanding the agent to account changes.
  • A bank tracking cost per resolved conversation for card-block requests across chat and voice channels, including telephony minutes.
  • A D2C retailer measuring resolution cost for order-status and returns queries over WhatsApp during a sale period.
  • A hospital measuring the cost of appointment reschedules handled end-to-end by a voice agent versus those transferred to reception.
  • An ed-tech provider evaluating whether its admissions agent resolves fee queries cheaply enough to justify extending it to scholarship questions.

Is Cost per resolved conversation a skill?

MetricA number you track, requiring reopen detection, escalation time capture and per-conversation cost attribution. Eazyware instruments it during delivery of customer service agents and reports it monthly under Maintenance & Support care plans.

Eazyware service that covers it: Software Maintenance & Support. Starting prices are on the pricing page.

Frequently asked questions

What should be included in the cost of a resolved conversation?

All inference and retrieval costs, voice or messaging platform charges, tooling fees allocated per conversation, and the loaded cost of any human time on escalated or reopened conversations. Leaving out escalation cost is the most common way the number is flattered.

How does it differ from cost per ticket deflected?

Deflection counts conversations that did not become tickets, including customers who abandoned. Resolution counts conversations where the issue was actually solved and not raised again. The resolved figure is smaller and harder to improve, but it reflects real value.

Related reading

Need Cost per resolved conversation built, not just explained?

PRJECT IN MIND?