PDF(485.3 KB) View with Adobe Reader on a variety of devices
ePub(560.4 KB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle)(370.3 KB) View on Kindle device or Kindle app on multiple devices
Updated:July 17, 2019
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This article describes and explains the steps required to successfully collect Session Information (Session Info) from an Outbound Interactive Voice Response (IVR) call that hits the Unified Contact Center Express (UCCX) system and pass it onto the Agent desktop (Cisco Finesse) as an Enterprise Variable.
Cisco recommends that you have knowledge of these topics:
The information in this document is based on these software and hardware versions:
Cisco Finesse 10.X
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, ensure that you understand the potential impact of any command.
This information is tied to an Outbound Contact which uses the Dialing List (Customer contacts) uploaded, as shown in the image.
These are the conditions required to recreate this scenario:
Unified Contact Center Express (UCCX) 10.X onwards.
Outbound IVR campaign configured to script.
Script has a simple queue template.
Get Session Info
UCCX allows the Get Session Info step to collect details from an Outbound Contact that comes into the IVR system. (Outbound IVR - Progressive or Predictive). New variables are added to the Get Session Info step of Unified Contact Center Express (CCX) Editor for IVR-based and agent-based progressive and predictive outbound campaigns. These variables are included in the session for an outbound call that is transferred to IVR.
These are the new added variables:
BAAccountNumber - Account number of the caller. BACampaignName - Of the outbound campaign. BACallResult - Result of an outbound call.
For more information review this document on page 5:
Note: Use the Get Contact Info step to instantiate an object of type session, before you use the Get Session Info step. This is to capture the Session information and only then the values get returned in the Get Session Info step.
Step 1. Here, an IVR Outbound campaign contains Account Number,First Name,Phone Number uploaded as parameters in the Dialing List (Contact_list.txt file for the campaign).
Step 2. The IVR outbound call is made to the outside number - Phone Number from the dialing list.
Step 3. The call is then connected to the IVR script after Call Progress Analysis (CPA) by the Session Initiation Protocol (SIP) Gateway.
Step 4. Once the call hits the script, the script collects the Session Info for the call with step Get Session Info.
Step 5. This Session Info can capture these variables (including Account Info in this example) of the caller and be used for further steps in the script.
Step 6. In this case, this Session Info variable is set to a Call Variable 10 which is then the Enterprise Variable displayed onto Finesse desktop after the select resource step.
Step 1. Ensure the dialing list has the Account Number set and the correct field selected to classify this as the customer account number.
UCCX has an internal mechanism that converts this account number and sets it in a session variable call BAAccountNumber, as shown in the image.
Step 2. Define the steps in the script. The script must have an accept step, welcome prompt and collect the Session Info for Account Number. Define a Session variable called BAAccountNumber, as shown in the image.
step 3. Use Get Session Info step, with Session variable BAAccountNumber, context - BAAccountNumber and Variable AccountNumber. Set variable AccountNumber to capture this information, as shown in these images.
Step 4. Set the Enterprise call variable 10 to this variable (called AccountNumber). Call Peripheral Variable 10 in this example, as shown in the image.
Step 5 Ensure that the desktop layout has the correct display for the Account Number with this Call Peripheral Variable 10. This is done on Cisco Finesse Administration, as shown in the image.
Step 6. Put a select resource step as usual. The Agent must be able to see this info on Finesse, as shown in this image.
Configure the IVR Outbound campaign.
Upload the Dialing list with the Account number field and the Phone number and First name.
Start the campaign and point it to the script. Ensure the Agent is part of the correct Contact Service Queue (CSQ).
Keep the agent in Ready, you will see the Outbound call hit the Customer's phone.
When the customer answers the call, the call will be redirected to the script, then to the Agent and the Account number displayed correctly.
Note:Alternatively, once can use this AccountNumber variable and use a Database dip steps - DB-READ (Database Read) or DB-GET (Database get) to query an external database to check the customer's details which uses his unique Account Number collected from the Get Session Info step.