Support queues match individuals or teams to the topic in which they have expertise. To set up support queues, an administrator must perform the following procedures:
This topic includes the following sections:
Choose the following methods to define how self-service users are assigned to support queues:
By topics— Configure topics and queues. Make it mandatory for self-service users to select a topic from the Topics menu when they choose to chat with a live agent. From this menu, users can select a topic with which to associate their question. If the user selects a topic, the user's question is routed to the most appropriate support agent with that subject matter expertise. For example, you might define a support queue of UNIX, with three topics of HP-UX, Linux, and IBM AIX. When you assign an agent to one or more support queues, the agent sees queries in the support queue, as well as queries in the general queue. If a user does not select a topic, the query goes into the general queue. Queries in the general queue have a lower priority than queries in topic-specific queues. For example, if you assign Francie to the Hardware queue, she will see queries in the Hardware queue, followed by queries in the general queue. You do not set up general queue.
By topics and user login information — When support queues by topics are configured and we want to use values of the CTM:People form. First, the system searches for support queue related to the Topic selected by user. If the system does not find such support queue, then the system searches for support queues for topic-<something else>, such as topic-region (e.g. Hardware-EU). If such support queue is found then, the query is routed to that queue, otherwise - to the the general queue. This allows you to assign agents to support queues related to the same topic, but in different regions. For example, you can assign Francie to the Hardware-US and Bob to the Hardware-EU region. Then users from US region with Hardware-related questions will be routed to Hardware-US queue (to Francie) and users from EU region with Hardware-related questions will be routed to Hardware-EU queue (to Bob).
VIP - Create a queue named VIP. If a self-serve user is set as a VIP in BMC Remedy ITSM (on the CTM:People form), this user is automatically routed to the VIP queue. You can assign agents to the VIP queue. For example, you might assign top-performing agents to the VIP queue. If you set up a VIP queue, the VIP will be routed to the VIP queue, regardless of what topic the VIP selects. If you do not set up a VIP queue, the VIP gets routed to a queue based on the topic that the VIP selected, and the VIP is placed at the top of the queue. An agent assigned to the VIP queue also sees queries in the general queue.
The VIP queues works only when both—virtual agent and live agent are enabled. VIP queues do not work when only virtual agent is enabled.
In a multi-tenant environment, agents can have access to one or more companies and are responsible for providing support to those companies. Self-service users belong to a specific company. Agents can assist users who belong to any of the companies that the agent supports.
If you set up a support queue for a specific company, you can assign support agents who support that company.
If you set up a support queue for the Global company, you can assign any support agents to the support queue. The agent sees queries only from self-service users who belong to the company that the agent supports. Let's look at an example in which you set up a Hardware queue for the Global company. Francie supports the Calbro company, and Bob supports both Company A and Company B. Both Francie and Bob are assigned to the Hardware queue. If Joe belongs to Calbro and asks a question on a hardware topic that is assigned to the Hardware queue, only Francie would be assigned Joe's question. Because Bob does not have access to Calbro, he cannot see Joe's question.
If you set up a support queue for the Global company, you can also set up a support queue with the same name for a specific company. When a self-service user belongs to the specific company, that user's queries are routed to the queue for the specific company and not to the queue for the Global company. Let's consider an example that builds on the previous example. If you set up a Hardware queue for the Calbro company, Joe's hardware questions get routed to the Calbro Hardware queue and not to the Global Hardware queue. If Francie is assigned to the Global Hardware queue, but not to the Calbro Hardware queue, she will not see any Calbro hardware queries.
To set up VIP or VIPX queues in a multi-tenancy environment, you must set up the queues for each company that requires a VIP or VIPX queue, and you must assign support agents to each VIP or VIPX queue.
(Optional) Set a queue timeout (in minutes). If an assigned agent does not respond to the chat within the specified timeout period, the chat is released to the general support agent queue. If there is an escalation queue defined for the topic queue, then at the timeout period, the chat is released to the escalation queue. The default value is 10 minutes.
If you do not want chats to be released to the general queue, specify an exceedingly long queue timeout, such as 1,000 minutes.
Select a company from the menu.
For the VIP and the VIPX support queues, you must select a specific company. For other support queues, you can select either a specific company, or the Global company.
Restart Apache Tomcat for these changes to take effect.
Open each Authentication entry and copy the value from <
request alias> element to the Enabled Authentications.txt text file.
If there were several names delimited by semicolon then treat them as separate values and save on new line in the file.
Do not use values with the word guest, such as “remedyguest” or “itsmguest”.
From the above example, copy <request_alias>userprofilebyloginid;remedyid</request_alias>
Open the Forms-Standard configuration entry.
If an overlay is not created, click Create Overlay and open the Forms - Standard configuration entry again.
Open the Enabled Authentications.txt text file and perform the following steps:
Paste the entire xml section for
<request_alias> parameter from the entry to the overlay.
In the <
profile> element of the overlay, update the <
The following is an example of the updated code:
In the above example, the following table explains the parameters and their values:
|This parameter and value is pasted from the Authentications entry.|
[_TOPIC_] is placeholder for Topic selected by a user and 200000012 is ID of the “Region” field in the CTM:People form.
You can provide ID of any other field in the CTM:People form. For example, ID of the “Site” field is 260000001.
You can change format of the <
Save the overlay.
To ensure that each authentication type is updated with the <
supportqueue> element value, repeat the steps for each of the names saved in the Enabled Authentications.txt file.
To apply these changes, click Refresh Servlets.
The following image is an example of the Forms-Standard configuration:
You assign agents to queues, not topics. Before you can assign an agent to a support queue, the agent must login to the Support Agent Console and save his or her profile.
Click the Agent from the table.
Type the logon ID of the agent and click Save.
The agent appears in the Support Queue Agents box in the console.
topicrequired> parameter to 1, as shown in the following image:
After you enforce topic selection, self-service users receive the following message when they request to chat to a live agent: