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
Incoming tickets are assigned to teams by automation and routed by agent skills, SLAs exist with conditional SLAs reserved for Enterprise, macros carry 500 and 1,500 limits by tier, and Enterprise adds routing and capacity planning with custom reports — this is well past a shared inbox. But we found no public information on business-hours-aware SLA policies, breach warnings or escalation, merge and split, or first-response and resolution-time reporting by agent and queue, so I stop below the top band. 2 2 2 6 2 2