Ticket Resolved Processing
Talos is being set up to ensure a level of consistency and accuracy when tickets are being completed. Each IT Support provider is different in their procedures but this process of sending a resolved ticket to Talos will allow for multiple things. For now, the primary use of this is to confirm that the Ticket Resolution field has appropriate details in it. For example, can’t be blank and can’t exceed your Maximum Resolution Characters setting.
Create the Workflow Rule for Resolved Ticket
Whenever a new ticket has been idle for too long Talos will notify your selected Teams channel again about the inactive ticket.
- Login to Autotask and go to Admin -> Workflow Rules
- Ensure you are on the Service Desk tab and click the New button
- Give the Workflow a recognisable name. We recommend that any workflow that is interacting with a TRIBU product starts with TRIBU.
- Fill out the description with something meaningful for quick reference
- Tick on the ‘Edit by’ option and set to “Anyone”
- Scroll down to Conditions and set the first condition to ‘Status’ -> equal to -> your company resolved status
- In the example below, we exclude the Monitoring Alert’s Queue for resolution analysis.
- Then down to Updates and set “UDF: TRIBU” to “Resolved”
UDF Setup instructions here
- Then go to Actions and set the ‘Then Execute Extension Callout’ and set it to your “TRIBU Callouts” callout.
Callout setup instructions are here
- You can add in any other conditions and actions to take that follow your standard business procedures as well, however, there can only be one Extension Callout that must be set to go to Talos.
- Ticket SLA overdue configuration
- New ticket
- New ticket IDLE configuration
- Customer replied configuration
Go to using Talos