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
Tickets come with status, priority, owner and source, reassignment to agents or groups, duplicate threads merging into one, and first-response and resolution-time reporting by agent and group — enough to run and report on a real queue. I found no public information on SLA policies with breach warnings and escalation. The help centre also states the native tickets feature was sunset from January 2025 and that accounts created after June 1, 2023 are directed to HelpDesk.com tickets, so I would confirm exactly which engine carries my SLA before signing. 4 5 5 4