Virtual Queue Requirements

To enable Virtual Queues in your instance of SupportLogic, you will need to do the following:

1. Ensure that Intelligent Case Assignment (ICA) is enabled.
2. Configure Shifts for your agent teams.
3. If you have not done so already, you should also create your Virtual Teams and Virtual Accounts as you may need these for steps 4 and 5.
4. Create the logic conditions for each queue.
5. Refine the case assignment filters and settings for each queue.

Case Assignment and Virtual Queues

Virtual Queues allows you to sub-divide the existing queues from your CRM into much more targeted routing queues for agent assignments. Combing routing logic and intelligent case assignments you can route cases from specific customers, from a specific regions, based on customer criteria and/or agent criteria automatically. 

Feature	Definition	Use Case or Example
Case Assignment	Assignment queues are comprised of individual agents, Virtual Teams or Virtual Orgs used when manually assigning a case and by the auto-assign engine. These are often named by the leader of a team or division, but are not required to be. You can make them viewable, enable them for Auto assign or not. If you do not designate any of the Queues you create for Auto-assignment, you do have the ability to define a Virtual Team or Org separately.	Case Assignment Queues impact Console, Case Assignments, Support Hub and the Keywords and Trends report. You have an additional option to set the Backlog agent card view to sort by Status or Priority.
Virtual Queues	Either CRM or SupportLogic queues can be configured with Virtual Queue rules. A Virtual Queue is comprised filters based on Case Fields or Customers (including Virtual Accounts), recommended Teams or Individual Agents, with routing logic applied.	Routing logic for a Virtual Queue is: Always will always attempt to assign an agent to unassigned cases in this Queue, even if there are no matching agents available for assignment. Never will never attempt to assign an agent to unassigned cases in this Queue. This may be used to prevent certain cases from being assigned automatically by SupportLogic under any circumstances. Optional will always attempt to assign an agent to unassigned cases in this queue. If (and only if) there are no matching agents available for assignment, assignment will proceed without this queue as a requirement. Do Nothing will ignore this Queue when assigning cases. It will be effectively disabled.

Creating a Virtual Queue

The process to create a Virtual Queue is wizard driven and can be completed in four steps..sort of*:

1. Name and describe your Virtual Queue.

2. Select the CRM Queue or Queues cases will be routed from.

3. Filter the cases based on case fields and values that you select.

4. Identify which customers are appropriate for that Queue.

Once created, determine if you want to "Auto Assign" cases to your newly created queue. You will need to configure the auto-assignment rules which is covered in  and define the settings for it. 

* Review the section below on Virtual Queue Condition Statements before you hit Save!

Building Virtual Queue Logical Statements

Some organizations have complex requirements for case routing that will need to build detailed logical statements in order to filter cases to the correct agents and/or teams.

For example, if your organization's support team is divided both by region and by language, you may need to create very specific conditions for case routing:

• Region A, Region B

• Language M, Language N

Where cases that are routed from Region A, should also have the language property of Language M and cases routed from Region B, should have the language property of Language N. 

Virtual Queue Condition Statement

The use of parentheses correctly is very important when you have complex rules for case routing. Let's look at a an example with actual case properties to see why. 

In the table below, we have listed the criteria required for cases to be routed to our Hardware and Integration Support Team that covers North America:

How you create the logical statement that combines the parameters and properties matters. In particular, the use of brackets is essential. 

However, since there could be any number of combinations of how you want to include or exclude specific parameter types and properties, the SupportLogic Virtual Queue Wizard cannot add the logical conditions for you. So, you will need to add the parentheses AFTER you have selected your CRM queues and Case fields values.

Incorrect Statement Syntax

By default, the Virtual Queue Creation Wizard will list the parameters and properties you have selected, see below:

This will create a Queue that will route all cases coming from SFDC3234 OR cases coming from SFDC2218 + Region of North America + Category of Hardware OR cases of the Category of Integrations.

This is NOT the result we want for this Virtual Queue. 

Correct Statement Syntax

Parentheses are your friend. Use the Add brackets ( ) button, then click and drag the parentheses into the appropriate location(s).

By adding in three parenthetical pairs, we can get the results that we wanted. See the statement below:

This statement tells SupportLogic to route cases from either SFDC3234 OR SFDC2218 AND the Region of North America AND for Category of Hardware OR Integrations to be assigned to the agents, or team, you wish.

Exclude Option

In addition to using proper AND / OR syntax, you also have the ability to EXCLUDE cases based on any of the parameters or properties selected. Use the drop-down icon next to and | or:

For example, if your organization has tiered support offerings and a special team dedicated to your GOLD and PLATINUM accounts, you might need exclude their cases from the Virtual Queue defined above. To do so:

1. Just add the "exclude" option.
2. Select the Account | Virtual account | Virtual group | Individual reporter needed.
3. Then Add brackets ( ) .
4. Click and drag the brackets into the appropriate location, shown below:

Congratulations! you are now a Virtual Queue aficionado!

Virtual Queue Statement Building General Guidelines

Here are a couple of quick tips that should save you a lot of frustration. When building complex Virtual Queues:

1. Start with a table and make sure you list all of the Queues and Case Property requirements.
2. In general, you should include parentheses around each parameter type. It's OK to include them even if you only have one parameter value.
3. Do not mix different parameter types within a parenthetical pair. In the example above, we would not combine ( Region: North America and Category: Hardware or Category: Integrations ).
4. Always double-check the syntax for your logical statements. Better yet, have someone else proof what you have scripted!