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 routing engine is real: SLA targets sit on entry points and inboxes with documented precedence on transfers and reassignment, due dates drive queue priority, and replies can be pinned to the same agent within a time window or pushed to the next available one. Canned responses and rules are documented and SLA attainment is reported by channel and available via API, though that report and the channel-mix report are both stated to be sunset soon, and I found no public information on search across tickets, merge and split, or breach warnings and escalation. 2 3 5