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 Skeptic
The engine is real: tickets carry statuses, tags and a split action, and SLA is a defined feature with first-answer, next-answer, first-assign and first-resolve levels, business hours (timers extended rather than paused outside them), an SLA log, and report endpoints for SLA compliance, load and agent performance. My tier-reading: SLA starts on Team at $29 billed annually or $35 monthly, and even unlevelled tickets get an internal 7-day answer time feeding the ticket grid's Importance ordering. I found no documentation of ticket merge, breach warnings or escalation on breach, or skills- or load-based assignment beyond the To-solve distribution. 4 5 13 11