Queuewi

Queuewi is used in conjunction with a work item point of contactClosed The entry point that an inbound contact uses to initiate an interaction, such as a phone number or email address. to generate new work item contacts, typically for routing to an agent.

This action is used in monitoring scripts that query the external system for work items. Monitoring scripts are used in conjunction with work item routing scripts that actually queue up the work items for agents. Work Item Routing Scripts have the OnAnswer event that can process any needed marquee or screen popsClosed A configurable pop-up window with information about the contact. It appears on an agent's screen after a certain event, usually when the agent connects to a contact. of the data.

Dependencies

  • The work item point of contact is different from other APIs. Instead of using the GUID in CXone, it must be in the format of ID - Name, for example: 123456 - workItemPOC.
  • Before work item contacts can be generated, a work item ACD skillClosed Used to automate delivery of interactions based on agent skills, abilities, and knowledge and work item point of contact must be created in CXone and referenced at some point in the workflow.
  • Queuewi does not have payload restrictions. However, CXone has a 50 KB payload limit for handling persistent work item points of contact. It's recommended that payloads for all work item points of contact stay within this limit.

Supported Script Types

The icon for the Chat script type - a chat bubble with an ellipsis inside (...), in a diamond shape.

The icon for the Phone script type - an old-style phone handset with curved lines indicating sound coming out of it.

The icon for the Work Item script type-a piece of paper with one corner folded down and a bullet list on it.

Chat Phone Work Item

Input Properties

These properties define data that the action uses when executing.

Property

Description

Caption

Enter a short phrase that uniquely identifies this action in the script. The caption appears on the script canvas under the action icon. The default is the action name.

WorkItem ID

A user-defined unique ID for this work item.

WorkItem Payload

User-defined field for passing payload-specific information to a work item contact. If you want to pass JSON as a string in this property, you must first escape any JSON-specific characters. The API services cannot properly parse the content, therefore this field would be empty without first escaping the necessary characters. Also, this field would contain <WorkItemPayload i:nil="true"> in the trace after firing in the script if you have not escaped the necessary characters.

WorkItem Type

Defines a type for the work item.
From User-defined description of the work item origin.

newContact ID Var

Tracks the new contact ID of the work item that gets spawned.

PointOfContact

Select an existing point of contact from a drop-down. This is the point of contact that will handle this work item.

Result Branch Conditions

Result branch conditions allow you to create branches in your script to handle different outcomes when an action executes.

Condition

Description

Default

Path taken unless the script meets a condition that requires it to take one of the other branches. It is also taken if the action's other branches are not defined.

Error

Path taken when the action fails to execute properly. For example, when there is an unexpected problem such as poor connectivity, syntax errors, and so on. The _ERR variable, with a single underscore character, should be populated with a condensed explanation of the problem.