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 engine is deep in the ways that matter on the hundredth reply: six SLA timer types from first answer to call pickup, business hours that extend the clock rather than pause it, an SLA log with compliance reports by agent and department, canned and predefined messages, and ticket split with assignment to the right department. What holds it down is silence on the parts an agent feels daily: I found no public information on merging tickets, on breach warnings or escalation when a timer expires, or on skills- or load-based routing — the To solve distribution is named but its logic is not described. Search across ten thousand tickets is likewise not documented, and that is the first thing I look for. 4 5 11 13