Spotter Scenario: Ticket Volume Alert for Companies

Use the "Ticket volume alert for companies" Spotter Scenario to send notifications when you have a certain amount of tickets in a specific status from the same company. You can add other conditions the tickets must also meet to trigger notifications. 
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 Ticket volume alert for companies 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 number in the If condition.
    2. Enter the maximum number of tickets you can have in the selected status from the same company before the Then action is triggered. 
    3. Press Enter on your keyboard or click the checkmark .
    4. Click status in the If condition.
    5. Select the ticket status to use for the Scenario. When there are more than the entered number of tickets in this status from the same company, the Then action is triggered. 
  1. (Optional) Click + Add a ticket based condition to add a condition that must also be met to trigger the Then action: 
7.  Set the Then action that will occur when the If conditions are met:
8.  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

Spotter Scenario: Open Tickets Volume Alert

Use the "Open tickets volume alert" Spotter Scenario to send notifications when you have a certain amount of Open tickets within a selected time period. You can add other conditions the tickets must also meet t

9 min read

Spotter Scenario: Reduce Delays in Ticket Handling

Use the "Reduce delays in ticket handling" Spotter Scenario to apply actions when a ticket has been in the "Investigating" status for too long. You set the duration in which tickets can be in this status before

10 min read

Spotter Scenario: Escalate Tickets That Might Be Stuck

Automatically apply actions to assigned tickets that have been in the same status without activity for too long. With the "Escalate tickets that might be stuck" Spotter Scenario, you decide the status and durat

10 min read

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

10 min read

Spotter Scenario: Spot and Handle Unanswered Tickets

Use the "Spot and handle unanswered tickets" Spotter Scenario to apply actions on tickets that have not received a reply in a certain amount of time. Choose who's replies count towards answering tickets and the

11 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