Documentation forTechnician
Support

Service Desk Automation

moduleservice-desk typetask Updated 6 Nov 2026

Introduction

Several automated features in AMG manage ticket creation, assignment, updates, reminders and escalations throughout the ticket lifecycle. These features are configured by the system administrator to ensure that tickets are processed consistently and reach the appropriate technicians or teams.

As a technician, understanding these automated processes helps you identify why a ticket has been created, why it has been assigned to you, when notifications are triggered and how the system handles tickets that remain unresolved.

Table 2.11.1: Automation that affects your tickets

Feature What it does for you
Email to Ticket AMG can automatically convert incoming emails sent to configured support mailboxes into service tickets. The email subject is generally used as the ticket subject, while the email content becomes the ticket description. This allows users to report issues through email without accessing the application. Such tickets are automatically created with Created Via set to Mail. Once created, they follow the normal ticket assignment and management workflow.
Ticket Scheduler The Ticket Scheduler automatically creates tickets based on predefined schedules configured by the administrator. Tickets can be generated on a daily, weekly, monthly or yearly basis. For example, an administrator can configure a daily backup verification task or a monthly preventive maintenance activity. Once generated, these tickets appear in the regular ticket listings and can be assigned to technicians for action.
Auto Allocation Auto Allocation automatically assigns newly created tickets to technicians belonging to a configured allocation group. The system considers the technician's configured ticket allocation limit while distributing tickets. This helps distribute incoming tickets among available technicians and reduces the need for manual assignment. Depending on the allocation configuration, tickets are assigned according to the defined allocation mechanism.
Ticket Trigger Ticket Triggers automatically execute predefined actions when a ticket meets specific conditions configured by the administrator. These conditions may be based on ticket properties such as category, priority, status or other configured parameters. Depending on the trigger configuration, actions can include assigning a handler, changing ticket priority, initiating an escalation process or deleting tickets identified as spam.
SLA Reminders SLA Reminders notify users and technicians about approaching SLA deadlines. These reminders help ensure that tickets receive attention before the defined response or resolution time expires. Depending on the configuration, reminders can be delivered through normal email notifications or the Buzzer notification type, which uses an alert sound.
Escalation Escalation automatically forwards or highlights tickets to a configured escalation user or group when the ticket reaches its predefined escalation trigger time. This helps bring delayed or unattended tickets to the attention of the appropriate authority. Escalation rules are configured by the administrator and may depend on the ticket's SLA or escalation settings.
Auto close and archive AMG automatically manages the closure and archival of tickets based on configured time intervals. Resolved tickets are automatically closed after three days. Closed tickets are subsequently archived after the number of days specified in the system configuration. This helps maintain active ticket listings while retaining historical ticket records for future reference.

Important notes

  • Automated actions are controlled by administrator-defined configurations. The exact behaviour may vary depending on the rules enabled for your organization.

  • Auto-assignment does not necessarily mean that a ticket has been resolved. The assigned technician remains responsible for reviewing and processing the ticket.

  • SLA reminders and escalations help technicians monitor deadlines and take timely action.

  • Automatically generated or assigned tickets should be reviewed and handled through the standard ticket management workflow.