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
Assignment to named operators, priorities, statuses, tags, notes, smart views and macros are all documented, and the ticket data endpoint exposes departments and custom fields — good bones for a working queue. But the ticketing page itself states no SLA or queue features, and we found no public information on ticket search or first-response and resolution reporting. The API docs quietly admit assignment resets to null the moment a ticket is solved, which is exactly the kind of quirk you feel at the hundredth reply. 4 5 7 1 4