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
Routing is real and well documented: round-robin, origin, intent and custom strategies, assignment to specific agents, team pickup or a private sub-inbox, canned messages, reminders, and clear escalation paths from the AI agent to a human. But everything my team's SLA stands on is undocumented here — we found no public information on priorities, SLA timers or breach warnings, first-response or resolution reporting, merge and split, or search across conversations; the only service level agreement named in the terms is a contractual one reserved for Enterprise Plan customers. A four: stronger than a shared inbox with views, short of a queue I can manage against a promise. 1 5 6 8 2