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 the real strength: skills-based, language, priority and workload balancing plus intent detection and custom attributes, all built with a no-code visual rule builder. But the SLA half of the engine is undocumented — no public information on response-time targets, breach warnings, escalation timers, macros, merge and split, or ticket search — and the reporting that is documented is automated QA and performance scoring rather than first-response and resolution times by agent and queue. 4 5 1 3