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 rules by page, domain and country, ticket rules like priority customers skipping the line, four statuses with priority, owner and source pinned to every ticket, first-response and resolution reporting per group and per agent, and an MCP server that searches tickets and transcripts — that is a real engine. But no SLA policy with breach warnings or escalation appears anywhere in the captures, and the help pages say the native ticketing was sunset in January 2025 with accounts created after June 2023 pointed at HelpDesk.com, so I would verify exactly which engine I am buying. 4 5 5 11 4