AT&T 585-350-812 manual Asai Voice Script Design

Page 19

ASAI Application Planning and Design

A_Tran — Used within a voice response script to transfer a call away from a T/R or LST1 channel on the VIS. This action makes use of the Third Party Call Control capability of ASAI to effect the transfer.

ASAI Voice Script Design

ASAI voice response applications are designed using the A_Callinfo and

A_Transactions within voice response scripts. Other standard Script Builder actions are also used in the voice script to answer the call, greet the caller, collect data, etc. an example of a voice script making use of the A_Callinfo and A_Tran events is included in Appendix A, “Sample Scripts.”

The A_Callinfo and A_Tran actions are used only in voice scripts which handle calls delivered to a VIS T/R or LST1 channel. These two actions are not used in routing and monitoring scripts where, in contrast to voice scripts, a call is not present at a VIS T/R or LST1 channel.

For ASAI voice response applications, incoming calls are routed to the VIS over T/ R or LST1 channels configured as an ACD split on the DEFINITY Generic 3i sys- tem. The Notification capability of ASAI is used by the VIS to monitor this split. As a call is offered to this split, the VIS receives ASAI event reports indicating the sta- tus of the call (for example call offered, queued, alerting, and connected event reports). The VIS uses the information contained in these event reports to provide the following capabilities:

DNIS Service - The Dialed Number Information Service (DNIS) information associated with the incoming call is used to select a particular Script Builder script to service the call. A unique dialed number can be provided for each unique voice response application. Each dialed number would typically be represented by a unique Vector Directory Number (VDN) on the DEFINITY Generic 3i switch. Calls to these different VDN’s can be routed to the same VIS split. The DNIS information associated with an incoming call is then used to select a particular application. An administra- tive screen on the VIS allows the different dialed numbers to be associated with a specific voice response application. This allows T/R or LST1 chan- nels to be shared across many applications. Prior to this capability, chan- nels had to be dedicated to specific Script Builder Applications.

Call Information - Once the call is answered by the VIS, the ASAI informa- tion related to the call can be retrieved for use in the voice script handling the call. In particular, the A_Callinfo action can be used to ANI, DNIS, switch collected user data (call prompting digits), call ID, and incoming trunk group ID if ANI is not available.

A user designing a voice script need not be concerned with processing the individ- ual, lower-level ASAI event reports for incoming calls to the VIS. Rather, special software is provided as part of the ASAI feature. This software processes the event reports and stores the information contained in these event reports on a

2-3

Image 19
Contents Conversant VIS Adjunct Switch Application Interface Blank Contents Asai Administration Asai Script Builder Actions Vi Issue 1 October Asai Overview Asai Voice Response Applications System Monitor Voice ChannelsPage Asai Routing Application route.pic Routing ApplicationsData Screen Delivery Applications Data Screen Delivery Applications gateway.pic Page Enhanced Customer Service Advantages Using the VIS Asai FeatureReduced Cost of Doing Business Asai Overview Asai Application Planning Design Asai Application Planning Design OverviewVIS Script Design Asai Voice Script Design Page Routing Script Design Page Monitoring Script Design Page VIS-to-Agent Transfers Page Agent-to-Agent Transfers Page Blind Transfer Page Consult Transfer Page Page Host Application Planning and Design Routing Application Considerations Asai Voice Response Application ConsiderationsData Screen Delivery Application Considerations Page Communications System Planning Call Center Operations Planning Page Installation Overview Asai InstallationPrerequisites for Asai Installation Typical Hardware Architecture Asai Hardware ArchitectureBase RAM Address Selection Switches Installing Asai HardwareIpci Switch Settings Conversant VIS Installing Asai SoftwareControl and ALT Removing the Asai Software Asai Administration Overview Asai AdministrationVoice System Administration Feature Packages Asai Administration Screen Change a Channel Entry Channel AdministrationPage Page Add Channel Entry Screen achannel.ps Add Channel EntryChange Channel Entry Screen Change Channel EntryRemove Channel Entry Virtual Channel AdministrationPage Page Diagnose Ipci Board Screen Diagnose Ipci BoardDomain Administration Domain AdministrationPage Page Page 10. Add Domain Entry Screen Add Domain EntryRemove Domain Entry Change Domain EntryInitialize Ipci Board Initialize Ipci BoardAsai Parameters Parameter AdministrationPage Trace Detail Display 14. Show Asai Software Version Screen version.ps Show Asai Software VersionShow Status of Asai Link Show Status Asai LinkShow Status Asai Link Displays Take Ipci Board Off-line Take Ipci Board Off-lineAsai Administration Administering Asai Administering the VIS ACD Split Domain Administering the LinesPage Administering the VIS Agent Lines Page Administering Asai Asai Script Builder Actions Overview Asai Script Builder ActionsDefine ACallinfo Form Screen defacall.ps Defining ACallinfoPage Defining AEvent Define AEvent From Screen Page Page Page AEvent Return Field Value Meaning Return Value Explanation Connect Route Abnormal Abandon Request Route END AEvent Fields Input/Output Required? Field Type Field Size Defining ARouteSelDefine ARouteSel Form Screen defroute.ps Page Defining ATran Deind ATran Form Screen deftran.ps Page Page ATran Fields Input/Output Required? Field Type Field Size Sample Scripts Overview Sample ScriptsSample Asai Voice Script Page Sample Routing Script Modify Table Sample Monitoring Script Page Page Asai Performance Performance Overview Data Screen Delivery Voice Response Integration