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 Solo IT Admin
Email, a portal, social channels and an AI chatbot that works in Microsoft Teams and by email all create tickets, with incidents, requests, problems and changes as separate record types, routing by category, company and user group, automatic categorisation and prioritisation, SLA timers that predict violations and escalate, and a knowledge base built into the ticket; reports, dashboards, BI and a mobile app for agents are listed too. What I could not find on the captured pages: major-incident handling with communication to affected users, time tracking on tickets, or skills- or load-based routing. For a one-person department, the intake side is exactly what I need. 12 18 2 6 7