Zendesk resolved cases
The incremental metric-event export: one row per timing event on a ticket, of which we keep the ones that say a ticket was solved. Never a subject, never a comment, never a requester.
Access
- Kind
- A read-only key you paste
- What to give
- Subdomain, email and API token
- Why that one
- A Zendesk API token on an admin account: the incremental exports are admin-only. This source writes no spend: it reports what the spend produced.
What it attributes on its own
- From the source
- cases resolved per day, at the moment each was solved · reopens, counted apart so a case resolved twice is still one case
- Needs a rule or a trace
- which cases an assistant handled — Zendesk records no such thing, so cost per resolved case is a floor on the cost per assisted one · the workflow, which you tell us · how hard a case was: a password reset and an escalation both count as one
Connecting it
- Turn on token access. Admin Center → Apps and integrations → Zendesk API → Token access, then Add API token. Open ↗
- Use an admin account. The incremental exports are admin-only, so the token has to belong to an admin. It reads timing events and nothing else.
- Name the workflow, paste the three values, click Test and connect. Valistry reads the last seven days of solves, reports how many, then fills thirty.
Where your agents' assistant writes the ticket id into a trace, we can join case to spend exactly instead of by workflow; ask us and we will read it.