Connect Zendesk to prove a support agent's impact, volume handled, sliced any way you track it.
What you can measure
- Count of Tickets, Users, or Organizations over a window (created, solved, or updated dates).
- Slice by status, priority, type, tags, group, assignee, organization, satisfaction, brand, and your custom ticket fields.
Good things to measure: tickets solved per month, backlog by status, satisfaction-rated counts.
Reply-time, resolution-time and CSAT averages need Zendesk Explore and aren't available yet, today Zendesk measures volumes and counts (including satisfaction good/bad counts).
Connect it
In Zendesk, nothing to set up. You'll be asked for your subdomain (the part before .zendesk.com), then you authorize read-only access.
In Jents, Settings → Integrations → Zendesk → Connect → enter your subdomain → authorize (scope: read).
What Jents reads
Each metric is one Search count, a single number computed inside Zendesk. No tickets, messages, or personal data cross the boundary.
Specs
| Spec | Detail |
|---|---|
| Auth | OAuth (read) + your subdomain |
| API | Zendesk Search count (v2) |
| Access | Read-only, scoped |
| Reads | One server-side count per metric |
| Refresh | Daily, plus on-demand |
Privacy & security
Read-only counts only, never ticket text, requester names, or content. Every read goes through one audited, aggregate-only path and lands in your audit log. Credentials are encrypted at rest, we never train on or share your data, and you can disconnect anytime, see Privacy and Trust.