Cloud product

Helpdesk for support, service desks, and change workflows.

Tickets, email, knowledge base, roles, and multi-step processes in one central service platform.

Built for internal IT, MSPs, and organizations with multiple departments that need support handling without losing information in mailbox chaos.

Ticketing Email integration FAQ / self-service Change workflows
Core value

What the helpdesk brings together day to day.

The system combines classic support handling with structured process control.

Tickets

Control requests centrally

Internal and external cases run through one ticket model instead of fragmented inboxes and side channels.

  • Portal for customers and employees
  • Guest ticket creation when needed
  • Traceable status and history
Knowledge

Build self-service and FAQ

Recurring questions can be reduced through a knowledge base and self-service before they turn into tickets.

  • FAQ inside the customer portal
  • Fewer repetitive support cases
  • Better quality at first contact
Control

Keep roles, SLAs, and responsibilities clean

Departments, groups, and roles stay connected to tickets and processes in a traceable way.

  • Separate roles for admins, agents, and customers
  • SLA and priority control
  • Clear ownership between teams
Changes

Map multi-step work cleanly

More complex cases such as new VMs or system changes can be handled as structured changes with fixed steps.

  • Department-based workflows
  • Templates for repeatable changes
  • Automatic handover into the next step
Functional areas

These service areas become usable inside one platform.

The product page groups functions around real service work instead of listing isolated technical checkboxes.

Ticketing

Central ticket management

Internal and external requests, incidents, and tasks can be handled inside one consistent ticket flow.

  • Portal-based and incoming tickets
  • Status, priorities, and history
  • Asset and inventory relation to tickets
Email

Email integration without media breaks

Incoming and outgoing communication stays directly tied to the ticket context.

  • Replies mapped back to existing tickets
  • No isolated support inboxes
  • Unified communication across portal and email
Self-service

Customer portal, FAQ, and knowledge base

Users can find answers themselves or open well-structured tickets through the portal.

  • Self-service for standard questions
  • FAQ content for faster resolutions
  • Guest tickets for easier entry
Organization

Roles and ownership between teams

Groups, departments, and roles help route cases to the right place without losing context.

  • Role model for admins, agents, and customers
  • Department and group based ownership
  • Traceable handovers between teams
Process

Change management with workflows

Recurring or complex changes can run through structured multi-step process chains.

  • Templates for standard changes
  • Department-specific approvals
  • Automatic follow-up actions when a step completes
Technical

Deployment, import, and future readiness

The system can be introduced into existing environments and populated from older tools.

  • Windows-capable deployment
  • CSV import from Jira, ServiceNow, or osTicket
  • SQLite or MSSQL as data layer
Example flow

How a typical service case works.

The example shows the path from an incoming request to a structured change.

01 Request enters through portal or email

A customer raises an issue through the portal or email and may already find the right FAQ answer before opening a ticket.

02 Ticket is routed correctly

If a ticket is needed, it lands directly with the right department or group and remains traceable there.

03 Replies stay in the same context

Email replies are mapped back to the same ticket instead of creating disconnected parallel threads.

04 A change starts for more complex cases

For cases such as a new VM or system switch, a change with fixed steps and involved teams can be started.

Fit & technical setup

Who the product is built for and what sits behind it technically.

The helpdesk is strongest where support, mail, and internal process logic no longer fit together cleanly.

Good fit for

Typical use cases

The product is designed for support organizations that need clear ownership and reliable process handling.

  • IT departments and internal service desks
  • Managed service providers
  • Organizations with several specialist teams
  • Companies that want email, portal, and process handling inside one solution
Technical base

Deployment and data model

The platform is designed for controlled deployment and clean migration from existing tools.

  • Windows-capable closed system
  • SQLite or MSSQL depending on the environment
  • Optional direct HTTPS via Let’s Encrypt
  • Update and import strategy for growing environments
Helpdesk

Do you want to bring tickets, email, FAQ, and changes into one organized service platform?

We can review how well the helpdesk fits your team, responsibilities, and current tool landscape.