AT&T Conversant VIS Adjunct Switch 585-350-812 User Manual
2-2
ASAI Application Planning and Design
■
Routing Applications - The Routing capability of ASAI and DEFINITY
Generic 3i call vectoring is used to allow the VIS to act as a routing server.
A “routing” script on the VIS receives, processes, and responds to call rout-
ing requests sent by the DEFINITY Generic 3i system. Refer to Chapter 6,
"ASAI Script Builder Actions" for additional information on the A_Event and
A_RouteSel actions.
Generic 3i call vectoring is used to allow the VIS to act as a routing server.
A “routing” script on the VIS receives, processes, and responds to call rout-
ing requests sent by the DEFINITY Generic 3i system. Refer to Chapter 6,
"ASAI Script Builder Actions" for additional information on the A_Event and
A_RouteSel actions.
■
Data Screen Delivery Applications - The Notification capability of ASAI is
used to allow the VIS to monitor calls delivered to ACD agents. A “monitor-
ing” script on the VIS receives information concerning the status of non-T/R
or LST1 calls and passes this information to a host for use in presenting
data screens to agents receiving calls. Refer to Chapter 6, "ASAI Script
Builder Actions" for additional information on the A_Event action.
used to allow the VIS to monitor calls delivered to ACD agents. A “monitor-
ing” script on the VIS receives information concerning the status of non-T/R
or LST1 calls and passes this information to a host for use in presenting
data screens to agents receiving calls. Refer to Chapter 6, "ASAI Script
Builder Actions" for additional information on the A_Event action.
These three classes of applications can run simultaneously on a VIS. The plan-
ning and design considerations for these applications are provided later in this
chapter.
ning and design considerations for these applications are provided later in this
chapter.
The routing and data screen delivery applications are collectively referred to else-
where in this book as “data” or “data-only” applications. This is to differentiate
these types of applications from voice response applications. Similarly, the rout-
ing and monitoring scripts used to support these applications are collectively
referred to as “data” or “data-only” scripts.
where in this book as “data” or “data-only” applications. This is to differentiate
these types of applications from voice response applications. Similarly, the rout-
ing and monitoring scripts used to support these applications are collectively
referred to as “data” or “data-only” scripts.
VIS Script Design
Four additional Script Builder actions are provided with the ASAI feature and are
used to access ASAI capabilities. These actions are discussed in detail in Chap-
ter 6, "ASAI Script Builder Actions". A brief summary of these actions is provided
below for the discussions here.
used to access ASAI capabilities. These actions are discussed in detail in Chap-
ter 6, "ASAI Script Builder Actions". A brief summary of these actions is provided
below for the discussions here.
■
A_Callinfo — Used within a voice response script to retrieve ASAI informa-
tion about a call delivered to a T/R or LST1 channel (for example, calling
party number (ANI) and called party number (DNIS) for the call). This
action therefore provides access to the Notification capability of ASAI for
calls delivered to the VIS.
tion about a call delivered to a T/R or LST1 channel (for example, calling
party number (ANI) and called party number (DNIS) for the call). This
action therefore provides access to the Notification capability of ASAI for
calls delivered to the VIS.
■
A_Event — Used within routing scripts to receive information about call
routing requests sent by the DEFINITY Generic 3i system. This action is
also used in monitoring scripts to receive information about calls delivered
to an ACD agent. This action therefore serves a dual role by providing
access to both the Routing and Notification capabilities of ASAI for non-T/R
or LST1 calls.
routing requests sent by the DEFINITY Generic 3i system. This action is
also used in monitoring scripts to receive information about calls delivered
to an ACD agent. This action therefore serves a dual role by providing
access to both the Routing and Notification capabilities of ASAI for non-T/R
or LST1 calls.
■
A_RouteSel — Used within routing scripts to respond to call routing
requests previously received via the use of the A_Event action. This action
therefore provides access to the Routing capability of ASAI and allows the
VIS to send ASAI call routing information to the switch.
requests previously received via the use of the A_Event action. This action
therefore provides access to the Routing capability of ASAI and allows the
VIS to send ASAI call routing information to the switch.