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
Routing is the real thing here: skill, language, priority and custom-attribute rules in a no-code builder, intent detection that routes or filters spam before a human sees it, and workload balancing — the vendor itself says ticketing is a feature, not the identity, and the routing evidence backs that up. I found no public information on SLA targets with breach warnings, macros, ticket merge and split, or first-response and resolution-time reporting — the machinery that makes a queue manageable at the hundredth reply. The Auto-QA dashboards scoring every conversation are the part I would least trust to help anyone close a ticket. 4 1 3 1