Queue Task
Understand how to configure Queue Task in Cisco Webex Contact Center
This node calls Webex CC Queue Task API to queue the contact at Webex CC. While configuring flows in Webex Connect, you’d need to use this node for queuing the contact on Webex CC. Flow developer can configure the Skill based routing setting by selecting the appropriate skills and values on the node.
Authorization
Refer to section Node Authorizations for more information.
Methods and Outcomes
Here is a brief description of various methods, and corresponding output variables and node outcomes associated with each of the methods.
Method Name - Queue Task
Please note that the Skill Settings section visible in the screenshot above will be available only when a queue with skill-based routing is selected in 'Queue Name' dropdown.
| Method Name | Output Variables | Node Outcomes |
|---|---|---|
| Queue Task | taskId agentId | onInvalidData onError onInvalidChoice onauthorizatonfail Error taskFailed Queued onTimeout |
| Channel | Field Value |
|---|---|
| SMS, Facebook Messenger, WhatsApp, Live Chat, Email, and, Apple Messages for Business. | TASK ID - $(flid) CONVERSATION ID - $(conversationId) MEDIA TYPE MEDIA CHANNEL QUEUE NAME |
| Input Variables | Output Variables | Versions |
|---|---|---|
| TASK ID - $(flid) Flow transaction Id from the start node is converted into UUID in the evaluate node and passed to create task node for creating task with flid as task Id. CONVERSATION ID - $(conversationId) Conversation Id from the create conversation node. MEDIA TYPE - This field specifies the type of media on Webex CC while making task API call. Media Type can be selected from the dropdown: For SMS, Facebook Messenger, WhatsApp, and, Apple Messages for Business the media type is “Social”. For Email, media type is “Email”. For Live Chat/ In-App Messaging, media type is “Chat”. MEDIA CHANNEL - This field specifies the channel on Webex CC while making task API call. Facebook Messenger, SMS, Email, WhatsApp, Apple Messages for Business, and Live Chat/ In-App Messaging can be selected from the dropdown. QUEUE DETAILS - Choose a queue type, static or dynamic. STATIC QUEUE - Select a queue to which the contact must be queued: Longest Available Agent and Skill Based Routing. New queues can be added from WxCC admin. If you select Skill Based Routing, you must configure Skill settings and provide values for Skill, Skill Condition, and Skill Value. You can add multiple skills or add a Skill relaxation rule. The default timeout for the skill relaxation rule is 60. You may also add Skill, Skill Condition, and Skill Values if you added Skill relaxation is added. DYNAMIC QUEUE - Enter the Queue ID to which contact must be queued. CONTACT PRIORITY - Contact Priority allows contacts to be prioritized over other contacts in the queue. CONTACT PRIORITY - Contact Priority allows contacts to be prioritized over other contacts in the queue. Select a priority between numbers 1-9. The default priority for the field is 10. We can pass a number between 1-9, where 1 denotes the highest priority, and 9 denotes the lowest priority. Note: v1.3 is recommended because the version is upgraded to address any issues related to skill relaxation configuration. | taskId agentId | TASK ID, CONVERSATION ID, MEDIA TYPE, MEDIA CHANNEL, QUEUE NAME are available with v1.0, v1.1, v1.2, and v1.3. |
Note
When the variable is selected from the previous node output variables, the node Id will be the prefix for the variable. For example, if sms.serviceNumber is an output variable of start node (node Id 2), then the variable becomes $(n2.sms.serviceNumber).
Updated 6 days ago