This article is a tutorial on how to automatically set tickets to solved, if you do not hear back from the user after a few days. It is possible to automate the process of solving tickets with automations.
Note: If you use the messaging channel to communicate with your users, you can also configure notifications and solve tickets automatically through messaging inactivity reminders instead of using this automation workflow.
The workflow includes the steps below.
Step 1: Create an automation
- Create a new automation
-
Under Meet all of the following conditions, add the below conditions:
-
Ticket: Status category | Is
| Pending
Only the tickets marked as pending are checked by the automation - Ticket: Hours since update | Greater than | 48
-
Ticket: Hours since status category pending
| Greater than | 48
The Hours since update condition starts counting from the last update in the ticket. The Hours since status category pending condition targets tickets in a default or custom pending status that are in this state for more than two days. -
Ticket: Tags |
Contains none of the following |
ticket_solver
The Ticket: Tags condition guarantees that the automation runs only once in a ticket and it won't be updated again by the same automation
You can add tags, set users and groups, or target specific tickets to optimize your conditions
-
Ticket: Status category | Is
| Pending
-
Under Perform these actions, add the actions below:
-
Ticket: Add tags |
ticket_solver
-
Notifications: User email |
(requester and CCs) | Add your custom email subject and body. This action notifies your users of the ticket closure.
- Ticket: Status category | Solved
-
Ticket: Add tags |
-
Click Create automation
Step 2: Create a view to ensure tickets are being solved
- Create a ticket view
-
Under Tickets must meet all of these conditions to appear in the view, add the below:
-
Tags | Contains at least one of the following |
ticket_solver
- Status category | Is not | New
-
Tags | Contains at least one of the following |
-
Click Save
The view displays tickets that are tagged with
ticket_solver
. The purpose of the tag is to track the tickets that are solved by the automation in a view.
Note: In accounts with custom ticket statuses deactivated, use the Ticket: Status and Ticket: Hours since pending categories for the automation, and Status for the view condition.
For more details about automations, see the article: About automations and how they work.