Completely pre-configured state-workflows directly from the project experiences after installing workflows

Even if the complexity and amount of processes is very differently in the projects we finished, there are still some ways of ticket processing which are common for all service organisations. We summarized the best practice examples into optimal workflow configuration for every organisation. The customer-specific process design can be added on top, however, the basic flow will be kept as standard.

  • Completely pre-configured state-workflows directly from the project experiences after installing workflows: workflows for Incident / Incident Disaster, Problem, Service Request, Information Request, Standard-RfC.
  • After module installation, your service agents have the workflows directly in the system.

This additional module is charged and available for KIX Professional users.

Common Use Case

  • An ITSM system should be implemented including processing for some ticket types. However, there is no definition of processes yet and the service agents should start working quickly with the system.
  • An existing service system should be extended. The current processing should be improved and unified - among all for the better report and easier introduction into the system for the new service agents.