Audited resolution
An audited resolution is a support conversation counted as resolved (by the AI vendor's own flag, or by the most generous rule a careful vendor would use) that also passes three checks: the customer did not contact the company again within 7 days, the final reply did not redirect the customer instead of answering, and an LLM judge reading the conversation confirms the issue was resolved. It is defined in the Attify Audited Resolution Standard, v0.11.
The three checks#
A claim is counted at the first check it fails, so a report can say why claims failed in shares that add up.
Audited rate and gap#
- Audited rate: audited resolutions over eligible conversations with a request.
- Claimed rate: claimed resolutions over the same denominator.
- Gap: claimed minus audited, in percentage points, with a 95% interval.
Every audited number states its evidence tier: repeat contact only, judge-confirmed (the headline), or customer-confirmed.
Vendors' own "verified" terms#
Some vendors call their own count "verified". Since 18 May 2026 Zendesk bills only the automated resolutions that pass its own LLM check, and calls them "Verified resolutions": the AI agent answered, the customer asked for nothing further, and a model reading the conversation when it ended judged the request resolved. A conversation that fails the check is a "Contained resolution", and one a person finished is an "Assisted escalation"; neither counts against the resolution allowance (Zendesk).
In Attify's terms, a vendor's "Verified resolution" is the vendor's claim: a vendor's own resolved flag is tested exactly as set. It becomes an audited resolution only if it also passes the three checks above. Attify calls its own measure audited so the two are never confused. How other vendors define their outcome: automated resolution and support AI agent outcome definitions.
Example#
Synthetic example, for the arithmetic only: 1,000 eligible conversations with a request; the AI claimed 800. Of those, 120 had a repeat contact within 7 days and 60 ended in a handoff. The judge confirmed 85.0% of a sample of the remaining 620. Audited: 620 × 0.85 = 527. Audited rate 52.7% against a claimed rate of 80.0%, a 27.3-point gap.
Questions
Why 7 days?
- It is the standard's choice, closest to first contact resolution measured by the absence of a repeat contact within a window. Reports also show the audited rate at 24 hours, 3 days and 14 days, so readers can see how much the window matters.
Is Zendesk's "Verified resolution" the same as an audited resolution?
- No. It is Zendesk's own billing tier, decided by Zendesk's own model when the conversation ends. In Attify's terms it is the vendor's claim, and it becomes an audited resolution only if it also passes the three checks.
Does an audited resolution need the customer to say yes?
- No. That is a stronger tier, customer-confirmed, used where the data holds an explicit answer that the issue was resolved. None of the six help desks Attify reads asks it by default.
What happens to conversations where the customer only said thanks?
- Conversations with no request in them are left out of both the claimed and the audited rate, because there was nothing to resolve. The share left out is reported with a 95% interval.