Spotter Scenario: Take Care of Tickets Pending for Too Long

Automatically apply actions on tickets that have been in the "Pending" status for a specific amount of time. With the "Take care of tickets pending for too long" Spotter Scenario, you determine the time trigger, and the resulting actions. You can add more ticket-based conditions and choose between several actions to take. 
Note:
  • By default, this Scenario is enabled in your account and set to close tickets that have been pending for 3 days.
  • When snoozing tickets, time-related triggers in Spotter do not count the duration in which tickets are snoozed. 
Roles and permissions:
To access Spotter, you must be an administrator or have a custom role with Spotter enabled in the Settings > Tools permissions. 

To activate this Scenario:

  1. Click the Spotter icon  in the side panel on the left.
  2. Click the Pre-Made Scenarios tab at the bottom to expand it.
  3. Select the Take care of tickets pending for too long Scenario.
  1. (Optional) Enter a name, up to 120 characters, for the scenario. This makes the scenario easier to find, especially when using the same pre-made scenario multiple times.
  2. Set the If condition that must be met before the Then actions are triggered:
    1. Click time period in the If condition.
    2. Enter the time period in which tickets can be in the Pending status before triggering the Then action(s). 
    3. Press Enter on your keyboard.
  3. (Optional) Click + Add a ticket based condition to add a condition that must also be met to trigger the Then action(s). Select the condition type and repeat this step if necessary: 
7.  Set the Then action(s) that will occur when the If condition is met:
8.  (Optional) Click + Add Action and select another Then action that will occur:
9.  (Optional) Click Apply to snoozed tickets to apply this Scenario to snoozed tickets
10.  Click Save & Activate.

Related Articles

Using Spotter to Automate Tasks

Use Spotter to automate the tedious tasks that need to be done when common support scenarios occur. Spotter tracks real-time events across your entire support platform, then performs specified actions. Choose f

6 min read

About Ticket Statuses

Ticket statuses help you quickly understand if tickets need replies from team members. There are 5 ticket statuses that tickets can have at a time. You can change ticket statuses manually, in bulk, or while rep

3 min read

Manually Assigning Tickets to Team Members or Groups

You can manually assign tickets to the team members or groups that should handle them. When you assign tickets, the assigned members get notifications via email and in their notifications feed. Tips: Use auto

1 min read

Working with Internal Notes on Tickets

Use internal notes to add valuable information to tickets that customers can't view. You can also notify people by mentioning team members or groups. Note:To add, edit, or remove internal notes, you must be an

3 min read

Changing Ticket Priority Levels

Change priority levels to show which tickets should be handled ahead of others. Team members can view High and Low priority indicators on tickets and ticket lists. The default priority level for new tickets in

1 min read

Spotter Scenario: Handle Tickets Following Changes in Priority

Use the "Handle tickets following changes in priority" Spotter Scenario to apply actions to tickets when their priority changes. You can add other ticket-based conditions and choose from several actions to take

9 min read