What are Backup Search Filters?

Backup Search filters is a feature within Agent QA automations that can help with providing a consistent stream of tickets to grade for your QA graders.

This can be located right underneath the Primary Search filter.

Setting Up Backup Search Filters

Backup Search filters can only be configured for Agent QA automations. In order to enable Backup Search Filter, select any Ticket Status that is not “All”.

You will then be able to select the “Enable Backup Search” checkbox in order to create a second set of filters. The options that appear will be the exact same as the Primary Search filters.

How Do Backup Search Filters Work?

Backup Search filters will only trigger if there are not enough tickets available to be assigned after the first Primary Search filter runs. A way to visualize this can be seen in this table (for fixed number ticket distribution)

Agent

Tickets Expected

Primary Search Filter Run

Backup Search Filter Run

Bob

5

5

0

Sally

5

5

0

James

5

3

2

Mary

5

1

4

For agents Bob and Sally, they had enough tickets that matched through the Primary Search filter. However, James and Mary did not have enough tickets.

For James and Mary, the Agent QA automation assigned all possible tickets that would have matched at the time of automation run for the Primary Search filter. The automation then notes the remaining tickets needed, and runs again to assign an additional set of tickets based off of the Backup Search filter.

Understanding Automation Run Results

After an automation run, downloading the Automation Run Results can help breakdown how many tickets from the last run originate from which filters.

In the new CSV, there is a slight re-arrangement in the order of columns. Right after Agent Email, instead of seeing "Assigned Tickets", you will now see 3 columns:

  1. Expected Tickets: Total number of expected tickets assigned for the agent for the specific assignment

  2. Primary Search Assigned Tickets: Total number of tickets coming from the Primary Search filters

  3. Backup Search Assigned Tickets: Total number of tickets coming from the Backup Search filters

How does this affect the Replacing Ticket feature?

There may still be times where tickets generated by the automation are not best suited for grading and you may still need to use the "Replace Ticket" functionality to help find a new ticket.

Replace Ticket functionality will use the filters associated with the automation at time the assignment was created.

In the case where an assignment is created after an automation has Backup Search filters added, doing Replace Ticket will:

  1. Check the Primary Search filter to find a matching ticket

  2. Check the Backup Search filter to find a matching ticket

  3. If 1 and 2 are not finding any results, provide a message that says no matches are found


Why would I want to set up Backup Search Filters?

Backup Search filters can be a great way to build out a more targeted Agent QA automation without increasing effort required to find tickets for your QA team to grade.

A recommended set up would be to configure your Primary Search filter to be more granular and targeted on top of mind QA initiatives. Then, set up your Backup Search filter to help fill out additional tickets to QA on a broader level to ensure there is a consistent stream of QA feedback for your agents.


FAQ

My automation is still lacking tickets to assign even with backup search filters

This may warrant adding in another layer of backup search filters, and feel free to chat in to our support channel to help share the automation you are trying to build!

With that aside, we would recommend in this scenario to broaden your Backup Search filters or to try doing general validation that your Primary Search filters are configured correctly.

How would backup search filters work for Percentage distribution methods?

When we mention Percentage distribution, we are talking about using the "Percent" method underneath Assign Tickets > "Matching Tickets to Assign Ratio".

Using Percentage distribution, the Agent QA automation looks for x% of any number of tickets to return a number of tickets to assign. This means that as long as one ticket matches the search filters, a ticket will be assigned and the filter ran will be marked as a "success".

In the table example below, Bob and Sally each have a total of 1 and 40 tickets that match the Primary Search filters. The automation is distributing 5% of those tickets for grading. To help better highlight this, let's reference the table here:

Agent

Tickets Expected

Primary Search Filter Run

Backup Search Filter Run

Bob

5%

Success

Does not run

Sally

5%

Success

Does not run

James

5%

0% (Fail)

Backup Search Runs

Mary

5%

0% (Fail)

Backup Search runs

Understanding the Success results

Bob and Sally both had at least 1 ticket that matched the filters. These are considered a success, and the Backup Search filters will not run.

  • For Bob, 5% of 1 is 0.05 tickets, but Maestro will round up to assign 1 ticket.

  • For Sally, 5% of 40 is 2 tickets, and Maestro will assign 2 tickets for grading.

Understanding the Failures

James and Mary had 0 tickets that matched the Primary Search filter. This will mean that the Backup Search Filters will run

Did this answer your question?