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 Integrator
Skills-based routing, assignment of incoming tickets to the right team, macros with published limits per tier, SLAs including conditional SLAs at the top tier, and at Enterprise sophisticated routing and capacity planning for complex omnichannel deployments are all documented. That reads as a real workload engine rather than a tracked inbox. We found no public information on business-hours SLA policies with breach warnings and escalation, on merging and splitting tickets, or on first-response and resolution-time reporting by agent and queue. 2 6 2