AT&T 585-350-812 manual Data Screen Delivery Application Considerations

Page 36

ASAI Application Planning and Design

Data Screen Delivery Application Considerations

Prior to the use of data screen delivery applications, a host application typ- ically waits for input from agents before performing an operation. Thus, the agent’s input generally controls the application. With data screen delivery applications, a new input to the application is provided. While this input enables agents to work more quickly, it means that the host application must be modified. In particular, the call events provided by a monitoring script on the VIS must be used by the host to drive the screens on agent’s terminals. The interface to the VIS serves as a “control” link while the inter- face to the agent operates traditionally as an “inquiry/response” link. The interactions between these two properties of the application must be con- sidered carefully.

Suppose, for example, that a call arrives for an agent before that agent has finished entering data from the previous call. This scenario can be handled in one of two ways:

Agents can be trained to use Aux Work or After Call Work feature buttons on their phones to make themselves unavailable for calls until they have finished entering data from the previous call.

There is typically a point in the application’s sequence of operations (for example, base transaction screen) where the agent is waiting for a new call and begins interaction with the application. The appli- cation could look for information from the VIS only at this point. The agent’s phone will alert the agent to the new call, and the agent can quickly finish work on the previous call. You may wish to provide a quick way for the agent to move to this place in the interactions with the application.

In data screen delivery applications, phone extensions are used to identify agents receiving calls. The host application must therefore be able to asso- ciate extensions with particular data terminals.Three possible ways of doing this are:

The agent can be queried for the phone extension when the applica- tion is started. This is the most flexible arrangement and handles the situation where data terminals and terminal ID’s are not permanently associated with the same phone. Agents do make mistakes in pro- viding the phone extension to the system. You should plan for these occasional mistakes and make sure agents understand what must be done to properly use the system. Discuss this issue with the per- son responsible for the company’s agent operations.

If an agent is always assigned to the same work position and hence extension, the extension information could be added to an agent profile.

2-20

Image 36
Contents Conversant VIS Adjunct Switch Application Interface Blank Contents Asai Administration Asai Script Builder Actions Vi Issue 1 October Asai Overview System Monitor Voice Channels Asai Voice Response ApplicationsPage Routing Applications Asai Routing Application route.picData Screen Delivery Applications Data Screen Delivery Applications gateway.pic Page Advantages Using the VIS Asai Feature Enhanced Customer ServiceReduced Cost of Doing Business Asai Overview Asai Application Planning Design Overview Asai Application Planning DesignVIS 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 Asai Voice Response Application Considerations Routing Application ConsiderationsData Screen Delivery Application Considerations Page Communications System Planning Call Center Operations Planning Page Asai Installation Installation OverviewPrerequisites for Asai Installation Asai Hardware Architecture Typical Hardware ArchitectureInstalling Asai Hardware Base RAM Address Selection SwitchesIpci Switch Settings Installing Asai Software Conversant VISControl and ALT Removing the Asai Software Asai Administration Asai Administration OverviewVoice System Administration Feature Packages Asai Administration Screen Channel Administration Change a Channel EntryPage Page Add Channel Entry Add Channel Entry Screen achannel.psChange Channel Entry Change Channel Entry ScreenVirtual Channel Administration Remove Channel EntryPage Page Diagnose Ipci Board Diagnose Ipci Board ScreenDomain Administration Domain AdministrationPage Page Page Add Domain Entry 10. Add Domain Entry ScreenChange Domain Entry Remove Domain EntryInitialize Ipci Board Initialize Ipci BoardParameter Administration Asai ParametersPage Trace Detail Display Show Asai Software Version 14. Show Asai Software Version Screen version.psShow Status Asai Link Show Status of Asai LinkShow Status Asai Link Displays Take Ipci Board Off-line Take Ipci Board Off-lineAsai Administration Administering Asai Administering the Lines Administering the VIS ACD Split DomainPage Administering the VIS Agent Lines Page Administering Asai Asai Script Builder Actions Asai Script Builder Actions OverviewDefining ACallinfo Define ACallinfo Form Screen defacall.psPage Defining AEvent Define AEvent From Screen Page Page Page AEvent Return Field Value Meaning Return Value Explanation Connect Route Abnormal Abandon Request Route END Defining ARouteSel AEvent Fields Input/Output Required? Field Type Field SizeDefine 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 Sample Scripts OverviewSample Asai Voice Script Page Sample Routing Script Modify Table Sample Monitoring Script Page Page Asai Performance Performance Overview Voice Response Integration Data Screen Delivery