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 Data Protection Officer
Queues are real: preconfigured and custom queues with list, board and calendar views, JQL search, and urgency queues that surface work items approaching an SLA breach, while SLA goals are defined per project with business-hours calendars and pause conditions and escalation runs manual, automatic or API-driven depending on plan. This sits in the upper-middle band. We found no public information on macros, merge and split, skills- or load-based assignment, or first-response and resolution reporting by agent and queue, which is what separates a managed workload from a tracked one. 6 7 2 14