Platform capability

Service Desk and ITSM

Ticketing, SLAs, a knowledge base and asset tracking, with the onboarding and offboarding work behind each request automated and on record.

TicketingSLAsAsset trackingOnboarding requestsWorkflow automation

What you get

Tickets from every channel

Email, the self-service portal and phone intake all become tickets, routed to the right queue with a priority and a status that follows them to resolution.

SLAs watched for you

Response and resolution targets are set per service or customer, and the team is warned before a deadline is missed rather than after.

Answers before the ticket

A shared knowledge base serves the support team internally and customers on the portal, so many questions are answered before anyone opens a ticket.

Onboarding as a workflow

An onboarding or offboarding request arrives as a ticket, the automation behind it runs, and the ticket keeps the record of what happened.

Automation across systems

Visual flows chain steps across applications, started by a webhook, a schedule or an event, with around 200 ready-made connectors.

Agents governed like everyone else

Help desk access follows the same sign-on and permissions as the rest of the platform, and every ticket action is part of the same audit trail.

Where it fits

Service Desk and ITSM is one of eight capabilities in the ResorsIT Platform. Every one of them shares the same sign-on, the same permissions and the same audit trail.

Explore the whole platform

Under the hood

The components ResorsIT runs, connects and keeps up to date for this capability.

The details

A help desk that lives outside the identity system means an agent is provisioned once for email and again for the ticketing tool, and deprovisioned inconsistently when they leave. The requests that matter most, a new hire who needs accounts or a departure that needs them removed, are handled by hand from a checklist. ResorsIT runs the service desk and the automation behind it as part of the platform, so both problems go away together.

Tickets, Queues and SLAs

ResorsIT runs OTOBO, an ITIL-aligned, open-source service management platform built for IT help desks. Tickets are created from email, the customer self-service portal or phone intake, and route to the right queue with a priority and a status that tracks through to resolution. Service level agreements define response and resolution times per service or customer, and OTOBO watches those deadlines itself, notifying the team before a breach. A shared knowledge base publishes solutions internally for the support team or externally on the portal.

Assets Beside the Tickets

OTOBO’s configuration management database tracks IT assets and their relationships, so a request and the asset it concerns are held together. Configurable dashboards and reports cover ticket volume, response times and SLA compliance.

Automation Behind the Request

ActivePieces gives ResorsIT its visual automation: a canvas on which a flow chains steps across systems, started by a webhook, a schedule or an event in another application. Around 200 connectors ship with it, and more can be written against its TypeScript software development kit. The service desk is the front door for these flows. An onboarding or offboarding request arrives as a ticket, the automation runs, and the ticket carries the record of what happened.

Access That Matches the Rest of the Platform

Because OTOBO runs inside ResorsIT rather than beside it, agent access and permissions follow the same identity provider as every other application, and every ticket action is part of the platform’s audit trail rather than a separate log to check. The help desk stops being a separate system with its own accounts and becomes one governed piece of the same platform as everything else.