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 Municipal IT Lead
Intake by email, telephone, portal, chat and integrated systems with automatic caller identification, incidents and service requests as separate processes, an urgency-impact priority matrix, assignment by team, role, location, customer or service, and service level agreements configurable per service, priority, contract, customer and support calendar with automatic escalation are all documented, alongside a graphical workflow designer, ticket templates, per-ticket time tracking, a major-incident service portal, machine-learning matching of solutions with automatic delegation to the right groups, and custom dashboards on volume, resolution times and SLA compliance. We found no public information on scheduled reports or a dedicated agent mobile app, and the channel list names no Microsoft Teams or Slack intake, which keeps this a step below the top level. 3 8 11 12 14 18