What Counts as a Resolution? The Fine Print of Per Resolution Pricing

The Illusion of a Standard Price

Per-resolution pricing has become the accepted model for AI customer support agents. Fin charges $0.99 per resolution. HubSpot's customer agent dropped to $0.50 per resolved conversation. Salesforce Agentforce charges $2.00 per conversation. These headline numbers look comparable, but they are not. The real price is hidden in the contractual fine print, specifically in how each vendor defines a "resolution". The same volume of customer interactions can produce invoices that differ by 30 to 50 percent. The definition is the price.

Resolution Versus Conversation: The First Cost Variable

The most basic distinction in these contracts is between paying per conversation and paying per resolution. A per-conversation price charges for every interaction, regardless of whether the AI agent succeeded or failed. This means you pay for the failures.

Consider an agent with a 60 percent resolution rate. If you have 100 conversations at $1.00 each, your bill is $100. You paid for 40 unresolved issues. A true per-resolution model, however, should only charge for success. For those same 100 conversations, you would pay only for the 60 successful outcomes. At $1.00 per resolution, your bill would be $60. This simple difference highlights the importance of understanding what a resolved conversation means according to your contract. Paying for failures dramatically increases your effective cost per successful outcome.

Defining the Billable Trigger Event

Moving beyond the basic conversation versus resolution model, the core of the issue is the trigger event. What specific action or condition officially marks a conversation as resolved and therefore billable? This trigger is the contractual definition of success and it varies significantly between vendors. Each variant shifts the financial risk. A strict definition protects the buyer, while a loose one favors the vendor.

The "silence-as-resolution" definition is particularly problematic. It is the most vendor-friendly option and can easily count a customer who gives up in frustration as a success. This approach frequently leads to billing disputes and customer dissatisfaction.

The Reopen Window: A Safety Net for Charges

A resolution trigger should not be the final word on a charge. A well-structured contract includes a "reopen window" or settlement period, which functions as a crucial safety net. This means a charge for a resolution is held provisionally for a defined period, such as 24, 48 or 72 hours. If the customer re-engages about the same issue within that window, the original charge is automatically reversed. The issue was clearly not resolved.

This mechanism corrects for prematurely triggered charges and ensures you only pay for lasting solutions. The length of this window is a key negotiation point. A short window offers weak protection, while its complete absence is a major red flag for any buyer. The settlement window is also where the vendor's risk lives, a dynamic we explored in Pricing AI Outcomes as Risk Contracts.

Billing for Complex and Partial Resolutions

Customer conversations are rarely neat, single-issue interactions. This complexity is where many billing models break down and create ambiguity. If a user asks three distinct questions in one chat, is that one billable resolution or three? What happens if the agent answers two questions correctly but fails on the third?

Another common scenario involves partial resolutions, where an AI agent performs most of the work before a necessary human handoff. The contract must specify how these situations are priced. Undefined edge cases are a primary source of billing disputes and can erode the trust between a vendor and buyer. Clear rules for these complex scenarios are essential for accurate billing.

The Critical Need for Verification and Audit

A precise definition of a resolution is meaningless if it cannot be verified. Both the vendor and the buyer need a transparent, auditable system to maintain a healthy business relationship. Every single charge on an invoice must be traceable to a clear audit trail of events. This trail should include conversation transcripts, timestamps for trigger events, records of human handoffs and logs of any reopen events.

A charge that cannot be traced back to the events that justify it is an error waiting to be disputed. We covered how this audit trail works in practice in How Transparent Invoicing Stops AI Billing Disputes.

For Vendors: Engineer Your Pricing for Clarity

For vendors building AI agents, the lesson is to treat your pricing definition like code. Define "resolution" with a set of machine-checkable rules, not an ambiguous paragraph of legal text. This precision eliminates confusion for both your team and your customers. Our guide on defining concrete billable outcomes shows what these definitions look like.

You should price that definition honestly. A stricter, more buyer-friendly definition delivers more guaranteed value and can support a higher per-unit price. A loose definition invites disputes that will erode your margins and damage your reputation. From day one, instrument your product to capture every confirmation, handoff and reopen event. This data is the foundation of trustworthy pricing and a scalable business.

For Buyers: A Pre-Signature Checklist

For buyers evaluating AI solutions, the headline price is only the beginning of the conversation. Before signing any contract, you must ask these critical questions to understand what you are actually buying:

• What specific event triggers a billable resolution?
• What reverses a charge and how long is the reopen window?
• How are partial or multi-issue conversations billed?
• Can I access the raw event logs that justify each line item on my invoice?

Never compare per-unit prices without first comparing the definitions behind them. This is the only way to accurately forecast your cost and ensure you are paying for real value.

Building Billing on a Foundation of Proof

Sustainable partnerships in the AI industry are built on precision and auditable proof. The contract must align with the invoice and the invoice must align with the underlying events that prove value was delivered.

witn is billing infrastructure built for exactly this. Express resolution definitions as conditions over events. Hold charges through settlement windows until reversals clear. Get invoices where every line traces back to its proof. Read the docs to see how it works.