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 Support Lead
The SLA machinery is real: separate first-answer, next-answer, first-resolve and call-answer timers, business hours that extend the clock rather than pause it, a To-solve queue distributed by importance, and an SLA log with compliance and load reports I could actually take to a quarterly review. Rules and time rules handle routing at ticket creation, and tags, canned messages, department-level roles and ticket splitting are documented. I found no public information on warnings before a timer breaches, escalation paths, ticket merging, or assignment by skill, so it sits a notch below the top of this scale. 4 5 13 1