Skip to content

Configure helpdesk

The business portal has an integrated ticket system (help desk) with which you can record and process support requests from your customers in a structured manner. In the Helpdesk configuration area (under Communication management) you define the framework conditions and structure of this system.

You need this menu in particular if you want to give your customers the opportunity to send support requests directly to you in the self-care / customer portal. The structures created here ensure that tickets are recorded in a structured manner and are sorted and prioritized and assigned to the responsible people or groups.

In the left menu, navigate to Communication Management > Helpdesk Configuration.

First things first: At the top of the page you will find the Activate helpdesk for self-care / customer portal switch.

  • Activated (green): Customers see a support function in the self-care / customer portal and can create tickets.
  • Disabled (gray): The ticket system is invisible to the customer. Use this if you want to temporarily pause support or only handle it via external channels (such as a classic support email address).

2. The building blocks of the helpdesk (tab)

Section titled “2. The building blocks of the helpdesk (tab)”

The menu is divided into six tabs to reflect the structure of your support processes:

  1. Categories: Here you define the broad subject areas that the customer can choose from when creating a ticket (e.g. “billing”, “contract” or “login problems”). This means that concerns are roughly structured when they are created.
  2. Priorities: Define the priority levels (e.g. “High”, “Medium”, “Low”). When creating a new priority, in addition to the name, you also assign a numerical value (field: Priority), which is later used for sorting and weighting the tickets in the system.
  3. Tags: Tags are keywords (e.g. “User Account” or “Billing”). They help support teams to classify tickets more precisely internally and later filter them specifically in evaluations.
  4. User groups: This is where you represent your internal support teams (e.g. “1st Level Support”). When you add a group, you can use the Add User dropdown to select and group individual users registered in the business portal.
  5. Assignment rules: Here you define “if-then rules” (ticket routing). You can specify: If a ticket has a certain category, day, priority or status, then automatically assign it to a specific person (or group) who is working on it. You also assign a “routing priority” if rules overlap.
  6. Templates: Here you can create pre-structured ticket templates. These templates can be created for a specific target group, for example internal or customer. You can already specify categories, priorities, tags and a formatted description text (e.g. “Description of the incident including expected solution”). This saves both customers and employees an enormous amount of recording effort for standard problems.
    • Force due date: An important function of the templates is the setting of a fixed processing time. If you define this period in the template, the system automatically calculates a due date (creation date + defined period) for each newly created ticket - regardless of whether a different date (or no date at all) was actually requested when the ticket was created.
  • Forgotten switch: Common error. The helpdesk has been fully configured internally in all tabs, but the Activate helpdesk for self-care / customer portal switch is still off. The customer searches the portal for help in vain.
  • Too many categories: If you create 30 different options in the “Categories” tab, this can overwhelm customers when creating tickets. Limit yourself to a few, very clear categories and instead use internal “tags” for fine sorting.

With this configuration you create a structured basis for your customer support. Tickets are recorded in a structured manner and can be processed efficiently.

tebio is developed “API-first”. This means that not only the operational use of the helpdesk, but also the configuration via the API can be controlled. This is particularly valuable if you want to roll out helpdesk structures across different tenants via scripts.

Almost every tab in the user interface has corresponding endpoints in the Settings API:

To connect external systems or your own portals, use the operational endpoints: