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 Data Protection Officer
Tickets carry status, priority, owner and source, standing rules run automatically (priority customers skip the line, duplicates merge into one thread, follow-ups auto-solve after four days), and reports cover first-response and resolution time per agent and group. We found no public information on SLA policies per queue with breach warnings or business-hours escalation. The captured pages give different pictures of ticketing's future: one help article schedules the native Tickets feature for sunset in January 2025 with newer accounts pointed to HelpDesk.com, while other pages describe creating and managing tickets in the Text inbox. 4 5 5 4