AT&T 585-350-812 manual

Page 40

ASAI Application Planning and Design

must make sure that the original call is on “transfer” hold before completing the transfer. A call is said to be on transfer hold when the call was placed on hold by hitting the Transfer button. This is as opposed to “regular” hold where the call is placed on hold by hitting the Hold button.

For example, the agent may decide to return to the original caller before complet- ing the transfer (for example to say, “please wait while I transfer you to Bill who can handle your question”). When the agent returns to the original caller, the orig- inal caller is no longer on transfer hold. The agent must be sure to place the orig- inal call on transfer hold (not regular hold) before completing the transfer.

The following procedure should be followed for consult transfer situations where the screening agent wants to go back and talk to the original caller before com- pleting the transfer. In this procedure, Agent 1 is the screening agent who receives the original call from the calling customer. Agent 2 is the specialized agent who receives the transferred call. Although this procedure may seem cum- bersome initially, it is the most natural set of steps to take in consult transfer sce- narios were the screening agent wants to announce the transfer to the original caller after having talked to the specialized agent. This procedure also insures that the VIS can properly identify the original call when the two calls are merged. If agents do not follow this procedure, inaccurate call events are reported to the host application.

1.Agent 1 places the call to Agent 2 on regular hold by hitting the Hold button while the call to Agent 2 is still the active call.

2.Agent 1 returns to the original caller by pressing the call appearance for the original call. This makes the original call active once again. Agent 1 may now talk to the original caller.

3.After talking to the original caller for the second time, Agent 1 places the original caller on transfer hold again by pressing the Transfer button again. This is the second time Agent 1 has pressed the Transfer button. This causes a third, as yet unused, call appearance to become active (dial tone is heard on this call appearance but this call appearance is not used for anything - go to the next step and ignore the dial tone).

4.Make the call to Agent 2, which is currently on regular hold, the active call by pressing the call appearance for this call. At this point Agent 1 and Agent 2 are connected again and Agent 1 can inform Agent 2 that the transfer is about to be completed.

5.Agent 1 completes the transfer by hitting the Transfer button again. This is the third time Agent 1 has pressed the Transfer button.

2-24

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