Freshservice vs TOPdesk

Freshservice

The API documentation lists ticket intake from email, portal, phone, chat, Slack, MS Teams, a chatbot and monitoring feeds like PagerDuty and AWS CloudWatch, and an analytics article documents an unresolved-tickets metric with plan-dependent reporting duration limits. What the captured pages never show me is incidents told apart from service requests, and I found no public information on SLAs with escalation, assignment queues, an agent knowledge base or automation — a long source list alone does not make a service desk.

TOPdesk

Intake is genuinely multi-channel — email import with automatic categorisation and assignment, the portal, live chat, Teams and a WhatsApp add-on — with SLAs, an agent knowledge base, canned 'standard solutions', a four-step report wizard and custom dashboards with drag-and-drop widgets. Major incidents get a portal banner where users click 'I am affected', the AI proposes category and priority with what it does stated, and a mobile app sits in every package. We found no public information on time tracking on tickets, scheduled reports, or SLAs per service, customer or contract, so I stop short of the top band.

Freshservice

I found no public information on change requests, problem records, release management, a change calendar or any ITIL process certification in the pages captured for this review. The API documentation and the analytics article I read describe tickets, attachments and reporting metrics only.

TOPdesk

Problem management is the strongest piece: problems linked to incidents, root-cause analysis, conversion into known errors feeding a department-wide database, and a prioritised change list derived from impact, urgency and linked incidents. Change management offers workflow templates that turn standard changes into seconds of work, a planner, an explorer, forms and approvals in the self-service portal. We found no public information on normal and emergency change types, a change calendar or blackout periods, release management, an audit trail of approvals, or any named process certification.

Freshservice

We found no public information on an asset inventory, a configuration management database with relationships, discovery or licence tracking in the captured pages. The API documentation covers tickets, attachments and authentication, and the analytics article covers ticket metrics — nothing ties a ticket to a device, service or licence in what I read.

TOPdesk

Assets are unlimited at no extra cost whether you hold 50 or 50,000, with custom templates, role-based team visibility, warranty alerts, unused-licence detection and an impact overview for outages, fed by syncs from Intune, Entra ID, Active Directory and Lansweeper. The captures say you can see how assets relate and link them to users, tickets and changes. We found no public information on CI types with a documented relationship model, the product's own discovery, licence metering or data quality rules — so this reads as a well-fed asset register, and whether it is a CMDB the pages do not prove.

Freshservice

A service desk portal exists: users sign up, log in and create tickets through it, a custom SSL certificate is configurable for its domain, and the admin console manages multiple portals per organisation with customisable names, logos and login policies. I found no public information in the captured pages on a service catalog, request approvals, an end-user knowledge base, announcements or satisfaction surveys — what is documented about the portal is largely its domain and certificate configuration.

TOPdesk

The portal is described in shop-like terms — big buttons, drag-in tiles in the corporate design, predefined forms, status tracking, a searchable knowledge base with thumbs up and down, and single sign-on in every package; outages get a banner where users click 'I am affected'. Password reset automation and the Ebbot AI chat answering recurring questions are named, and satisfaction comes as star ratings and in-tool surveys. We found no public information on portal languages, conditional forms, costs and delivery times per catalog item, deflection measurement or accessibility, so this sits above the middle band and below the top.

Freshservice

There is a genuine documented REST API version 2.0 with OAuth, CORS, rate limits per named plan and a 60-day deprecation notice, plus SAML 2.0 and OpenID Connect single sign-on with guides for Okta, ADFS, Azure AD and OneLogin, and MS Teams, Slack, PagerDuty and AWS CloudWatch appear as ticket sources. I found no public information on an on-premise edition, SCIM provisioning, webhooks or uptime terms — everything captured, down to the pending Cloudflare migration, points to a vendor-run cloud service only.

TOPdesk

The API story is solid and free: REST with OData endpoints and webhooks covering calls, changes and assets, a marketplace of over 90 integrations, and named connectors for Teams, Exchange, Entra ID, Intune, Jira, SharePoint, TeamViewer, Dynatrace and Lansweeper; there is a virtual appliance, an on-premises e-book, a sandbox in every package, two-weekly free updates and RTO and RPO of one hour each. Feature parity between cloud and on-premises is not stated on the captured pages. We found no public information on SCIM provisioning, multi-tenant operation with separated client data, time and contract billing, migration from named tools, or a public status page.

Freshservice

The entity named on the captured pages is Freshworks Inc of San Mateo, California, so the vendor and copyright holder are non-EU. I found no public information on where tickets and attachments are stored or processed, on any subprocessor, or on a data processing agreement in the captured pages, and no on-premise edition that would keep records on the customer's own European servers appears in what I read.

TOPdesk

The chain starts European: TOPdesk Deutschland GmbH as controller with a named data protection officer, hosting in Germany, EU data residency stated as standard, SOC 2 and ISAE 3000 conformity in every package, and a stated promise that data is never used to train external AI models. What is missing is the rest of the chain: we found no public information on the hosting infrastructure, a subprocessor list with locations, or a published data processing agreement, and the residency attributes remain unconfirmed on the vendor's own captured pages. The virtual appliance can put records on the customer's own servers, but that is one sentence of marketing, not documentation of where every attachment ends up.

Freshservice

Four plan names — Starter, Growth, Pro and Enterprise — show up only in the API rate-limit table, and a support article promises to explain how to buy more licenses. We found no public price figure at all, per agent or otherwise, in the captured pages, so a buyer cannot compute any part of the annual cost from what is published here.

TOPdesk

The package structure is unusually open — three tiers with their inclusions listed, an operator defined as anyone who can open or edit tickets with dashboard-only users free, unlimited assets from 50 to 50,000 at no price difference, volume discounts, VAT stated as excluded, and a free API — but the one thing missing is a number: no captured page shows a price per operator, and one captured page states it contains no price, only a link to request one. Add-ons such as the reservation planner, WhatsApp integration and the health check are marked as add-ons with no prices, and the on-premises licence and onboarding are unpriced. I can describe the bill in detail; I cannot compute a single figure of it.