What Counts as a Resolution? The Word Every AI Support Vendor Defines in Its Own Favor

A resolution should mean the customer problem closed with a confirmed outcome and no human handoff. In practice vendors differ: Intercom can count a resolution when a customer simply does not escalate, and Zendesk confirms one if a ticket is not reopened within 72 hours, so buyers often pay for activity rather than solved problems.

Why the definition matters more than the price

Every AI support vendor quotes a resolution rate and a per-resolution price. Buyers obsess over the price. The number that actually decides your outcome is the definition, because a resolution rate is only as honest as the event it counts.

If two vendors define resolution differently, their rates are not comparable, and neither is their pricing. You could pick the cheaper per-resolution fee and pay more, because that vendor counts more soft resolutions.

How Intercom, Zendesk, and Ada each count a resolution

Intercom Fin can count a resolution when a customer receives an answer and does not escalate, even if the answer was not actually helpful. Silence becomes success. Zendesk waits about 72 hours after an AI-handled conversation closes; if the customer does not reopen the ticket in that window, it is billed as an automated resolution. Ada, by design, is built to answer questions and deflect volume, which is closer to deflection than to resolution.

None of these are lies. They are just definitions that happen to favor the vendor headline number.

Activity billed as outcome: the buyer trap

When a resolution is defined as the absence of a complaint, you end up paying for activity, not outcomes. A customer who gives up and churns does not reopen the ticket. A customer who got a vague answer and solved it themselves does not escalate. Both get counted as resolved. Your dashboard looks great while your retention quietly leaks.

An honest definition: confirmed outcome, no human

A resolution should mean one thing: the customer problem closed with a confirmed outcome and no human handoff. Refund issued. Address changed. Order tracked down and the customer told. That is a bar you can be proud of, and it is the only one that maps cleanly to satisfaction and cost.

5 questions to ask any vendor

A fifth question is worth adding: what happens to the metric when a customer is unhappy but does not reply? If the honest answer is that it still counts as resolved, you now know exactly how inflated the headline number is.

Verify with a 100-ticket test

Take 100 real tickets, run them, and count only the ones that closed with a confirmed outcome and no human. Compare that to the vendor reported rate. The gap between the two is the honesty tax, and it is the most useful number you will collect in the whole evaluation.

Frequently asked questions

1) What is a resolution rate in AI customer service?

It is the share of tickets an AI closes without a human. The catch is that each vendor defines closed differently, from no escalation to no reopen within a set window, so the number is only meaningful once you know the definition.

2) How does Intercom Fin count a resolution?

Fin can count a resolution when a customer receives an answer and does not escalate, even if the answer was not actually helpful, which can inflate the reported rate.

3) How does Zendesk confirm an automated resolution?

Zendesk waits about 72 hours after an AI-handled conversation closes; if the ticket is not reopened in that window, it is billed as an automated resolution.