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 Support Lead
Routing is genuinely there: assignment rules with contact, email and custom-data conditions, drag-and-drop ordering, a default fallback, and chats routed to departments or agents in a shared inbox with statuses, tags, notes, search and filters. What the pages don't show is what my team runs on — anything on SLA targets, timers that warn before a breach, escalation paths, or first-response and resolution reporting by agent and queue. The departments report also skips tickets assigned straight to an individual agent, which would hide part of my queue from any quarterly review. 3 4 5