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
Skills-based routing, incoming tickets automatically assigned to the right team, SLAs with conditional SLAs at the Enterprise tier, macros by tier, and helpdesk areas for queue organisation give me most of the routing spine my team needs. I found no public information on SLA breach warnings, ticket merge and split, or first-response and resolution reporting broken out by agent and queue, and the documented routing and capacity planning at Enterprise is as close as the pages get to capacity-aware assignment. 2 2 6 2