Reqagent (Digital Scripts)
This help page is for CXone Studio. This information is also available for Desktop Studio.
|
Requests an agent that has a specific digital skill Used to automate delivery of interactions based on agent skills, abilities, and knowledge to handle an active contact. This action is similar to the Reqagent action for other script media types, but it has some differences. Both request an agent to handle an interaction. However, CXone handles digital interactions differently from other media types. Because of this, the Reqagent (Digital) action works differently:
|
Dependencies
- Before working with digital scripts, learn more about the differences in how CXone handles digital and traditional ACD interactions.
- You must assign the script to the digital Any channel, contact, or skill associated with Digital Experience. point of contact.
- In digital scripts, the Reqagent (Digital) action routes contacts to Digital Experience. Digital Experience handles the contacts from that point, unless a workflow automation job spawns a script.
Supported Script Types
|
Digital |
The Reqagent action used with all other script media types has a separate help page.
Input Properties
All properties of this action accept variable substitution.
Property |
Description |
---|---|
|
Enter a short phrase that uniquely identifies this action in the script. The caption appears on the script canvas under the action icon. |
Skill | Select an ACD skill Used to automate delivery of interactions based on agent skills, abilities, and knowledge. If you select Default, the script uses the default skill set in the script when this action fires. If no skill is set in the script, it uses the skill assigned to the associated point of contact The entry point that an inbound contact uses to initiate an interaction, such as a phone number or email address.. You can use a variable in this property. |
Priority |
Enter the priority of contacts for this skill (0-1000). |
HighProficiency |
The highest skill proficiency an agent must have in order to receive a contact. Proficiency values are whole numbers from 1 to 20, with 1 being best and 20 being worst. |
LowProficiency |
The lowest skill proficiency an agent must have in order to receive a contact. Proficiency values are whole numbers from 1 to 20, with 1 being best and 20 being worst. |
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. |
Script Example
This is an example to show how this action can be used in scripts. It is not intended to be a complete script. Additional scripting may be required.
In this example, Begin triggers an Askcaller action, which gives the contact the option to contact sales or support. The Case action creates two custom branches, each of which connect to a digital Reqagent action. Branch 1 is configured with the skill Used to automate delivery of interactions based on agent skills, abilities, and knowledge for the Sales team and branch 2 is configured with the skill for the Support team.
The last action in this example is End. In digital scripts, the End action terminates the script, but not the contact. After the Reqagent action, the contact is passed into Digital Experience, where it stays until the end of the interaction, unless a workflow automation job calls another script.