Service desk, incidents & requests
How this is scored
How tickets come in and get resolved: intake by email, portal, chat, phone and Microsoft Teams or Slack, incidents and service requests told apart, categories, priorities and an impact-urgency matrix, assignment rules and queues, SLAs with escalation and business hours, major incidents, templates and canned responses, a knowledge base for agents, automations and workflows, time tracking on tickets, and reports and dashboards on volume, resolution time and SLA compliance.
0 — Not a ticketing or service desk product; requests cannot be recorded and worked in it.
3 — Tickets from email and a web form with status, priority and assignment; SLAs, automation and reporting are basic or not described.
5 — Multi-channel intake (email, portal, chat or Teams), incidents and service requests told apart, assignment rules and queues, SLAs with escalation and business hours, an agent knowledge base, rule-based automations, and standard reports on volume, resolution time and SLA compliance.
8 — A visual workflow builder for any ticket type, major incident handling with communication to affected users, SLAs per service, customer and contract, skills- or load-based routing, time tracking on tickets, AI suggestions or classification with what they do stated, custom dashboards and scheduled reports, and a mobile app for agents.
10 — A service desk an organisation of thousands runs on: every workflow, form and SLA configurable without code and versioned, omnichannel intake with one history per requester, AI features documented with their data use and limits, operational level agreements and underpinning contracts tracked, and every report reproducible from an exportable ticket history.
The Change & Configuration Manager
Intake is broad — email with automatic ticket conversion and an AI email bot, the self-service portal, chat with IT support, and an AI chatbot on the portal, Microsoft Teams and email — with incidents, requests, problems and changes kept as distinct record types, automatic categorisation and prioritisation, routing by SLA, company, user group and category, SLA timers with escalation and violation prediction, a knowledge base reachable from within a ticket, reports and dashboards, and a mobile app listed. For a desk the size of mine we found no public information on major incident handling with communication to affected users, time tracking on tickets, or skills- or load-based routing, and the no-code workflow builder is documented for change workflows rather than for any ticket type. 2 6 12 18 20