AT&T 585-350-812 manual Agent-to-Agent Transfers

Page 27

ASAI Application Planning and Design

the CONNECT event for the transferred call is received.The call ID in the Other Call ID field of the CONNECT event can be used to correlate the two calls.

The call may again be transferred after having been serviced by the live agent. In this case, an END event is not reported until all transferring is completed and the call terminates normally. As in the single transfer case, the END event contains information pertinent to the original call. Rules for how subsequent call events are reported is discussed under planning for Agent-to-Agent Transfers in this chapter.

The discussions on blind and consult transfers, discussed next under plan- ning for Agent-to-Agent Transfers, do not apply to VIS-to-agent transfers completed using the A_Tran action. Also, the delay needed for agent-to- agent transfers discussed later does not apply to VIS-to-agent transfers completed using the A_Tran action.

Transfers away from the VIS may still be accomplished by using standard flash transfer mechanisms. The use of this type of transfer, however, pre- cludes the ability to use the VIS Data field of A_Tran to save voice script data for later use in data screen delivery applications. Also, the host appli- cation must view this type of transfer as an agent-to-agent transfer as dis- cussed next. Hence, the discussions on blind versus consult transfer and the need to introduce delay for blind transfers from the VIS will apply.

Agent-to-Agent Transfers

There are two options for call transfer in an agent-to-agent transfer scenario: blind transfer and consult transfer. These two options differ as to when the screening agent (the agent transferring the call) completes the transfer to the specialized agent (the agent receiving the transferred call) by pressing the Transfer button a second time.

With a blind transfer, the screening agent presses the Transfer button a second time immediately after dialing. The screening agent does not talk to the specialized agent before completing the transfer. In addition, a delay is built into call handling so that the call is distributed to a specialized agent after the screening agent presses the Transfer button the second time.

With a consult transfer, the screening agent waits until the specialized agent answers before pressing the Transfer button a second time.This allows the screening agent to talk to the specialized agent before complet- ing the transfer.

Both of these call-transfer options are described in more detail later.To set up either a blind transfer or a consult transfer, it is important to understand two key concepts of how transferred calls are handled on the DEFINITY Generic 3i sys- tem.

2-11

Image 27
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