Automation for Tasks, Expenses, and Tickets
Periodic operations can create Tasks, execute Expenses actions, and close old Tickets items based on a set timeframe.
Last updated 13 days ago
Tasks and Expenses automated operations
Automated operations can create recurring Tasks and execute scheduled Expenses actions.
Tasks reminders and recurrence
Individually configure how many hours in advance responsible parties (Staff) should be reminded about critical, start, and end dates. A specific Task type may have its own interval, which then applies instead of the general one.
Create recurring Tasks items X days in advance determines how far ahead the system prepares copies. A higher number allows the schedule to be viewed earlier but creates more records at once. Check the recurrence frequency, end date, and the responsible parties being copied.
Expenses automated operations
Time of day specifies the hour (0 to 23) when Expenses automated operations are executed. Reminder about Expenses Payment date determines how many days in advance responsible parties (Staff) are notified.
The notification channel depends on team member notification settings. Select a time when system load is lower and verify that the responsible parties receive the system notification or email.
Automatic closure of Tickets
Under specified conditions, old Tickets items may be closed automatically; therefore, it is important to select an appropriate timeframe.
Automatic closure of Tickets
Specify the number of hours of inactivity after which Ticket should be closed automatically. If the value is 0, automatic closure is disabled.
The time is calculated from the last response, or—if there are no responses—from the creation of Tickets. Upon closure, the status is updated, and an email is sent to the recipient. Before enabling this feature, align the interval with your service process and review the automatic closure email template.
Related articles
Was this helpful?
Still need help? Ask the team