What is a ticketing system?

A ticketing system is software that gathers incoming questions, fault reports and tasks in one place and follows them all the way to closure. Each ticket gets an owner, a priority and an expected resolution time, and the system provides an overview of what is open, what is overdue and where the bottlenecks are.

Which ticketing system is best for Nordic organisations?

It depends on where the requests come from. For internal IT, Freshservice offers the best balance between ITIL support and simplicity for most Nordic organisations, with Swedish implementation. In the public sector you will most often meet TOPdesk, and if requests come from customers, Freshdesk is the right product.

What is the difference between a ticketing system and a customer service system?

A customer service system handles requests from your customers and is built around external channels such as email, chat, phone and social media. A ticketing system is a broader term that also covers internal requests, IT support, fault reports and work orders. Many organisations need both and run them integrated.

Do we need ITIL to implement a ticketing system?

No. ITIL is a framework of good practice, not a requirement. Most organisations get a long way with incident and request management, and should introduce problem, change and configuration management only when someone owns those processes. Activating the whole framework from day one usually makes the system heavier without solving anything.

What does a ticketing system cost?

These systems are usually priced per agent and month, and the range between the simpler tools and the enterprise platforms is wide. List price says little, however: asset management, AI features and integrations are usually add-ons. Calculate total cost over three years including implementation and operations – we are happy to produce a comparison in SEK for your setup.

How long does it take to implement a ticketing system?

A basic implementation with a request flow, categories and a self-service portal normally takes two to four weeks. The timeline is driven by the number of integrations, how much history needs migrating and how well your processes are already defined. Full ITIL coverage with asset and change management takes closer to two or three months.

Can we migrate our existing tickets to a new system?

Yes. Tickets, categories, users, attachments and comments can normally be migrated in a structured way. What requires most thought is mapping your current statuses and fields to the new system’s structure. We always run the migration in a test environment first so that nothing is lost – read more in our guide to switching ticketing system.

Ticketing systems 2026: 6 platforms compared

We compare six ticketing systems for Nordic organisations on request type, ITIL support, automation, price level and local support – for internal IT, service desk and customer requests.

Quick answer

A ticketing system gathers incoming questions, fault reports and tasks in one place and follows them to closure with an owner, a priority and an SLA. For internal IT, Freshservice and Jira Service Management are the most common choices, while Freshdesk fits when the requests come from customers rather than colleagues.

What decides the choice of ticketing system?

Who submits the requests. Internal employees and external customers place completely different demands on the portal, permissions and communication. That is the first fork in the decision – and the one most often skipped.
How much ITIL you actually need. Incident and request management is enough for most. Problem, change and configuration management is powerful but requires someone to own the process – otherwise it just adds mandatory fields.
Automation and self-service. The gain rarely lies in resolving tickets faster, but in tickets never arising. A knowledge base, forms and automated workflows do more for the workload than extra agents do.
Integrations with your existing systems. A ticketing system that does not know your users, assets and contracts becomes an isolated island. Map the integrations before comparing feature lists.
Data residency and GDPR. Tickets often contain personal data, sometimes sensitive. For the public sector and regulated industries, data residency frequently decides which systems are viable at all.

“Almost everyone we meet believes they need a more powerful system. In practice the process is usually what is missing – the same tickets arrive again and again, and no system in the world solves that for you. Start by categorising one month of tickets.”
— Scaly’s ticket management consultants

Comparison table: six ticketing systems at a glance

System	Fits	Strengths	Weaknesses	Request type and automation	Operations and time to live	Public list price
Freshservice	Internal IT and service desks with 3–50 technicians wanting order without starting a platform project.	Only agents are licensed – everyone who submits a request is free SSO and SAML included, up to 99 parallel configurations Change, problem and release already on Pro Nordic implementation and support via Scaly	Live translation requires Freddy Copilot at USD 29/agent/month Asset management on Pro holds 100 ITAM units; a server counts four The portal cap follows the workspace cap, normally 25 Freddy AI Agent, sandbox and audit logs are Enterprise	Internal requests and IT support Orchestration: 5,000 transactions/month on Pro Self-service portal included	Part time is enough 2–4 weeks to live Upgrades happen without you doing anything	Starter 19 · Growth 49 Pro USD 99 (EUR 84 in EU)
Jira Service Management	IT and support teams close to development, where Jira is already running and developers keep it.	Developers are already there – one tool fewer to roll out Standard is roughly half of Freshservice Pro at list price Up to 300 help centres per site on Premium Knowledge base without a Confluence licence, Assets Discovery is free	Standard lacks change management, CAB, risk assessment and an uptime SLA Multiple identity providers require Enterprise, with no public price SSO via Atlassian Guard is billed across your entire Atlassian estate Marketplace apps are billed on the site’s user count	Internal requests and development work in one tool Assets caps: Standard 5,000, Premium 50,000 objects Virtual agent from Premium	Atlassian’s own Forrester study: at least 1.5 FTE ongoing Licence = 46% of three-year cost, labour 54%	Standard USD 10,300/yr Premium USD 26,000/yr (26–50 agents)
HaloITSM	Process-heavy organisations from ~20 technicians with formalised IT processes or on-premise requirements.	Everything in a single tier – no feature split Contract, asset and SLA management on a par with the large platforms Handles on-premise and special hosting requirements Nordic implementation via Scaly	Custom reports require SQL knowledge Onboarding is mandatory per the vendor’s pricing page, at a quoted price The virtual agent runs via a third party Without a process owner it becomes heavier than the problem	Internal requests, IT and assets Automation requires configuration Full ITIL coverage	Process owner + part time 4–8 weeks to live SQL skills needed in-house	GBP 69/agent/month single tier
Freshdesk	Customer service where requests come from outside. Often run alongside Freshservice internally.	Built for external channels – email, chat, telephony, social Strong AI for customer requests and deflection Same vendor and login as Freshservice Nordic implementation via Scaly	Lacks real ITIL support No IT asset management The wrong product for internal IT support Telephony is a separate product with its own cost	Customer requests, not internal Automatic categorisation and routing Self-service for customers	No technical resource needed 2 weeks to live Part-time admin is enough	Public price list per agent and month
ServiceNow	Large groups with an in-house platform team wanting to run the whole business in one system.	The most complete platform on the market Reaches far beyond IT – HR, finance, facilities Enterprise-grade governance and reporting Strong Swedish partner network	Modules are priced separately Business approvers are their own user type with their own cost Upgrades require testing your customisations Almost always oversized below a few thousand users	Requests across the whole business Integration platform with its own licence Complete ITIL	Assumes a platform owner and developer Implementation measured in quarters Upgrades are projects	No public price
TOPdesk	Swedish municipalities, schools or property companies – often ten years in the same system with facilities in the same instance.	Established and safe with a long Nordic track record Broader than IT – property and facilities in the same system Local presence and a known model in the public sector Low perceived risk in renewing	Self-service and the employee experience feel dated AI and automation are thin next to the leaders Cross-system orchestration, such as on- and offboarding, is weak If facilities are included the switch is organisational, not technical	Internal requests, IT and facilities Limited automation Broad business coverage	Often already staffed after many years The switch is bigger than the ITSM question if facilities are included	No public list price

List prices are the vendors’ own public annual-billing prices, checked 2026-08-19 – verify the current price before deciding. <strong>The operations line decides total cost</strong> and never appears in a quote: for Jira Service Management it draws on Atlassian’s own Forrester study, otherwise on Scaly’s estimates from Nordic implementations. If you need a purpose-built ITSM tool with ITIL depth, see our <a href="/en/itsm-systems">ITSM system comparison</a>.

The six ticketing systems in detail

Freshservice – the best balance for internal IT

Freshservice is built for internal service desks and covers request, incident, problem and change management plus asset management, without the administrative weight the very large ITSM tools bring. A self-service portal and automated workflows let an IT department of a few people handle an entire organisation’s requests.

Bäst för: IT departments and internal service desks that want ITIL support without a platform project.

Tänk på: asset management and the more advanced AI features sit in higher tiers – check which level you actually need before comparing prices.

Jira Service Management – natural if you already run Jira

For organisations where development already lives in Jira, Service Management is the logical choice: requests and development work connect in the same tool, making escalation from a support ticket to a bug fix straightforward. Pricing is competitive, particularly for smaller teams.

Bäst för: IT and support teams close to the development organisation, above all in tech companies.

Tänk på: it requires more configuration than it appears to, and for business request handling outside IT it often feels developer-oriented. Scaly is not an Atlassian partner – we include it here because it belongs in the comparison.

HaloITSM – the deepest ITIL support of the alternatives

HaloITSM covers virtually the whole ITIL framework and has very strong contract, asset and SLA management. Where other systems require add-ons to reach full process coverage, most of it is already included, which makes total cost predictable for organisations that genuinely need the breadth.

Bäst för: organisations with formalised IT processes and requirements for complete ITIL coverage.

Tänk på: the power costs configuration time – without someone owning the process the system quickly becomes heavier than the problem it was meant to solve.

TOPdesk – the Nordic classic

TOPdesk has a long Nordic track record, particularly among municipalities, schools, property companies and healthcare-adjacent operations. Many have run it for ten years or more, often with property and facilities in the same instance. That makes it a safe choice rarely questioned.

Bäst för: the public sector and property-adjacent operations wanting IT and facilities in one shared system.

Tänk på: self-service and the employee experience are where the gap to the leaders shows most clearly, and cross-system orchestration is weak. If facilities share the instance, the decision also moves outside IT.

Freshdesk – when the requests come from customers

Freshdesk is built for external customer requests rather than internal IT: email, chat, telephony and social channels are gathered in the same ticket view, with automatic categorisation and AI support. Many organisations run Freshdesk for customers and Freshservice internally, with the same login and the same vendor.

Bäst för: customer service and support teams whose requests come from outside.

Tänk på: it lacks real ITIL support and asset management – for internal IT, Freshservice is the right product in the same family. See our <a href="/en/customer-service-system">customer service system comparison</a>.

ServiceNow – the enterprise choice

ServiceNow is the most complete platform in the category and reaches far beyond IT: HR, finance and business processes can run in the same system. For very large organisations with their own platform team it is often the right answer.

Bäst för: large enterprises and groups with enterprise requirements and resources to run the platform.

Tänk på: cost and complexity are in a different class – for organisations under a few thousand users it is almost always oversized. See our <a href="/en/servicenow-alternative">ServiceNow alternative</a>.

How to choose the right ticketing system

Requests come from your own employees: start with Freshservice or Jira Service Management. Both provide ITIL support and self-service without requiring a platform team.
Requests come from customers: what you actually need is a customer service system – read the customer service system comparison instead.
You have formalised ITIL processes: then what you need is a purpose-built ITSM tool. See our ITSM system comparison, where ServiceNow, BMC, Jira Service Management, HaloITSM, Freshservice, Ivanti, TOPdesk and ManageEngine are weighed against each other.
You are on an old TOPdesk agreement: compare on self-service and orchestration, not the feature list. If property shares the instance, the switch is organisational, not technical.
You already have a system but nobody uses it: start with the process, not with a replacement. Read our guide to switching ticketing system before you procure.

Ticketing system, issue tracking or ticket management – the same thing?

In practice, yes. Ticketing system is the most common English term, while helpdesk, issue tracking and ticket management are used for the same thing. In Swedish the established term is ärendehanteringssystem, with ärendesystem as the short form. The differences lie not in the term but in what the system is used for: internal IT support and service desk, external customer requests, or business flows such as deviations and work orders. That question – not the wording – decides which system you should choose, and it is the starting point for the comparison above. For the fundamentals, read what ticket management is.

Unsure which ticketing system fits you?

We go through your request types, volumes and integrations and give you a straight answer on which system fits – including when the answer is one we do not sell. The consultation is free and takes about 30 minutes.

Book a free consultation Calculate total cost

Read on

Frequently asked questions about ticketing systems

Are ticketing system, issue tracking and ticket management the same thing?: Yes, in practice. Ticketing system is the most common English term, issue tracking and helpdesk are used for the same thing, and in Swedish the established term is ärendehanteringssystem with ärendesystem as the short form. What actually separates the systems is not the term but the use: internal IT support, external customer requests, or business flows such as deviations and work orders.
What is a ticketing system?: A ticketing system is software that gathers incoming questions, fault reports and tasks in one place and follows them all the way to closure. Each ticket gets an owner, a priority and an expected resolution time, and the system provides an overview of what is open, what is overdue and where the bottlenecks are.
Which ticketing system is best for Nordic organisations?: It depends on where the requests come from. For internal IT, Freshservice offers the best balance between ITIL support and simplicity for most Nordic organisations, with Swedish implementation. In the public sector you will most often meet TOPdesk, and if requests come from customers, Freshdesk is the right product.
What is the difference between a ticketing system and a customer service system?: A customer service system handles requests from your customers and is built around external channels such as email, chat, phone and social media. A ticketing system is a broader term that also covers internal requests, IT support, fault reports and work orders. Many organisations need both and run them integrated.
Do we need ITIL to implement a ticketing system?: No. ITIL is a framework of good practice, not a requirement. Most organisations get a long way with incident and request management, and should introduce problem, change and configuration management only when someone owns those processes. Activating the whole framework from day one usually makes the system heavier without solving anything.
What does a ticketing system cost?: These systems are usually priced per agent and month, and the range between the simpler tools and the enterprise platforms is wide. List price says little, however: asset management, AI features and integrations are usually add-ons. Calculate total cost over three years including implementation and operations – we are happy to produce a comparison in SEK for your setup.
How long does it take to implement a ticketing system?: A basic implementation with a request flow, categories and a self-service portal normally takes two to four weeks. The timeline is driven by the number of integrations, how much history needs migrating and how well your processes are already defined. Full ITIL coverage with asset and change management takes closer to two or three months.
Can we migrate our existing tickets to a new system?: Yes. Tickets, categories, users, attachments and comments can normally be migrated in a structured way. What requires most thought is mapping your current statuses and fields to the new system’s structure. We always run the migration in a test environment first so that nothing is lost – read more in our guide to switching ticketing system.