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 Skeptic
Routing is real, not brochure copy: assignment rules match email sender, recipient, subject, contact attributes and custom data, apply first-match in a reorderable priority order, and forwarded emails land as tickets with assignment, statuses, tags, internal notes, search, filters and performance reports. What I read for and did not find is the SLA layer — we found no public information on SLA targets, breach warnings, escalation, priorities or business-hours policies — and the reporting that is documented is department-level, with the vendor stating that tickets assigned straight to an agent without a department are excluded from the departments report. 3 4 5