Managing Sessions in Your Scripts
A session provides script designers with an easy way to associate information with a customer (caller) as the call moves through the system (similar to an in-memory database or a shopping cart on the web).
The script automatically associates a call contact with a session object when the contact is received (inbound) or initiated (outbound). You can also create sessions manually, using the Get Session step of the Session palette; this feature may be useful when you want to use sessions for HTTP or e-mail contacts.
Customer information stored in a session object can persist for a specified length of time after the contact ends and be made available to a subsequent contact. This feature can save customers the need to re-enter information such as credit card account digits.
You can store any type of information in these session objects, and retrieve the information with the Set Session Info and Get Session Info steps of the Session palette.
Note | A session is maintained on a single Cisco Unified CCX server only; for example, information entered on Cisco Unified CCX Server #1 will not be available if the call arrives at or is transferred to Cisco Unified CCX Server #2. |