Customers¶

Administrators manage customer master data and customer-specific dynamic fields.

Overview¶

This page explains how to use Customers and describes its main effects. Test changes in a test environment first whenever they may affect existing tickets, permissions, notifications, or automations.

Typical workflow¶

Create and edit a customer. Open the relevant administration or action form, enter the required values, and save only after checking assignments and required fields.
Deactivate a customer. First check which existing records or users are affected. Where possible, deactivate entries instead of deleting them permanently.
Create, edit, and delete dynamic customer fields. Open the relevant administration or action form, enter the required values, and save only after checking assignments and required fields.

Notes¶

Visible menu items and actions depend on the signed-in agent’s group and program permissions.
Deactivated entries are often retained for existing tickets and reports, but are no longer available for new assignments.
After making changes, test at least one realistic use case with a user in the affected role.