TOPdesk

The Skeptic

Requests submitted through the portal are shown being auto-assigned, categorised and routed to the right team, and 'Contract & SLA Management' is a line in the feature overview — but the evidence stops at the feature name. We found no public information on SLA timers with breach warnings, escalation chains, priorities, or search across ticket bodies; the page names the module, the captured pages never show the clock. 1 3

Report an error

The Skeptic

Here the queue question gets a direct answer: email, portal, chat and social media inquiries 'can be handled in one place', the agent 'will see the entire conversation in one single ticket', customers can switch channels and continue where they left off, WhatsApp is offered, and portal users can track their own requests. Every channel that shares the queue is a text channel, though — we found no public information on telephony or call logging, and nothing on messenger consent handling, which is what separates this level from the next one up. 2 3

Report an error

The Skeptic

Two dedicated pages show knowledge managed as an asset: user ratings with change dates and review reminders, folders with pinning and archiving, one-click creation of an article from a solved ticket, technicians-only marking, portal search that surfaces articles while the user types, and answers published explicitly to shrink the ticket queue. We found no public information on multilingual articles, on suggestions shown to the agent while answering, or on deflection reported per article, so it sits just under the top level. 3 4

Report an error

The Skeptic

The captured pages give almost no purchase on this: we found no public information on a signable data-processing agreement, a stated retention period, a deletion path for a requester's data, agent roles, or an audit log — a data-protection page exists in the captures but yields no usable statements. The only access-restriction evidence anywhere is that knowledge content can be marked for technicians only, and that protects articles, not the requester's ticket history. 4 5

Report an error

The Skeptic

The platform page is concrete: a documented REST API with webhooks and OData endpoints, an offer to build custom connections, and more than a hundred integrations with names attached — Jira, Entra ID, SharePoint, Intune, Active Directory, Dynatrace. The list leans ITSM (asset discovery, DevOps, meeting-room booking); we found no public information on rate limits, SCIM provisioning, a sandbox, or CRM and shop context shown inside the ticket. 1 6

Report an error

The Skeptic

Every sovereignty attribute comes back unknown: we found no public information on where the ticket archive is hosted, on the contracting chain beyond the entity name, on a subprocessor list, or on whether vendor support can read customer instances. A Dutch legal-entity name and a German-language privacy webinar are the only European signals, and neither of those is a residency commitment. 1 5

Report an error

The Skeptic

We found no public information on pricing at all: no per-agent figure, no tier names, no billing period, no minimum term, and nothing telling a buyer at which tier the channels or SLA capabilities begin. There is no figure here for a support lead to compute an invoice from; the only path to a number runs through a sales conversation. 1

Report an error