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 — A shared mailbox with labels; no ownership, no status model, no history beyond the thread.
3 — Tickets with assignment and open/closed status, but routing is manual, there are no SLA timers and search covers subject lines only.
5 — Queues with rules-based routing, priorities, a working status model, SLA timers with breach warnings, and full-text search across ticket bodies.
8 — Business-hours-aware SLA policies per queue or customer, escalation chains, macros and triggers, merge and split, 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
Two SLA timers are genuinely documented — a Company timer that counts down only during your business hours and a per-marketplace timer that runs around the clock with Amazon's 24-hour default — with an Overdue-plus-minutes readout, To Do and Resolved states, and a mailbox sorted by least time left. That is a real engine, but we found no public information on escalation chains, merge and split, or first-response and resolution-time reporting by agent and queue; "intelligent ticket routing" is a homepage phrase with no settings page behind it in the captured pages. 1 3 4 5