Ticketing, queues & SLA
How this is scored
The engine: how work is routed, prioritised, escalated and measured — and whether an agent can find the ticket they need among ten thousand.
0 — Not a ticketing tool: requests stay in a shared mailbox or chat with no ticket, owner or status of their own.
3 — Tickets with assignment, a status and a conversation history, worked from a shared inbox with views or filters.
5 — Tickets routed by rules or automations to teams or agents, priorities and statuses, SLA targets or response-time reporting, and search across tickets.
8 — Business-hours-aware SLA policies per queue or customer with breach warnings and escalation, macros and triggers, merge and split, skills- or load-based assignment, and reporting on first-response and resolution time by agent and queue.
10 — The workload is managed rather than merely tracked: capacity-aware assignment, SLA per contract with reporting an account manager could show a customer, audit of every status change, and search that finds the ticket from a half-remembered phrase.
The Agent Advocate
The queues documentation is the real thing: customizable queues with dynamic per-viewer assignment, JQL search, and queues that surface work by how close it is to breaching an SLA, with goals set via JQL, pause conditions and business-hours calendars in the SLA articles, plus escalation by plan and per-plan automation steps. But I found no public information on macros, merge and split, or first-response and resolution reporting by agent and queue, so it stops short of the top band — six years of replies and no documented canned response is a real gap. 6 7 2