Ticketing

Purpose of the Ticketing

This feature allows code users to report service requests. Relevant information, such as the location and contact details, is requested through a process defined by you to simplify problem analysis and problem solution. This reduces waiting times, queries and ambiguities.

Ticketing settings

Standard questions in Ticket Creation Flow

In the settings you can specify which standard questions can be asked to the code user when creating a ticket.

The following standard questions can be selected:

ticketing
  1. Due Date: Code users can specify when the service request should be resolved.
  2. Location: Code users are asked to indicate the location of the problem.
  3. Media Upload: To simplify problem analysis, code users can upload photos and videos of their problems.
  4. Ticket Reporter: Code users can leave their names.
  5. Notifications: Code users can specify whether and how they would like to be informed about status changes to their ticket.

Note: If a standard question is not checked, it will neither appear in the standard nor in the self-defined Ticket Creation Flows.

Edit settings

  1. Select TEMPLATES from the side menu.
  2. Select a template that you want to edit.
  3. Select the Modules tab.
  4. Select Ticketing from the side menu.
  5. Now you can activate or deactivate standard questions.
Ticketing

Edit Submodules

Submodules are used to customize the ticketing process.

  1. Select TEMPLATES from the side menu.
  2. Select a template that you want to edit.
  3. Select the Modules tab.
  4. Select Ticketing from the side menu.
  5. Use the toggle buttons to turn Ticketing Submodules on and off.
Ticketing submodules EN

Learn more about the submodules under the following links:

Was this article helpful?
YesNo

Leave a Reply

Your email address will not be published. Required fields are marked *

1 + one =