AT&T 585-350-812 manual Blind Transfer

Page 29

ASAI Application Planning and Design

With a consult transfer, the merge takes place after the second call is delivered to the second, specialized agent. In this case, the original call is still on hold at the first agent’s phone when the second call is delivered to the second agent. Hence, for consult transfers, the VIS can only provide information related to the second call in the CONNECT event for the second call. In particular, the call ID of the original call is not reported in the Other Call ID field of the CONNECT event for the second call. The host application must use a mechanism other than call ID’s to associate the original call with the second call. The alternate mechanism is the Calling Party Number information as discussed later.

Blind Transfer

With a blind transfer, the screening agent does not talk to the specialized agent before completing the transfer. With this type of transfer, the VIS retains the call ID of the original call and reports it in the Other Call ID field of call events for the transferred call. Also, other ASAI information such as ANI and DNIS related to the original call is reported in the call events for the transferred call. A typical call flow for blind transfers is described below. In this call flow, Agent 1 is a live agent in a screening split who transfers calls to specialized agents. Agent 2 is a specialized agent that can receive calls via a monitored VDN or ACD split or can be a regular extension. Calls to Agent 1 in the screening split must be delivered via a moni- tored VDN or ACD split.

1.A call arrives for Agent 1.

2.Agent 1 answers the call and enters pertinent information about the calling customer.

3.Agent 1 transfers the call to Agent 2. This is done by pressing the transfer button, dialing the VDN, split, or individual extension and pressing the transfer button again.

4.Agent 1 is finished with the call.

5.The host application uses call ID information reported in CONNECT events to determine which data to display on Agent 2’s data-terminal screen. The call ID from the Call ID field of the CONNECT event for the original call matches the call ID provided in the Other Call ID field of the CONNECT event for the transferred call.

Two CONNECT events are passed to monitoring scripts for the entire scenario, that is, one for the original call to the screening agent and one for the transfer to the specialized agent. One END event is generated when the call eventually ter- minates. Refer to Appendix B, “Call Flow Examples” for detailed call flow exam- ples which include complete descriptions of call flows and call event contents.

The persons responsible for administration and application development must thoroughly understand the call flow described previously. In addition, note the fol- lowing:

2-13

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