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 documented properly: three modes including skills-based matching where an operator must hold every skill in a set, per-widget configuration, and unmatched conversations falling to an Unassigned inbox section. But the measured half of the engine is dark — I found no public information on SLA targets, priorities, escalation, macros, or first-response and resolution reporting, and nothing shows an agent can search the archive for a half-remembered old thread. 4 5 7 10