Signatures

Signatures are managed for queue and email communication.

Overview

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

Typical workflow

1. Create a signature. Open the relevant administration or action form, enter the required values, and save only after checking assignments and required fields.

2. Edit a signature. Open the existing record, change only the required fields, and check dependent assignments before saving.

3. Deactivate a signature. First check which existing records or users are affected. Where possible, deactivate entries instead of deleting them permanently.

4. Assign a signature to queues. Open the existing record, change only the required fields, and check dependent assignments before saving.

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.