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
Conversations land in one message center with assignment to operators and a documented unassigned fallback area, and routing is genuinely rule-based: per-widget routing, group selection, and skills-based matching where an operator must hold every skill in a set, with advanced routing on the top plan. I found no public information on priorities, SLA targets, timers that warn before breach, first-response or resolution reporting, or search across conversations, so this stops short of what I need to run a team against a promised SLA. 4 5 7 2 10