Avaya Interaction Center Release Media Workflow Reference

Transcription

1 Avaya Interaction Center Release Media Workflow Reference Issue 3.0 July 2004

2 2004 Avaya Inc. All Rights Reserved. Notice While reasonable efforts were made to ensure that the information in this document was complete and accurate at the time of printing, Avaya Inc. can assume no liability for any errors. Changes and corrections to the information in this document may be incorporated in future releases. Preventing toll fraud "Toll fraud" is the unauthorized use of your telecommunications system by an unauthorized party (for example, anyone who is not a corporate employee, agent, subcontractor, or person working on your company's behalf). Be aware that there may be a risk of toll fraud associated with your system and that, if toll fraud occurs, it can result in substantial additional charges for your telecommunications services. Avaya fraud intervention If you suspect that you are being victimized by toll fraud and you need technical assistance or support, call Technical Service Center Toll Fraud Intervention Hotline at for the United States and Canada. For additional support telephone numbers, see the Avaya Web site: Select Support, then select Escalation Lists. This Web site includes telephone numbers for escalation within the United States. For escalation telephone numbers outside the United States, select Global Escalation List. Providing telecommunications security Telecommunications security (of voice, data, and video communications) is the prevention of any type of intrusion to (that is, either unauthorized or malicious access to or use of) your company's telecommunications equipment by some party. Your company's "telecommunications equipment" includes both this Avaya product and any other voice/data/video equipment that could be accessed via this Avaya product (that is, "networked equipment"). An "outside party" is anyone who is not a corporate employee, agent, subcontractor, or person working on your company's behalf. Whereas, a "malicious party" is anyone (including someone who may be otherwise authorized) who accesses your telecommunications equipment with either malicious or mischievous intent. Such intrusions may be either to/through synchronous (time-multiplexed and/or circuit-based) or asynchronous (character-, message-, or packet-based) equipment or interfaces for reasons of: Use (of capabilities special to the accessed equipment) Theft (such as, of intellectual property, financial assets, or toll-facility access) Eavesdropping (privacy invasions to humans) Mischief (troubling, but apparently innocuous, tampering) Harm (such as harmful tampering, data loss or alteration, regardless of motive or intent) Be aware that there may be a risk of unauthorized intrusions associated with your system and/or its networked equipment. Also realize that, if such an intrusion should occur, it could result in a variety of losses to your company (including, but not limited to, human and data privacy, intellectual property, material assets, financial resources, labor costs, and legal costs). Link disclaimer Avaya Inc. is not responsible for the contents or reliability of any linked Web sites and does not necessarily endorse the products, services, or information described or offered within them. We cannot guarantee that these links will work all of the time and we have no control over the availability of the linked pages. Trademarks Avaya is a trademark of Avaya Inc. All trademarks identified by the or are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners. Ordering information: Avaya Publications Center Voice: (Toll-free, U.S. and Canada only) Fax: (Toll-free, U.S. and Canada only) Write: Globalware Solutions 200 Ward Hill Avenue Haverhill, MA USA Attention: Avaya Account Manager Web: totalware@gwsmail.com Order: Document No , Issue 3.0 July 2004 Avaya support Avaya provides a telephone number for you to use to report problems or to ask questions about your contact center. The support telephone number is in the United States. For additional support telephone numbers, see the Avaya Web site: Select Support, then select Escalation Lists. This Web site includes telephone numbers for escalation within the United States. For escalation telephone numbers outside the United States, select Global Escalation List. Comments To comment on this document, send to crminfodev@avaya.com. Acknowledgment This document was written by the CRM Information Development group. Your responsibility for your company's telecommunications security The final responsibility for securing both this system and its networked equipment rests with you, an Avaya customer's system administrator, your telecommunications peers, and your managers. Base the fulfillment of your responsibility on acquired knowledge and resources from a variety of sources, including, but not limited to: Installation documents System administration documents Security documents Hardware-/software-based security tools Shared information between you and your peers Telecommunications security experts To prevent intrusions to your telecommunications equipment, you and your peers should carefully program and configure: Your Avaya-provided telecommunications systems and their interfaces Your Avaya-provided software applications, as well as their underlying hardware/software platforms and interfaces Any other equipment networked to your Avaya products. Warranty Avaya Inc. provides a limited warranty on this product. Refer to your sales agreement to establish the terms of the limited warranty. In addition, Avaya s standard warranty language, as well as information regarding support for this product, while under warranty, is available through the following Web site:

3 Avaya Interaction Center Release Media Workflow Reference Contents Before you begin Typographical conventions Notes, tips, and cautions Contacting Technical Support Product documentation Readme file Electronic documentation Printed documentation License to print the electronic documentation Educational services Chapter 1: Introduction Types of media workflows Required knowledge How to invoke a media workflow System workflows Sample media workflows Location of project folders Sample contact routing flows Sample Analysis flows Sample Blender flows Business Advocate flows Related documentation Chapter 2: Routing hints Routing hints and queues RoutingHint table Routing hints and addresses Example: routing hint for Types of contact qualification and routing Standard contact qualification and routing Business Advocate qualification and routing Routing hints for voice contacts Routing hints in the Incoming Call flow Routing hints in the Qualify Voice flow for Business Advocate Routing hints for chat contacts Issue 3.0 July

4 Contents Routing hints in the Qualify Chat flow Routing hints in the Qualify Chat flow for Business Advocate Routing hints for contacts analysis flows that identify routing hints Routing hints identified by analysis flows Routing hints in the Qualify flow Routing hints in the Qualify flow for Business Advocate Chapter 3: Standard blocks ADU palette Fetch ADU Get ADU Values Advocate palette Fetch LRMID Map to Qualifier Post Qualification Set Qualifier Set Voice Wait Treatment Translate Category/Qualifier Application palette Create Record Fetch Customer Record Get Record Value(s) Table Clear Table Search Content Analysis palette Get Language Get Matched Category QA Outbound (QA Category) Test Category EDU palette Create EDU Delete EDU Data Fetch EDU Get EDU Values Set EDU Test EDU Data Write EDU palette Add Component Auto Response Bounce Dismiss Get Agent Quota Get Suggested Response IC Analyzed IC Outbound Response Media Workflow Reference

5 Contents Route Set Alert Smart Auto Ack General palette Comment Config Parameter Demo Get Input Parameters Initialize Global On Exit Raise Alarm Set Output Parameters Set Default Values Start Stop Test Data Routing palette Add Routing Hints Complete Qualification Create Agent Desktop Data Fetch Routing Hints Map Hints to Queue Set Chat Wait Treatment Set Route Parameters Set Routing Hint Telephony palette Hangup Call Transfer Call Tools palette Build SeqCouple Build SeqString Build String Copy SeqCouple Find Value in SeqCouple Format String Keyword Search Keyword Search Parse SeqCouple Parse SeqSeqCouple Chapter 4: Voice contact routing flows Telephony in Avaya IC Routing process for voice contacts Incomingcall events Prerequisites for the Incoming Call flow Customization of the Incoming Call flow Modifying block properties Adding blocks Issue 3.0 July

6 Contents Incoming Call flow Input parameters and EDU values Contact information Routing hints Transfer voice contact Stop flow Chapter 5: Chat contact routing flows Prerequisites for the Qualify Chat flow Customization of the Qualify Chat flow Modifying block properties Adding blocks Using localizable on-hold treatments Qualify Chat flow EDU values and input parameters Customer lookup Customer preferences Routing hints Route parameters and wait treatments Complete chat qualification Stop flow Chapter 6: Voice chat contact routing flows IV Chat flow Incoming IV Chat flow Chapter 7: contact routing flows Prerequisites for the Qualify flow Customization of the Qualify flow Qualify flow EDU values and input parameters Customer lookup Agent desktop data Preferred agent Routing hints qualification Stop Flow Chapter 8: Analysis flows Types of Analysis flows analysis with keywords analysis with Content Analyzer Purpose of Analysis flows Customization of Analysis flows Adding routing hints Modifying block properties Media Workflow Reference

7 Contents Adding blocks Detecting loops Process of Analysis flows Analyze with Keywords flow EDU values and input parameters type analysis Routing hints Suggest responses Route disposition analyzed Stop flow Outbound with Keywords flow EDU values and input parameters type Set alert components Approval by supervisor Outbound response Stop flow Analyze with Content Analyzer flow EDU values and input parameters type Test for Website analysis with Content Analyzer Test category Routing hints Suggested response Route disposition analyzed Stop flow Outbound with Content Analyzer flow EDU values and input parameters type Set alert component Approval category Approval by supervisor Routing hints outbound response Stop flow Chapter 9: Blender Flows Blender flows in Avaya IC Setting task loads with Blender flows Initialization flow Client Login flow ADU values in the Client Login flow Issue 3.0 July

8 Contents Example: adding agent attribute to ADU Steps in sample Client Login flow State flow Input parameters ADU values Agent state Inittransition state Available state Stop flow Blender system flows Client Logout flow Channel State flow Channel Server Failure flow Chapter 10: Business Advocate flows Qualification workflows in Business Advocate Data used for qualification Prequalification steps Required qualifiers Qualify Voice flow for Business Advocate Input parameters and EDU values Contact information Qualifiers Post qualification Stop flow Qualify Chat flow for Business Advocate Input parameters and EDU values Contact information Qualifiers Post qualification Stop flow Qualify flow for Business Advocate Input parameters and EDU values Contact information Channel qualifier Preferred agent Routing hints Qualifiers for approval Qualifiers for contact Post qualification Stop flow Chapter 11: Advanced concepts Creating an EDU Dictionary Importing an EDU Dictionary Exporting an EDU Dictionary Using properties and symbols Media Workflow Reference

9 Contents Project Symbol Dictionary Variable symbols Constant symbols Global variables Auto-defined symbols Using library files Reviewing a sample library file Library file naming conventions Creating a library file Working with semaphores About semaphores Semaphores and threads Syntax of a semaphore Optional flags available for use in a semaphore Defining semaphores Using semaphores Troubleshooting the misuse of semaphores Examples of semaphores Example: semaphore in the sample Voice Chat workflow Example: Using a simple semaphore Example: Using a complex semaphore Example: using different threads to acquire and release semaphores Example: using semaphores with Block Acquire Chapter 12: Test and debug workflows Debugging Contact Routing and Blender flows Recommended debugging levels Print statements Project debug logging codes Workflow debug property Block debug property Working with debug properties Monitoring workflow performance Index Issue 3.0 July

10 Contents 10 Media Workflow Reference

11 Typographical conventions Before you begin This section includes the following topics: Typographical conventions on page 11. Notes, tips, and cautions on page 12. Contacting Technical Support on page 12. Product documentation on page 13. Educational services on page 15. Typographical conventions This guide uses the following font conventions: Font Type command commandvariable italics link Meaning This font signifies commands, information that you enter into the computer, or information contained in a file on your computer. This font indicates variables in a command string. This font is used to add emphasis to important words and for references to other chapter names and manual titles. Blue underlined text in online documents indicates a hypertext jump to related information. To view the related material, click the blue underlined text. Issue 3.0 July

12 Before you begin Notes, tips, and cautions Note: Important: Tip: CAUTION: Note: A note calls attention to important information.! Important: An important note calls attention to a situation that has the potential to cause serious inconvenience or other similar repercussions. Tip: A tip offers additional how-to advice.! CAUTION: A caution points out actions that may lead to data loss or other serious problems. Contacting Technical Support If you are having trouble using Avaya software, you should: 1. Retry the action. Carefully follow the instructions in written or online documentation. 2. Check the documentation that came with your hardware for maintenance or hardware-related issues. 3. Note the sequence of events that led to the problem and the exact messages displayed. Have the Avaya documentation available. 4. If you continue to have a problem, contact Avaya Technical Support by: Logging in to the Avaya Technical Support Web site Calling or faxing one of the following numbers from 8:30 a.m. to 8:30 p.m. (Eastern Standard Time), Monday through Friday (excluding holidays): - Toll free in the U.S. and Canada: TECH-SPT ( ) - Direct line for international and domestic calls: Direct line for faxes: Sending with your question or problem to crmsupport@avaya.com. You may be asked to one or more files to Technical Support for analysis of your application and its environment. 12 Media Workflow Reference

13 Product documentation Note: Note: If you have difficulty reaching Avaya Technical Support through the above URL or address, please go to for further information. Product documentation Most Avaya product documentation is available in both printed and online form. However, some reference material is available only online, and certain information is available only in printed form. A PDF document with detailed information about all of the documentation for the Avaya Interaction Center is included in the Doc directory on the product CD-ROM. This PDF document is also included on the separate documentation CD-ROM. Readme file The Readme file is a PDF file included on the Avaya Interaction Center software CD-ROM. This file contains important information that was collected too late for inclusion in the printed documentation. The Readme file can include installation instructions, system requirements, information on new product features and enhancements, suggested work-arounds to known problems, and other information critical to successfully installing and using your Avaya software. Avaya may also deliver an Addendum to the Readme, which will be posted on the Avaya Technical Support Website. The Readme Addendum will contain similar information uncovered after the manufacture of the product CD-ROM. Review the Readme file and the Readme Addendum before you install your new Avaya software. Electronic documentation The electronic documentation (in PDF or HTML format) for each Avaya Interaction Center product is installed automatically with the program. Electronic documentation for the entire Avaya product suite is included on the product CD-ROM and the documentation CD-ROM. You can also view the documentation set online at Issue 3.0 July

14 Before you begin Printed documentation You can purchase printed copies of these manuals separately. For details, see Ordering information: Avaya Publications Center on the back of this manual s title page. License to print the electronic documentation Online copies of documentation are included on the CD-ROM that accompanies every software release. An Avaya customer who has licensed software (a Licensee ) is entitled to make this online documentation available on an internal network or intranet solely for the Licensee's use for internal business purposes. Licensees are granted the right to print the documentation corresponding to the software they have purchased solely for such purposes. Right-to-print license terms Documents must be printed as-is from the provided online versions. Making changes to documents is not permitted. Documents may be printed only by any employee or contractor of Licensee that has been given access to the online documentation versions solely for Licensee's internal business purposes and subject to all applicable license agreements with Avaya. Both online and printed versions of the documents may not be distributed outside of Licensee enterprise or used as part of commercial time-sharing, rental, outsourcing, or service bureau use, or to train persons other than Licensee's employees and contractors for Licensee's internal business purposes, unless previously agreed to in writing by Avaya. If Licensee reproduces copies of printed documents for Licensee's internal business purposes, then these copies should be marked For internal use only within <Licensee> only. on the first page or cover (where <Licensee> is the name of Licensee). Licensee must fully and faithfully reproduce any proprietary notices contained in the documentation. The copyrights to all documentation provided by Avaya are owned by Avaya and its licensors. By printing any copy of online documentation Licensee indicates its acceptance of these terms and conditions. This license only governs terms and conditions of printing online documentation. Please reference the appropriate license agreement for terms and conditions applicable to any other use, reproduction, modification, distribution or display of Avaya software and documentation. 14 Media Workflow Reference

15 Educational services Educational services Avaya University provides excellent training courses on a variety of topics. For the latest course descriptions, schedules, and online registration, you can get in touch with us: Through the web at Over the telephone at (within the U.S.) (outside of the U.S.) Through at Avaya.U.Helpdesk@accenture.com Issue 3.0 July

16 Before you begin 16 Media Workflow Reference

17 Types of media workflows Chapter 1: Introduction Media workflows accomplish their tasks through a sequence of steps that you define in Workflow Designer. Media workflows handle all workflow tasks required to process, qualify, and route contacts in all media. This document provides information about the blocks you can use with media workflows and other reference information for media workflows. This section provides an overview of media workflows, including the workflows provided with Avaya IC, the knowledge you require to customize and create media workflows, and information about the other documentation available for Avaya IC workflows. Topics include: Types of media workflows on page 17. Required knowledge on page 18. How to invoke a media workflow on page 19. System workflows on page 20. Sample media workflows on page 20. Related documentation on page 27. Types of media workflows Avaya IC uses the following types of media workflows: Contact routing flows - These workflows do the following: Interpret information about a voice, , or web contact. For example, a flow can review entries made by a caller on an Interactive Voice Response Unit (IVR) or request information from the contact s Electronic Data Unit (EDU) or from the database. Make routing decisions for contacts to determine where to route the contact. analysis flows - These workflows do the following: Analyze the content of contacts. Route the contacts to agents with the appropriate skills Issue 3.0 July

18 Introduction Send an auto-response to the customer Blender flows - These workflows implement business rules to match the requests, history, and value of each contact with the skills and current workload of agents in a multi-media contact center. Business Advocate flows - These workflows do the following: Qualify and assign qualifiers to contacts to enable Business Advocate to match contacts with agents. Provide load balancing for Business Advocate systems that include multiple Logical Resource Managers. Required knowledge You can customize the sample media workflows, or create your own custom workflows. What you want to do with a media workflow determines the type and level of knowledge that you need. The following table shows the knowledge you need to perform different tasks. Task Use existing contact routing flows and modify only basic block properties. Modify existing contact routing flows, including blocks and block properties. Required knowledge Rudimentary understanding of how your contact center operates Some knowledge of your contact center s media channels and configuration Access to the information in the following documentation: - This guide - Avaya Workflow Designer User Guide Understanding of how your contact center operates In-depth knowledge of the media channels and configuration in your contact center Access to the information in the following documentation: - This guide - Avaya Workflow Designer User Guide 18 Media Workflow Reference

19 How to invoke a media workflow Task Design simple contact routing flows and modify the properties of existing blocks. Create new blocks and design complex contact routing flows. Required knowledge Complete understanding of how your contact center operates In-depth knowledge of the media channels and configuration in your contact center Access to the information in the following documentation: - This guide - Avaya Workflow Designer User Guide Complete understanding of your contact center operations Comprehensive knowledge of the media channels and configuration in your contact center An understanding of the VBA Scripting Language Access to the information in the Avaya IC documentation: - This guide - Avaya Workflow Designer User Guide - Avaya IC Workflow API Reference - IC Scripts Language Reference How to invoke a media workflow You can use one of the following methods to invoke a media workflow: Invoking a workflow through an event - Use an event such as TS.IncomingCall to invoke a workflow through the Workflow server. Note: Note: To receive an event, the Workflow server assigns to the server that sends the event. For example, the Workflow server uses TS.Assign to receive events from the Telephony server. Invoking a workflow through a method invocation - Use a method invocation such as QWorkflow.Start or QWorkflow.Run to invoke a workflow through the Workflow server. For more information about how to invoke a media workflow with a method invocation, see Avaya IC Workflow API Reference. Issue 3.0 July

20 Introduction System workflows The out-of-the-box Workflow Designer includes system flows that you must compile to run an Avaya IC system. These system flows provide functions to search for agents and transfer contacts. Avaya IC installs the project folders for system workflows as subfolders of the following directory: IC_INSTALL_DIR\IC61\design\IC\Flows\! CAUTION: CAUTION: Do not modify the system workflows. If you change these flows, your Avaya IC system will not function correctly. For information about the location of system workflows, see Avaya Workflow Designer User Guide. Sample media workflows The out-of-the-box Workflow Designer includes a set of sample media workflows. Use these workflows to configure a development environment for your Avaya IC system. When you understand the sample media workflows and are sure that they perform correctly, you can customize these workflows to meet the specific needs of your contact center. This section describes the sample media workflows and their locations. Topics include: Location of project folders on page 21. Sample contact routing flows on page 21. Sample Analysis flows on page 22. Sample Blender flows on page 23. Business Advocate flows on page Media Workflow Reference

21 Sample media workflows Location of project folders Avaya IC installs the project folders for sample media workflows as subfolders of the following directory: IC_INSTALL_DIR\IC61\design\IC\Flows Note: Note: Use Workflow Designer to compile and load the applicable sample workflows (or replacement custom workflows) in the database for your Avaya IC system to function properly. Some sample workflows need to be customized with system-specific property values before being compiled. For more information, see Avaya Workflow Designer User Guide. Sample contact routing flows You need to customize the sample contact routing flows with site-specific property values before you compile and load them in the database. Avaya IC installs the project folders for contact routing flows as subfolders of the following directory: IC_INSTALL_DIR\IC61\design\IC\Flows\Avaya The following table describes the sample contact routing flows. Workflow Project folder Project Description Incoming Call flow TS ts.prj Routes voice contacts. File: incomingcall.qfd For more information, see Incoming Call flow on page 153. Qualify Chat flow wacd wacd.prj Routes chat contacts. File: qualifychat.qfd For more information, see Qualify Chat flow on page 164. Qualify flow wacd wacd.prj Routes contacts. File: qualify .qfd For more information, see Qualify flow on page 180. Issue 3.0 July

22 Introduction Workflow Project folder Project Description IV Chat flow ivchat ivchat.prj Gathers the values needed to route a voice chat contact, and sets the value in the EDU that identifies the chat contact as a voice chat. File: ivchat.qfd For more information, see IV Chat flow on page 173. Incoming IV Chat flow TS ts.prj Routes incoming voice chat contacts. File: incoming_ivchat.qfd For more information, see Incoming IV Chat flow on page 176. Sample Analysis flows Analysis flows determine information about contacts that is useful to your contact center and execute actions based on that information to ensure more accurate routing of contacts. Avaya IC installs the sample analysis flows in the following directory: IC_INSTALL_DIR\IC61\design\IC\Flows\Avaya\IC You need to customize the sample analysis flows before you compile them. For more detailed information about the sample analysis flows, see Analysis flows on page 189. The following table describes the sample analysis flows: Workflow Project name Purpose Analyze with Keywords flow Outbound with Keywords flow ic .prj ic .prj Uses keywords to identify a limited set of attributes for incoming contacts, then sets route dispositions or routing hints according to the values that you set in the blocks. File: analyzenoca.qfd Uses keywords in the contacts to provide post-processing for outbound contacts. File: outboundnoca.qfd 22 Media Workflow Reference

23 Sample media workflows Workflow Project name Purpose Analyze with Content Analyzer flow Outbound with Content Analyzer flow ic .prj ic .prj Uses Content Analyzer to identify the language and intent of incoming contacts, then sets route dispositions or routing hints according to the results of the analysis. File: analyzeca.qfd Uses Content Analyzer to provide postprocessing for outbound contacts. File: outboundca.qfd Sample Blender flows Blender flows apply business rules to contact routing, and monitor the availability and status of contact center agents to route contacts to the appropriate agent. Avaya IC installs the sample blender flows in the following directory: IC_INSTALL_DIR\IC61\design\IC\Flows\Avaya\blender You need to customize the sample blender flows with site-specific property values before you compile and load them in the database. For more detailed information about the sample blender flows, see Blender Flows on page 235. The following table describes the sample blender flows. Workflow Project name Purpose Initialization flow blender.prj Specifies the name of the flow to run when an agent's status changes. File: initialization.qfd Client Login flow blender.prj Collects the task ceiling and task load information for the agent from the database and stores it in a global object for use by the State Flow. File: clientlogin.qfd Client Logout flow blender.prj Clears the cache on the agent desktop, including the task ceiling and task load information for the agent. File: clientlogout.qfd Issue 3.0 July

24 Introduction Workflow Project name Purpose State flow blender.prj Sets the initial task load and task ceiling for an agent. Resets the task load and task ceiling when the state field in the ADU for an agent changes. File: state.qfd Channel State flow blender.prj Resets the task load and task ceiling when the <media>state field in the ADU for an agent changes. File: channelstate.qfd Channel Server Failure flow blender.prj When one of the following fields in the ADU changes, assumes that the channel server has failed and flags the appropriate channel.state in the ADU as failed: chat.forceserverfailed .forceserverfailed voice.forceserverfailed File: channel_forceserverfailed.qfd Business Advocate flows Business Advocate flows qualify contacts for Avaya IC systems with Business Advocate. Avaya IC installs the sample Business Advocate flows in the following directory: IC_INSTALL_DIR\IC61\design\IC\Flows\Avaya\Advocate Business Advocate flows include the following: System workflows for Business Advocate on page 25. Sample workflows for Business Advocate on page Media Workflow Reference

25 Sample media workflows System workflows for Business Advocate! CAUTION: CAUTION: Do not modify system flows for Business Advocate. If you modify any of the system workflows, your Business Advocate system will not function correctly. The following table describes the system workflows for Business Advocate. Workflow Project Name Purpose Synchronization Advocate.prj Synchronizes qualifier representations in global variables with the qualifiers in the database. Fetches the category/qualifier values and their associated numeric representations from the database and creates global string variables for the Workflow server. File: update_qualifiersetids.qfd Sample workflows for Business Advocate You need to customize the sample Business Advocate workflows with site-specific property values before you compile and load them in the database. For more detailed information, see Business Advocate flows on page 259. Issue 3.0 July

26 Introduction The following table describes the sample Business Advocate flows. Workflow Project Name Purpose Qualify Voice flow Advocate.prj Identifies a collection of Business Advocate qualifiers for an incoming voice contact. Assigns those qualifiers to the voice contact so that Business Advocate can accurate route the contact to an appropriate agent. File: qualifyvoice_adv.qfd For more information, see Qualify Voice flow for Business Advocate on page 263. Qualify Chat flow Advocate.prj Identifies a collection of Business Advocate qualifiers for a chat contact. Assigns those qualifiers to the chat contact so that Business Advocate can accurate route the contact to an appropriate agent. File: qualifychat_adv.qfd For more information, see Qualify Chat flow for Business Advocate on page 271. Qualify flow Advocate.prj Identifies a collection of Business Advocate qualifiers for an contact. Assigns those qualifiers to the contact so that Business Advocate can accurate route the contact to an appropriate agent. File: qualify _adv.qfd For more information, see Qualify flow for Business Advocate on page 281. Exception handling Advocate.prj Responds to exceptions that occur when Business Advocate cannot match an agent to a contact. File: handle_exception.qfd Transfer to agent Advocate.prj Supports the ability of the agent desktop application to transfer either an contact or a voice contact to a specific agent. File: transfertoagent.qfd 26 Media Workflow Reference

27 Related documentation Related documentation This document provides reference information about media workflows. To learn more about Workflow Designer, agent script workflows, and the API methods used to customize workflows, consult the following documents: Avaya Workflow Designer User Guide - This document provides introductory information about Workflow Designer and workflows, including how to use Workflow Designer to create and customize simple workflows. Agent Script Workflow Reference - This document provides procedures, block definitions, and advanced conceptual information regarding the workflows that are used to assist agents in communicating with contacts. Use this document when you are creating Prompter workflows. Avaya IC Workflow API Reference - This document is a reference for the IC Script extensions that are used for the Workflow server and Content Analyzer servers. Use these extensions to customize the basic functionality of these servers. IC Business Advocate Configuration and Administration - This document provides procedures, block definitions, and advanced conceptual information for workflows that compare contact information and needs against available agents through Avaya IC Business Advocate workflows. Avaya IC for Siebel 7 Integration - This document provides procedures, block definitions, and advanced conceptual information for workflows that are used in an environment where Avaya IC and Siebel 7 are used in conjunction on agent desktops to enhance interacting with contacts and handling multiple contacts through different media. Issue 3.0 July

28 Introduction 28 Media Workflow Reference

29 Routing hints and queues Chapter 2: Routing hints The sample workflows provided with Avaya IC use a collection of hints to drive contact routing. All qualification and routing workflows use these hints, including standard contact routing workflows, Business Advocate qualification flows, and Siebel flows. You must understand how the sample workflows use routing hints before you customize the workflows to meet the needs of a contact center. This section describes routing hints and how the sample Avaya IC workflows use routing hints to route contacts. This section includes the following topics: Routing hints and queues on page 29. Types of contact qualification and routing on page 34. Routing hints for voice contacts on page 35. Routing hints for chat contacts on page 39. Routing hints for contacts on page 43. This chapter includes information about routing hints in an Avaya IC system that includes an integration with a Siebel application. For more information, see Avaya IC for Siebel 7 Integration, which is available on the Avaya IC for Siebel 7 installation CD-ROM. Routing hints and queues When you set up standard contact routing in Avaya IC, you must assign queues to routing hints. You assign queues in the RoutingHint table of the Directory server. You can enter the same routing hint multiple times in the RoutingHint table, and associate each version of the routing hint with a different set of queues. You can use this ability to create multiple hints with the same queue defined for a channel. One unique queue would then match all of the hints. This section includes the following topics: RoutingHint table on page 30. Routing hints and addresses on page 30. Example: routing hint for on page 31. Issue 3.0 July

30 Routing hints RoutingHint table During contact routing, the workflow extracts hints from the EDU information and customer-related database information. The workflow does one of the following with the routing hints: Uses the routing hints to find the associated queue in the RoutingHint table. Maps the routing hints to another value, then uses that value to find the associated queue in the RoutingHint table. You use the Configuration tab of IC Manager to configure the RoutingHint table in the Directory server. The following figure shows a routing hint that uses the To address for contacts. As you can see from this example, the Routing Hint field contains the name of the routing hint. The name of the routing hint is the To address that customers can use to send contacts to the contact center. This routing hint has an queue that the Qualify workflow uses to route an contact with this routing hint. The routing hint is associated with the tenant DefaultTenant. Routing hints and addresses Avaya IC no longer requires you to associate an address with an queue or a chat queue. Instead, you configure a routing hint that uses the address as the name of the routing hint, and associate that routing hint with a queue. 30 Media Workflow Reference

31 Routing hints and queues Example: routing hint for In this example, a contact center uses the Avaya IC channel with the following tenants: Ferrar for the Ferrar Corporation Lambo for Lambo Inc. Each tenant has a Sales department, a Support department, and a QA department. Each tenant also includes agents who speak both English and Italian. This example includes the following topics that examine the configuration of routing hints and other items needed to route contacts to the LamboSupportItalian@Lambo queue: Agent workgroups Agent workgroups on page 31. Workgroups and queues on page 32. Routing hints on page 32. Assignment of hints to queues on page 33. Routing contacts to the queue on page 33. To accommodate the structure of this contact center, the Avaya IC system includes language specific workgroups and department specific workgroups. For example, the Lambo tenant includes the following workgroups: EnglishLambo ItalianLambo QALambo SalesLambo SupportLambo Issue 3.0 July

32 Routing hints Workgroups and queues The following figure shows the Membership tab for the Lambo Tenant. The workgroups are in the left pane of the tab. The queues associated with each workgroup are in the right pane of the tab. As you can see, the queue is in the SupportLambo workgroup and the ItalianLambo workgroup. Routing hints The following table shows the minimum number of routing hints that would be needed by the contact center. This example uses only the first hints in each category. Hint category Hint value Description language it contacts in Italian. en contacts in English. intent support contacts sent to the address for the Support department. sales QA contacts sent to the address for the Sales department. contacts sent to the address for the QA department. 32 Media Workflow Reference

33 Routing hints and queues Assignment of hints to queues Routing hints are assigned to queues in the RoutingHint table of the Directory server, as shown in the following figure. The following table shows the routing hints associated with the queue in the Routing Hint table. Hint category Hint value Description language it Routing hint for contacts in Italian. intent support Routing hint for contacts sent to the address for the Support department. Routing contacts to the queue To route an incoming contact, the Qualify workflow does the following: 1. Identifies the following routing hints for the contact: support routing hint from the To address of the contact, it routing hint from the Analysis flow run before the Qualify workflow Issue 3.0 July

34 Routing hints 2. Uses the values of the routing hints to look up the associated queue in the RoutingHint table of the Directory server. 3. Routes the contact to the queue. Because the queue is a logical grouping of agent workgroups, the Qualify workflow queues the contact to the SupportLambo workgroup and the ItalianLambo workgroup. Any available agent that speaks Italian and can handle contacts for support can receive this contact. If the Qualify workflow identified the sales routing hint, but did not identify a language routing hint, the workflow could route the contact to one of the following queues: LamboSales@Lambo LamboSalesEnglish@Lambo LamboSalesItalian@Lambo The Qualify workflow looks at the relative load of each queue, then selects the queue with fewest contacts. Assuming the workflow selects the LamboSales@Lambo queue, agents in the following workgroups could receive the contact: EnglishLambo, ItalianLambo, and SalesLambo. From this example, you can see that how you define various combinations of routing hints can focus the queue selection to a particular queue and to a specific set of workgroups. Types of contact qualification and routing Avaya IC includes two types of contact qualification and routing. An Avaya IC system that integrates with a Siebel application also uses these types of contact qualification and routing. Both types use the same basic set of routing hints for each media channel. The following topics describe the unique aspects of each type of contact qualification and routing: Standard contact qualification and routing on page 34. Business Advocate qualification and routing on page 35. Standard contact qualification and routing Standard contact qualification and routing extensively uses the following for a basic Avaya IC system and a basic Avaya IC system with a Siebel integration: RoutingHint table in the Directory server Relationship of routing hints to queues 34 Media Workflow Reference

35 Routing hints for voice contacts During qualification and routing, standard workflows do the following: 1. Identify a collection of routing hints. 2. Look up the routing hints in the RoutingHint table of the Directory server. 3. Route the contact to a queue associated with the routing hints in the RoutingHint table. Business Advocate qualification and routing Business Advocate qualification uses the same routing hints as standard qualification, and uses information fetched from a record in one of the following databases: For Business Advocate, the Customer table in the CCQ database For Business Advocate with a Siebel integration, the Contact table in the Siebel database During qualification, Business Advocate workflows do the following: 1. Identify a collection of hints. 2. Translate the hints into Business Advocate qualifiers. 3. Send the qualifiers to the Logical Resource Manager which selects an agent to match with the contact. Business Advocate qualification does not require any special configuration of queues, tenants, or workgroups. The only routing hint that you need to configure in the RoutingHint table is a routing hint for chat contacts. For more information, see Routing hints for chat contacts on page 39. Routing hints for voice contacts The sample routing and qualification workflows for voice contacts do not include a prequalification step. Therefore, the DNIS, or the number that the customer dialed, is the only routing hint that is always available for a contact. The workflows consider the DNIS to be a value of the intent category. This section describes how the sample qualification and routing workflows for voice contacts use routing hints. This section includes the following topics: Routing hints in the Incoming Call flow on page 36. Routing hints in the Qualify Voice flow for Business Advocate on page 37. Issue 3.0 July

36 Routing hints Routing hints in the Incoming Call flow The sample Incoming Call flow requires at least one routing hint in the intent category with a value of the DNIS where voice contacts arrive. The Incoming Call flow works the same in a basic Avaya IC system and in a basic Avaya IC system with a Siebel integration. The following table shows the sample Incoming Call flows. Type of Avaya IC system Workflow project Workflow name Basic Avaya IC system ts incomingcall.qfd Basic Avaya IC system with Siebel integration ts_sbl incomingcall.qfd Configuration for routing hints in the Incoming Call flow You do not need to configure any blocks to use the sample Incoming Call flow. To use the sample Incoming Call flow, do the following: 1. Create the following voice queues with the addressable property turned on: A queue named DefaultVoiceQueue@DefaultTenant for a failover number If desired, a queue for each internal queue or VDN or Vector on the switch that has a different Route To value. 2. For each voice queue associated with the DNIS, create a routing hint equal to the value of the DNIS number. Do not select a tenant. How the Incoming Call flow uses the routing hints When a voice contact arrives in Avaya IC, the Incoming Call flow will: 1. Identify the DNIS as an intent routing hint. 2. Use the DNIS to look up routing hints in the RoutingHint table of the Directory server. 3. Route the contact to a queue associated with the routing hints in the RoutingHint table. If the Avaya IC system includes a TSQS server, the workflow routes the voice contact to the voice queue with the lowest number of contacts. If the Avaya IC system does not include a TSQS server, the workflow routes the contact to the first voice queue found in the RoutingHint table. For more detailed information, see Incoming Call flow on page Media Workflow Reference

37 Routing hints for voice contacts Routing hints in the Qualify Voice flow for Business Advocate The sample Qualify Voice flow for Business Advocate does not require a routing hint. However, the Qualify Voice flow uses the DNIS for an incoming voice contact as a hint, then maps this hint to a Business Advocate qualifier. The following table shows the sample Qualify Voice flows for Business Advocate. Type of Avaya IC system Workflow project Workflow name Business Advocate only advocate qualifyvoice_adv.qfd Business Advocate and a Siebel integration advocate_sbl qualifyvoice_adv_sbl.qfd Configuration for routing hints in the Qualify Voice flow You do not need to create any routing hints for the Qualify Voice flow. Configuration for qualifiers in the Qualify Voice flow The Qualify Voice flow for Business Advocate maps the intent routing hints to a Business Advocate qualifier. The Qualify Voice flow requires the Channel/voice qualifier. You can create additional qualifiers. For example, create a qualifier category of intent with values such as support or printers. The Map to Qualifiers block maps the qualifier values to the DNIS numbers. You must configure these values in the Map to Qualifier (DNIS) block. For a complete list of qualifiers used by the sample Qualify Voice flow, see IC Business Advocate Configuration and Administration. Issue 3.0 July

38 Routing hints Database information used by the Qualify Voice flow The following table shows the attributes from the customer record in the database used by the Qualify Voice flow. Hint category CCQ Customer field Siebel Contact field Qualifier category Description preferredagent preferredagent Contact.PartyNa me not used Identifies the preferred agent for a customer. If the workflow finds a valid Avaya IC agent, the workflow attempts to route the contact to that agent. If the routing attempt is unsuccessful, the workflow identifies a qualifier set to use to route the contact. customertype customertype Contact.Status customertype Identifies the type of customer and the relative worth of a contact from that customer to the contact center. The values for the qualifiers must match the values entered in the customer records. language language Note: These values must be two character ISO language codes in lowercase, such as en. Contact.Preferre d LanguageCode Note: These values must be three character ISO language codes in uppercase, such as ENU. language Identifies the preferred language of the voice contact. The Map to Qualifier block in the workflow maps the language code to the corresponding language code used by Business Advocate. Business Advocate typically uses the full word for the language, such as english. How the Qualify Voice flow uses the hints, qualifiers, and database information When a voice contact arrives in Avaya IC, the Qualify Voice flow: 1. Identifies a collection of hints, including the DNIS and ANI. 38 Media Workflow Reference

39 Routing hints for chat contacts 2. Uses the ANI to retrieve a customer record from the database. 3. Maps the DNIS hint to an intent qualifier. 4. Translates the collection of qualifiers, including the intent qualifier, into a numeric sequence. 5. Calls the postqualification method of the TSA server. For more detailed information about the Qualify Voice flow in a Business Advocate only system, see Qualify Voice flow for Business Advocate on page 263. For information about the Qualify Voice flow in a Business Advocate with Siebel integration system, see Avaya IC for Siebel 7 Integration. Routing hints for chat contacts The sample routing and qualification workflows for chat contacts use the Web pages that a customer browses on the Web Management Website as a prequalification step. The following table describes the routing hints that Web pages can provide to prequalify a chat contact. Routing hint category language intent Routing hint value The language selected by a customer as that customer enters the Website. The routing hint associated with the Web Self-Service page where the customer initiates the chat contact. This section describes how the sample qualification and routing workflows for chat contacts use routing hints. This section includes the following topics: Routing hints in the Qualify Chat flow on page 39. Routing hints in the Qualify Chat flow for Business Advocate on page 41. Routing hints in the Qualify Chat flow The sample Qualify Chat flow for standard contact routing considers only the language and intent routing hints that are provided by the Website. The Qualify Chat flow works the same in a basic Avaya IC system and in a basic Avaya IC system with a Siebel integration. Issue 3.0 July

40 Routing hints The following table shows the sample Qualify Chat flows. Type of Avaya IC system Workflow project Workflow name Basic Avaya IC system wacd qualifychat.qfd Basic Avaya IC system with Siebel integration wacd_sbl qualifychat_sbl.qfd Configuration for routing hints in the Qualify Chat flow To use the sample Qualify Chat flow, do the following: 1. If desired, create additional chat queues with: Addressable property turned on Appropriate tenant selected 2. Create routing hints in the RoutingHint table of the Directory server. 3. Associate the routing hints with: Chat queue Tenant Web Self-Service documents 4. For Voice Chat, set the following properties in the Set Route Parameters block: IVChatWorkGroup PVChatWorkgroup How the Qualify Chat flow uses the routing hints When a chat contact arrives in Avaya IC, the Qualify Chat flow will: 1. Identify the intent and language routing hints. 2. Use the routing hints to look up the queue in the RoutingHint table of the Directory server. 3. Route the contact to a queue associated with the routing hints in the RoutingHint table. For more detailed information, see Qualify Chat flow on page Media Workflow Reference

41 Routing hints for chat contacts Routing hints in the Qualify Chat flow for Business Advocate The Qualify Chat flow for Business Advocate uses the same language and intent routing hints as the standard qualification. The workflow maps these hints to a Business Advocate qualifier. However, the Business Advocate workflows ignore the tenant value. The following table shows the Qualify Chat flows for Business Advocate. Type of Avaya IC system Workflow project Workflow name Business Advocate only advocate qualifychat_adv.qfd Business Advocate and a Siebel integration advocate_sbl qualifychat_adv_sbl.qfd Configuration for routing hints in the Qualify Chat flow You must associate the routing hints with the Default chat queue. The Qualify Chat flow does not use the chat queue to route the contact. However, the Web Self-Service document on the Website uses the chat queue to assign the correct routing hint for intent to the chat contact. To use the Qualify Chat workflow: 1. Create routing hints in the RoutingHint table of the Directory server. 2. Associate the routing hints with: Default chat queue of DefaultChatQueue@DefaultTenant Category/qualifier Web Self-Service documents Configuration for qualifiers in the Qualify Chat flow The workflow maps routing hints to a Business Advocate qualifier. However, the Business Advocate workflows ignore the tenant value. You must create an intent qualifier for each routing hint that you associate with a Web Self-Service document. For a complete list of qualifiers used by the sample Qualify Chat flow, see IC Business Advocate Configuration and Administration. Issue 3.0 July

42 Routing hints Database information used by the Qualify Chat flow The following table shows the attributes from the customer record in the database used by the Qualify Chat flow. Hint category CCQ Customer field Siebel Contact field Qualifier category Description preferredagent preferredagent Contact.Party Name not used Identifies the preferred agent for a customer. If the workflow finds a valid Avaya IC agent, the workflow attempts to route the contact to that agent. If the routing attempt is unsuccessful, the workflow identifies a qualifier set to use to route the contact. customertype customertype Contact.Status customertype Identifies the type of customer and the relative worth of a contact from that customer to the contact center. The values for the qualifiers must match the values entered in the customer records. language language Note: These values must be two character ISO language codes in lowercase, such as en. Contact.Preferre dlanguagecode Note: These values must be three character ISO language codes in uppercase, such as ENU. language Identifies the preferred language of the voice contact. The Map to Qualifier block in the workflow maps the language code to the corresponding language code used by Business Advocate. Business Advocate typically uses the full word for the language, such as english. 42 Media Workflow Reference

43 Routing hints for contacts How the Qualify Chat flow uses the hints, qualifiers, and database information When a chat contact arrives in Avaya IC, the Qualify Chat flow: 1. Identifies a collection of hints, including the language and intent. 2. If the customer logged into the Website with an login ID that exists in a customer record in the database, uses the customer_key field from the EDU to retrieve the customer record from the database. 3. Maps the hints to qualifiers. 4. Translates the collection of qualifiers into a numeric sequence. 5. Calls the postqualification method of the WAA server. For more detailed information about the Qualify Chat flow in a Business Advocate only system, see Qualify Chat flow for Business Advocate on page 271. For information about the Qualify Chat flow in a Business Advocate with Siebel integration system, see Avaya IC for Siebel 7 Integration. Routing hints for contacts The sample routing and qualification workflows for contacts use the largest number of routing hints. The routing and qualification flows use the inbound analysis flows to prequalify contacts and the outbound analysis flows to postqualify contacts. If the Avaya IC system is not configured for analysis, these routing hints are not available to the routing and qualification flows. This section describes how the sample qualification and routing workflows for contacts use routing hints. This section includes the following topics: analysis flows that identify routing hints on page 43. Routing hints in the Qualify flow on page 45. Routing hints in the Qualify flow for Business Advocate on page 46. analysis flows that identify routing hints An Avaya IC system can omit analysis or use the following versions of analysis: analysis with keywords, which includes the following workflows: - Analyze with Keywords flow - Outbound with Keywords flow Issue 3.0 July

44 Routing hints analysis with Content Analyzer, which includes the following workflows: - Analyze with Content Analyzer flow - Outbound with Content Analyzer flow An Avaya IC system with Business Advocate uses the same analysis flows. For information about these analysis flows, see Analysis flows on page 189. An Avaya IC system which includes an integration with a Siebel application uses a different set of two different inbound analysis flows and one outbound analysis flow. For information about these analysis flows, see Avaya IC for Siebel 7 Integration, which is available on the Avaya IC for Siebel 7 installation CD-ROM. Routing hints identified by analysis flows The Set Routing Hint block in the analysis flows identifies and assigns all routing hints for an contact. You can customize all of these routing hints except for the language hint in this block. For analysis with Content Analyzer, the language routing hint is set by the GetLanguage block. If the Avaya IC system includes a Siebel integration and Content Analyzer, the language routing hint is set by the Get CA Results from EDU block. The analysis flows stores the routing hints in the qw_qualifier table of the CCQ database indexed by the msgid of the . The following table shows the routing hints identified by the sample analysis flows. Avaya IC system Inbound analysis flow Inbound routing hints Outbound analysis Outbound routing hints Standard Avaya IC system ic .analyzeno ca intent printers sales ic .outbound noca QA approvalrequired Standard Avaya IC system with Content Analyzer ic .analyzeca intent home computing desktop ic .outboundc a QA approvalrequired suspectcontent language 2 character ISO code 44 Media Workflow Reference

45 Routing hints for contacts Avaya IC system Inbound analysis flow Inbound routing hints Outbound analysis Outbound routing hints Avaya IC system with Siebel integration ic _sbl. preanalyzenoca_ sbl intent printers support sales ic _sbl. outboundnoca_sb l none Avaya IC system with Siebel integration and Content Analyzer ic _sbl. preanalyzeca_ sbl ic _sbl. postanalyze_s bl none intent sales support home computing ic _sbl. outbound _s bl none language 3 character ISO code Routing hints in the Qualify flow The sample Qualify flow for standard contact routing considers the routing hints that are provided by the analysis flows. The Qualify flow works the same in a basic Avaya IC system and in a basic Avaya IC system with a Siebel integration. The following table shows the sample Qualify flows. Type of Avaya IC system Workflow project Workflow name Basic Avaya IC system wacd qualify .qfd Basic Avaya IC system with Siebel integration wacd_sbl qualify _sbl.qfd Configuration for routing hints in the Qualify flow To use the sample Qualify flow, do the following: 1. If desired, create additional queues with: Addressable property turned on Appropriate tenant selected Issue 3.0 July

46 Routing hints 2. Create routing hints in the RoutingHint table of the Directory server: For inbound contacts, accounts that can be used in the To address field For outbound contacts, routing hints for approvalrequired and suspectcontent 3. Associate the routing hints with: queue Tenant How the Qualify flow uses the routing hints for inbound contacts When an contact arrives in Avaya IC, the Qualify flow: 1. Identifies the routing hints, if any, from the analysis flows and the EDU. 2. Uses the routing hints to look up the queue in the RoutingHint table of the Directory server. 3. Routes the contact to a queue associated with the routing hints in the RoutingHint table. For more detailed information, see Qualify flow on page 180. How the Qualify flow uses the routing hints for outbound contacts When an agent sends an contact from Avaya IC, the Qualify flow: 1. Tests whether the type is SUP. 2. If the type is SUP, extracts the QA routing hint. 3. Fetches the routing hints from the original inbound Uses the routing hints to look up the queue in the RoutingHint table of the Directory server. 5. Routes the contact to a queue associated with the routing hints in the RoutingHint table. If there is no queue associated with both routing hints, routes the contact to the default queue identified in the Map Hints to Queue block. For more detailed information, see Qualify flow on page 180. Routing hints in the Qualify flow for Business Advocate The Qualify flow for Business Advocate uses the same routing hints as the standard qualification. The workflow uses the intent and QA hints in the same way as the standard workflows. However, the workflow uses the language and preferredagent hints, if any, differently. 46 Media Workflow Reference

47 Routing hints for contacts For a language hint, if the Fetch Routing Hints block finds a language hint, then the workflow uses that hint. If no language hint is available, the workflow uses the preferred language in the Customer record. For a preferredagent hint, the workflow uses the agent ID in the root of the EDU, if one is available. If the EDU does not include an agent ID, the workflow uses the value for preferred agent in the Customer record. The following table shows the Qualify flows for Business Advocate. Type of Avaya IC system Workflow project Workflow name Business Advocate only advocate qualify _adv.qfd Business Advocate and a Siebel integration advocate_sbl qualify _adv_sbl.qfd Configuration for routing hints in the Qualify flow You do not need to create routing hints for the Qualify workflow. Configuration for qualifiers in the Qualify flow The workflow maps the hints to Business Advocate qualifiers. For a complete list of qualifiers used by the sample Qualify flow, see IC Business Advocate Configuration and Administration. Database information used by the Qualify flow The following table shows the attributes from the customer record in the database used by the Qualify flow for Business Advocate. Hint category CCQ Customer field Siebel Contact field Qualifier category Description preferredagent preferredagent Contact.PartyNa me not used Identifies the preferred agent for a customer. If the workflow finds a valid Avaya IC agent, the workflow attempts to route the contact to that agent. If the routing attempt is unsuccessful, the workflow identifies a qualifier set to use to route the contact. Issue 3.0 July

48 Routing hints Hint category CCQ Customer field Siebel Contact field Qualifier category Description customertype customertype Contact.Status customertype Identifies the type of customer and the relative worth of a contact from that customer to the contact center. The values for the qualifiers must match the values entered in the customer records. language language Note: These values must be two character ISO language codes in lowercase, such as en. Contact.Preferre dlanguagecode Note: These values must be three character ISO language codes in uppercase, such as ENU. language Identifies the preferred language of the voice contact. The Map to Qualifier block in the workflow maps the language code to the corresponding language code used by Business Advocate. Business Advocate typically uses the full word for the language, such as english. QA none none QA The value can be either of the following. The value cannot be both. approvalrequired suspectcontent How the Qualify flow uses the routing hints for inbound contacts When an contact arrives in Avaya IC, the Qualify flow: 1. Identifies the routing hints, if any, from the analysis flows and the EDU. 2. Maps the hints to qualifiers. 3. Translates the collection of qualifiers into a numeric sequence. 4. Calls the postqualification method of the WAA server. For more detailed information, see Qualify flow for Business Advocate on page 281. For information about the Qualify flow in a Business Advocate with Siebel integration system, see Avaya IC for Siebel 7 Integration. 48 Media Workflow Reference

49 Routing hints for contacts How the Qualify flow uses the routing hints for outbound contacts When an agent sends an contact from Avaya IC, the Qualify flow: 1. Tests whether the type is SUP. 2. If the type is SUP, extracts the QA routing hint. 3. Fetches the routing hints from the original inbound Maps the hints to qualifiers. 5. Translates the collection of qualifiers into a numeric sequence. 6. Calls the postqualification method of the WAA server. For more detailed information, see Qualify flow for Business Advocate on page 281. For information about the Qualify flow in a Business Advocate with Siebel integration system, see Avaya IC for Siebel 7 Integration. Issue 3.0 July

50 Routing hints 50 Media Workflow Reference

51 Chapter 3: Standard blocks This section describes the standard blocks installed on palettes in Workflow Designer that are typically used in media workflows. For information about the palettes not described in this section, see Avaya Workflow Designer User Guide. This section includes the following topics: ADU palette on page 52. Advocate palette on page 55. Application palette on page 71. Content Analysis palette on page 78. EDU palette on page 85. palette on page 95. General palette on page 108. Routing palette on page 120. Telephony palette on page 134. Tools palette on page 137. Issue 3.0 July

52 Standard blocks ADU palette The ADU palette contains blocks that are typically used in media workflows that include ADUs, such as Blender flows. For more information, see Blender Flows on page 235. This section includes the following topics which describe those blocks: Fetch ADU on page 52. Get ADU Values on page 53. Fetch ADU Description Sample workflow Basic properties Advanced properties Retrieves a record from the ADU server, based on the current ADUID, by issuing the method, ADU.GetValues. By default the request is sent to server ADU, passing Script variable adu_id. If adu_id is empty, the block tries to fill it from the data that arrived with the event or method that started this flow. It stores the returned sequence of couples in Script variable adudata. You can modify these settings in the advanced properties. Advanced properties allow automatic ADU termination, if desired. For an example of how Fetch ADU can be used in a workflow, see State flow on page 243. The Basic tab of Fetch ADU does not have any properties. The Advanced tab of Fetch ADU includes the properties in the following table. Property Default Value Description adu_id $adu_id Script variable obtained from event or method that invokes the workflow. adudata $adu_data Script variable where sequence of couples returned by ADU server is stored. aduterminate on If set to on, terminates the ADU. Note: To terminate an ADU, you must also configure the value of adutouched. 52 Media Workflow Reference

53 ADU palette Property Default Value Description adutouched true If set to true, lets you terminate the ADU. Note: To terminate an ADU, you must also configure the value of aduterminate. blockdebug off Debug level of the block. Before changing the default value, see Block debug property on page 327. maxdebuglength Maximum debug output length. For more information, see Avaya Workflow Designer User Guide. servername ADU Name of the ADU server. start Fetch Adu Block IC Script. Alarms Fetch ADU generates an alarm (QWorkflow.FetchAduError): If no ADUID can be determined If the request returns no data Connections Accepts the following connections: Input: 1 or more Output: 1 Get ADU Values! CAUTION: CAUTION: Use this block only when the number of ADU attributes that have to be assigned to Script variables increases as the workflow performs time critical functions, such as routing voice contacts in a large contact center. If the number of ADU attributes does not increase, use a simple assignment statement with the method FindValue() on the IDL Data Object adudata. Description Assigns values from an ADU object (retrieved by Fetch ADU) into given targets. These values are the individual attributes of the ADU that are stored in the Script variable adudata. Issue 3.0 July

54 Standard blocks Sample workflow Basic properties For an example of how Get ADU Values can be used in a workflow, see State flow on page 243. The Basic tab of Get ADU Values includes the properties in the following table. Property Default Value Description Field_N empty Field in the ADU from which the block should retrieve data. You can specify up to 10 fields. Target_N $ChangeMe Target where the block should store values retrieved from the ADU field. For example, if you specify an ADU field in Field_10, enter the target for the data in Target_10. Advanced properties The Advanced tab of Get ADU Values includes the properties in the following table. Property Default Value Description adudata $adu_data Script variable where sequence of couples returned by ADU server is stored. blockdebug off Debug level of the block. Before changing the default value, see Block debug property on page 327. start Get ADU Values Block IC Script Alarms Connections Generates no alarms. Accepts the following connections: Input: 1 or more Output: 1 54 Media Workflow Reference

55 Advocate palette Advocate palette The Advocate palette contains blocks for workflows that qualify and route contacts in an Avaya IC environment with Business Advocate. For more information, see Business Advocate flows on page 259. This section includes the following topics which describe the blocks on the Advocate palette: Fetch LRMID on page 55. Map to Qualifier on page 56. Post Qualification on page 58. Set Qualifier on page 62. Set Voice Wait Treatment on page 65. Translate Category/Qualifier on page 68. Fetch LRMID Description Prerequisites Sample workflow Fetches the LRM ID for the Logical Resource Manager associated with the preferred agent for the contact. This block: 1. Uses the login ID of the preferred agent to search the Employee table. 2. Fetches the lrmid_pkey field from the agent record. To use this block, set the value of the DBNetwork property in the Start block of the workflow to q_qualification. This block also requires that the workflow include a Get Customer Record block to retrieve the login ID of the preferred agent from the customer record and add that value to the customerinfo.preferredagent value of the EDU. For an example of how the Fetch LRMID block can be used in a workflow, see Qualify Voice flow for Business Advocate on page 263. Issue 3.0 July

56 Standard blocks Basic properties The Basic tab of Fetch LRMID includes the properties in the following table. Property Default Value Description LoginName $PreferredAgent Input parameter for the search. Script variable that contains the login ID of the preferred agent for the customer. The login ID is retrieved by a Get Customer Values block and added to the customerinfo.preferredagent value of the EDU. LRMID $LRMid Output parameter for the search. Script variable that contains the lrmid_pkey retrieved by the search on the Employee table. Advanced properties The Advanced tab of Fetch LRMID includes the properties in the following table. Property Default Value Description blockdebug on Debug level of the block. Before changing the default value, see Block debug property on page 327. start Fetch LRMID Block IC Script. Alarms Connections Generates no alarms. Accepts the following connections: Input: 1 or more Output: 1 Map to Qualifier Description Maps the values in a script variable to a value in another script variable that contains Business Advocate qualifiers. This block: 1. Compares the value of the Source script variable to one of four possible values listed on the Basic tab. 2. If the value of the Source script variable matches a possible value, maps that value to the corresponding qualifier. 3. Assigns the qualifier value to the Target script variable. 56 Media Workflow Reference

57 Advocate palette This block is frequently used before a Set Qualifier block to map contact center specific values to Business Advocate qualifier values. Sample workflow Basic properties For an example of how the Map to Qualifier block can be used in a workflow, see Qualify Voice flow for Business Advocate on page 263. The Basic tab of Map to Qualifier includes the properties in the following table. Property Default Value Description DefaultQualifier empty Default qualifier for the block to use if none of the Value_N values can be mapped to the value of the Source property. Qualifier_N empty Up to four qualifier values. Each qualifier value must map to the equivalent Value_N property. For example, to map language qualifiers, if the value of the Value_1 property is sp, then the value of Qualifier_1 should be spanish. Source empty Mandatory. Script variable where the block retrieves the value to be compared to the Value_N properties. For example, enter the script variable $custlanguage to use the preferred language from the customer record. Target empty Mandatory. Script variable where the block stores the results of the mapping. If the value of the Source property does not match the value of a Value_N property, and no DefaultQualifier is set, the block stores a value of NULL in the script variable. Value_N empty Up to four values. Each value must map to the equivalent Qualifier_N property. For example, to map language qualifiers, if the value of Qualifier_1 is spanish, then assign a value of sp to the Value_1 property. Issue 3.0 July

58 Standard blocks Advanced properties The Advanced tab of Map to Qualifier includes the properties in the following table. Property Default Value Description blockdebug on Debug level of the block. Before changing the default value, see Block debug property on page 327. start Map to Qualifier Block IC Script. Alarms Connections Generates no alarms. Accepts the following connections: Input: 1 or more Output: 1 Post Qualification Description Completes the qualification of a contact for an Avaya IC system with Business Advocate. This block takes the information collected in other Advocate blocks, such as Set Qualifier, Translate Category/Qualifier and Wait Treatment. The block then returns a collection of qualifiers, a wait treatment style, and the other information that the Logical Resource Manager needs to match the contact to a qualified agent.! CAUTION: CAUTION: Improper configuration of this block can cause serious routing problems, such as unnecessary routing exceptions and route attempt failures. During the post qualification process, this block: 1. Sets the PostQualificationAction to route and sets ExcludeAgent to no. 2. Adds values collected by the workflow to the script variable for the routing hints, then writes those values to the advocate.n.routinginfo.n container in the EDU. The values can include: agent_id, lrmid, and exclusion_flag. 3. Dumps the current contents of the EDU to the workflow log file, if block debugging is enabled. 4. Uses values from the EDU to calculate the arrival time of the contact and determine the correct advocatecontainerindex value to set. 58 Media Workflow Reference

59 Advocate palette 5. Delivers the required values and arguments with the PostQualification() method back to the server that started the workflow, as follows: For voice qualification workflows, the Telephony Services Adaptor server. For qualification workflows, the Web Advocate Adaptor server. For chat qualification workflows, the Web Advocate Adaptor server. Sample workflow Basic properties For an example of how this block can be used in a flow, see Qualify Voice flow for Business Advocate on page 263 and Qualify Chat flow for Business Advocate on page 271. The Basic tab of Post Qualification includes the properties in the following table. Property Default Value Description AgentID $PreferredAgent String property with a value of a valid IC AgentID or NULL. This value is retrieved from the $PreferredAgent script variable. If the value is not NULL, Business Advocate will attempt to match the contact with this agent. ContactHandle $contacthandle For chat contact and contacts only. String property with the value of the contacthandle input parameter to the workflow. This value is retrieved from the $contacthandle script variable set by the Complete Qualification block. This property provides a unique identifier that helps the Web Advocate Adaptor server track the contact. Issue 3.0 July

60 Standard blocks Property Default Value Description VoiceContainer $VoiceContainer Mandatory. String property with the value of the advocatecontainerindex input parameter to the workflow. This value is retrieved from the $VoiceContainer script variable. Post Qualification uses this value to determine which advocate container in the EDU should include the new routinginfo subcontainer. This container and technique are used by Translate Category/Qualifier. WaitTreatment Style $waittreatment style For voice contacts only. String property with the value of the wait treatment style requested for a voice contact. If this value is not set by a Set Voice Wait Treatment block, the following default values are used: voice = 1 chat = 0 = -1. Tip: These values are not used for contacts or chat contacts, but the WebACD server requires a value. 60 Media Workflow Reference

61 Advocate palette Advanced properties The Advanced tab of Post Qualification includes the properties in the following table. Property Default Value Description blockdebug on Debug level of the block. Before changing the default value, see Block debug property on page 327. ConnectionData $sscchangeme Mandatory for chat contacts only. SeqSeqCouple with the value of the wait treatment sequence for the chat contact. This wait treatment sequence for chat is set by one or more Set Chat Wait Treatment blocks. Important: If you do not configure this property with the value assigned to the ChatWaitSequence property of the Set Chat Wait Treatment block, the chat wait treatment cannot work correctly. ExcludeAgent No Boolean property with the following options available from the drop-down list: Yes: Excludes the value assigned to the AgentID property from this route attempt. For example, the Transfer to Agent workflow uses this option to make sure that the contact is not routed back to the agent who attempted the transfer. No: Includes the value assigned to the AgentID property and makes sure the first route attempt is to the agent with this login ID. For example, the qualification workflows use this option. LRMID $LRMid Script variable with the value retrieved by the Fetch LRMID block. Important: This script variable must be the same script variable assigned to the LRMID property of the Fetch LRMID block. Issue 3.0 July

62 Standard blocks Property Default Value Description PostQualification Action route Property with the following options available from the drop-down list: Transfer: Identifies the qualification attempt as a transfer. For example, use this option for the Transfer to Agent workflow. Route: Identifies the qualification attempt as a route. For example, use this option in qualification workflows for all channels and exception workflows. Qualifiers $qualifier_set Script variable with values from the Translate Category/Qualifier block. Important: This script variable must be the same script variable assigned to the Result property of the Translate Category/Qualifier block. RoutingHintSeq Couple start $RoutingHintSeq Couple Post Qualification Script variable with SeqCouple value from the Translate Category/Qualifier block. Important: This script variable must be the same script variable assigned to the scroutinginfo property of the Translate Category/Qualifier block. Block IC Script. Alarms Connections Generates no alarms. Accepts the following connections: Input: 1 or more Output: 1 Set Qualifier Description Sets values for up to four qualifier categories specified in the block, as follows: Combines the value for the CategoryName_N property with the value retrieved from the script variable that is the value of CategoryValue_N into a name/value pair, for example, "channel/voice". 62 Media Workflow Reference

63 Advocate palette Searches the global environment variable in the Workflow server that holds the list of qualifiers found by the advocate.update_qualifiersetids workflow for a qualifier that matches the name/value pair. If a match is found, saves the name/value pair in the sequence couple $scqualifiers that is assigned to the Qualifiers property. If no match is found, and a name/value pair has been assigned to DefaultValue_N, saves the name/value pair in the sequence couple $scqualifiers that is assigned to the Qualifiers property. You can place this block after a Map to Qualifier block, or as a standalone block. If you place the block after a Map to Qualifier block, Set Qualifier retrieves the qualifier values from the Map to Qualifier block. If you use Set Qualifier as a standalone block, the workflow must include a block that provides Set Qualifier with the values for CategoryValue_N. Prerequisites Example Set Qualifier requires: To access the block properties, import the qualifiers.txt file from Business Advocate Supervisor. For more information, see IC Business Advocate Configuration and Administration. To run a workflow that includes the Set Qualifier block, configure the Workflow server to use the advocate.update_qualifiersetids workflow as a synchronous startup flow. For example, to use Set Qualifier to set the language qualifier and customer type qualifier for a contact: 1. Add two Map to Qualifier blocks earlier in the workflow that map values for the qualifiers into the following script variables: Language qualifier value maps to $language Customer type qualifier value maps to $customertype 2. Configure the following properties of the Set Qualifier block: CategoryName_1 with value of language CategoryValue_1 with value of $language CategoryName_2 with value of customertype CategoryValue_2 with value of $customertype DefaultValue_1 with value of language/english DefaultValue_2 with value of customertype/new With this example, if the script variable $language contains the value russian, and Business Advocate does not have a qualifier of language/russian, the Set Qualifier blocks automatically sets the value of the language qualifier to language/english. Issue 3.0 July

64 Standard blocks Sample workflow Basic properties For an example of how this block can be used in a flow, see Qualify Voice flow for Business Advocate on page 263 and Qualify Chat flow for Business Advocate on page 271. The Basic tab of Set Qualifier includes the properties in the following table. Property Default Value Description CategoryName_N empty CategoryName_1 is mandatory. Up to four qualifier categories. Each category must map to the script variable that is the value of the equivalent CategoryValue_N. For example, to map language qualifiers, if the value of CategoryName_1 is language, assign a value of $language to CategoryValue_1. CategoryValue_N empty CategoryValue_1 is mandatory. Up to four values. Each value must map to the equivalent CategoryName_N. For example, to map language qualifiers, if the value of CategoryValue_1 is $language, then assign a value of language to CategoryName_1. DefaultValue_N empty Optional. Up to four values. Each value must be a default qualifier for the equivalent CategoryName_N. For example, to make English the default value of the language qualifier, assign the value of language to CategoryName_N, and a value of language/english to DefaultValue_1. 64 Media Workflow Reference

65 Advocate palette Advanced properties The Advanced tab of Set Qualifier includes the properties in the following table. Property Default Value Description blockdebug on Debug level of the block. Before changing the default value, see Block debug property on page 327. Qualifiers empty Script variable with the qualifiers set by this block. Important: This script variable must be the same script variable assigned to the Qualifiers properties of the Translate Category/Qualifier block. start Set Qualifier Block IC Script. Alarms Generates the alarm in the following table. Alarm Description Troubleshooting Could not match Advocate Qualifier. Looking for: category/qualifier. An INFO alarm that is generated if a concatenation of CategoryName_N and CategoryValue_N yields an unknown Advocate category/qualifier pair. This alarm typically indicates that the logic of the workflow creates category/qualifier pairs that you did not intend to create. To correct the error, do one of the following: Change the values for CategoryName_N and CategoryValue_N. Add the category/qualifier pair to the list of qualifiers in Business Advocate. Connections Accepts the following connections: Input: 1 or more Output: 1 Set Voice Wait Treatment Description For voice contacts only, sets the wait treatment style so the switch knows which wait treatment to play for the customer, while that customer waits to speak to an agent. This block: Retrieves the value of the intent qualifier associated with the voice contact. Assigns the specified wait treatment for that intent value to the voice contact. Issue 3.0 July

66 Standard blocks If no wait treatment is specified for that intent value, assigns the value of DefaultWaitTreatment to the voice contact. To set the wait treatment for chat contacts, see Set Chat Wait Treatment on page contacts do not have a wait treatment. Prerequisites Sample workflow Basic properties This block has the following prerequisites: Set the values for the wait treatment styles as constants in the project Symbol Dictionary. The values for these constants can be a literal numeric value that the switch understands. For more information about constants and the Symbol Dictionary, see Using properties and symbols on page 300. Place this block before the Translate Category/Qualifier block and Post Qualification block in the workflow. For an example of how this block can be used in a flow, see Qualify Voice flow for Business Advocate on page 263. The Basic tab of Set Voice Wait Treatment includes the properties in the following table. Property Default Value Description Criteria_N DefaultWaitTreat ment 1: sales 2: support $WT_TRANSFER Up to four intent values. Each intent value must map to the equivalent WaitTreatment_N property. The wait treatment to play for customers if the intent of the contact does not match one of the values in Criteria_N. The value can be a literal numeric value that the switch understands. Source $intent Mandatory. Script variable that holds the value of the intent qualifier. The value of Source should be the same script variable used in the Set Qualifier block that sets the intent qualifier. If necessary, you can use a different script variable to determine wait treatment. However, that script variable must be the same variable set by a Set Qualifier block. 66 Media Workflow Reference

67 Advocate palette Property Default Value Description Target WaitTreatment_N $waittreatment style 1. WT_STYLE_ O8 2. WT_STYLE_ 09 Mandatory. Script variable that holds the result of this block. The value of Target can be NULL. The value assigned to Target must be the same as the value of the WaitTreatmentStyle property in the Post Qualification block. Up to four wait treatment styles. Each wait treatment style must map to the equivalent Criteria_N property. You set wait treatment styles in constant script variables defined within the workflow project. To find the constants, select any value that begins with $WT_ from the drop-down list. Use the Symbol Dictionary to view or change values for the constants. Advanced properties The Advanced tab of Set Voice Wait Treatment includes the properties in the following table. Property Default Value Description blockdebug on Debug level of the block. Before changing the default value, see Block debug property on page 327. start Set Voice Wait Treatment Block IC Script. Alarms Connections Generates no alarms. Accepts the following connections: Input: 1 or more Output: 1 Issue 3.0 July

68 Standard blocks Translate Category/Qualifier Description Prerequisites Sample workflow Collects all of the qualifiers set by all of the Set Qualifier blocks in the workflow. How this block functions depends upon whether the block is part of a qualification workflow or an exception workflow. In a qualification workflow, this block: 1. Transforms the collection of qualifiers in name value pairs to a text string that contains the numeric representations for these qualifiers in ascending order. 2. Assigns the text string to the script variable that is the value of the Result property for use by the Post Qualification block. 3. Starts to build a new sequence couple for routing hints that contains information about the current routing attempt. 4. Uses the value of the VoiceContainer property to determine whether to create a new advocate container (VoiceContainer = 0) in the EDU or a new routinginfo container (VoiceContainer > 0) in the current advocate container. 5. Adds the field qualifiers to the container in the EDU. In an exception workflow, this block also: 1. Uses the LastQualifiers property to access the qualifiers set in the previous route attempt. 2. If the route to a preferred agent failed, removes the value of preferredagent criteria from the route attempt, but retains the other qualifiers from failed route attempt. This block has the following prerequisites: The value of the Qualifiers property of Translate Category/Qualifier must be the same script variable used in the Qualifiers property of the Set Qualifier block. This script variable contains the collection of qualifiers set in the workflow. The workflow must also contain the following blocks: Post Qualification Set Qualifier Get Input Parameters For an example of how this block can be used in a qualification flow, see Qualify Voice flow for Business Advocate on page Media Workflow Reference

69 Advocate palette Basic properties The Basic tab of Translate Category/Qualifier includes the properties in the following table. Property Default Value Description Qualifiers $scqualifiers Mandatory. Script variable with the collection of qualifiers set in the workflow. Important: This script variable must be the same script variable assigned to the Qualifiers property of the Set Qualifier block. Result $qualifier_set Mandatory. Script variable that contains the numerical representation of the qualifiers. This block writes data to this property. scroutinginfo $RoutingHintSeq Couple Mandatory. Script variable that contains the current routinginfo container that the block builds for insertion into the EDU. This block writes data to this property. This script variable must be passed to the Post Qualification block. VoiceContainer $VoiceContainer Mandatory. Script variable that contains the advocatecontainerindex value. The Get Input Parameters block parses and inputs this value into the workflow. Issue 3.0 July

70 Standard blocks Advanced properties The Advanced tab of Translate Category/Qualifier includes the properties in the following table. Property Default Value Description blockdebug on Debug level of the block. Before changing the default value, see Block debug property on page 327. LastQualifiers empty For exception workflows, this Script variable contains the qualifier set from the failed routing attempt. In an exception workflow, Fetch Last RoutingInfo and Get Values (RoutingInfo) blocks.extract this qualifier set. This script variable must match the script variable in those blocks. start Translate Category/ Qualifier Block IC Script. Alarms Connections Generates no alarms. Accepts the following connections: Input: 1 or more Output: 1 70 Media Workflow Reference

71 Application palette Application palette The Application palette contains blocks that retrieve and store data in a relational database. Some of these blocks are used in workflows that qualify and route contacts for all media. Other blocks are primarily used in agent script workflows. For more information about agent script workflows, see Agent Script Workflow Reference. This section includes the following topics which describe the blocks on the Application palette which are frequently used in media workflows: Create Record on page 71. Fetch Customer Record on page 72. Get Record Value(s) on page 74. Table Clear on page 75. Table Search on page 76. Create Record Description Basic properties Creates a database record and populates the database table. The Basic tab of Create Record includes the properties in the following table. Property Default Value Description Field_N empty Field in the database table where the block should enter a value. You can specify up to 10 fields. Tablename empty Mandatory. Database table where the block will create the record. Note: This table must belong to the DBNetwork of the Start block. For more information, see Start on page 117. Value_N empty Values that the block should enter in the associated Field_N property. Issue 3.0 July

72 Standard blocks Advanced properties The Advanced tab of Create Record includes the properties in the following table. Property Default Value Description blockdebug off Debug level of the block. Before changing the default value, see Block debug property on page 327. RecordKey $RecordKey After the record is created in the database table, this variable holds the pkey for the record. start CreateRecord Block IC Script. Alarms Connections Generates no alarms. Accepts the following connections: Input: 1 or more Output: 1 Fetch Customer Record Description Searches the Customer table of the CCQ database for a record that matches the specified value of the specified field. If a record is found: 1. Fetches the Customer record. 2. Sets a NumRecords value for the number of records that match the search criteria. 3. If NumRecords value matches the specified value of 1, retrieves the values from the Customer record. 4. Stores all values found in the customerinfo container and stores the pkey of the Customer record value into the customerid field in the EDU. 5. Sets the customer_fetched field in the EDU to either true or false, depending upon whether the query was successful or not. A value in this field of either true or false indicates that the query has already been run on the contact. You can specify up to ten fields and values on the Basic tab. These values must correspond to a field in the Customer table. 72 Media Workflow Reference

73 Application palette Basic properties The Basic tab of Fetch Customer Record includes the properties in the following table. Property Default Value Description Field_N empty Field in the Customer table from which the block should retrieve data. You can specify up to 10 fields. Value_N empty Target where the block should store values retrieved from the Customer table. The value can be a sequence of couples or script variable. Advanced properties The Advanced tab of Fetch Customer Record includes the properties in the following table. Property Default Value Description blockdebug off Debug level of the block. Before changing the default value, see Block debug property on page 327. CustData $sccustdata A sequence couple that contains the Customer record. NumRecords $RecordCount Number of records that should match the search criteria. If not otherwise specified, value is assumed to be 1. start Fetch Customer Record Block IC Script. Alarms Connections Generates no alarms. Accepts the following connections: Input: 1 or more Output: 1 Issue 3.0 July

74 Standard blocks Get Record Value(s) Description Basic properties Retrieves the values of the specified fields from a database table. You can specify the number of record for which the values must be retrieved from the table. By default, the values of the first record are retrieved. The Basic tab of Get Record Value(s) includes the properties in the following table. Property Default Value Description Field_N empty Field in the database table where the block should retrieve values. You can specify up to 10 fields. RecordNumber 0 Identifying number of the record to be retrieved from each field. The default of 0 retrieves the first record. Tablename empty Mandatory. Database table in the DBnetwork of the Start block where the block will retrieve the record values. Note: This table must belong to the DBNetwork of the Start block. For more information, see Start on page 117. Target_N $ChangeMe Target where the block should store values retrieved from the associated Field_N. For example, if you specify a database field in Field_1, enter the target for the data in Target_1 Advanced properties The Advanced tab of Get Record Value(s) includes the properties in the following table. Property Default Value Description blockdebug off Debug level of the block. Before changing the default value, see Block debug property on page 327. start Get Record Values Block IC Script. 74 Media Workflow Reference

75 Application palette Alarms Connections Generates no alarms. Accepts the following connections: Input: 1 or more Output: 1 Table Clear Description Basic properties Clears the data from the previous database search. The Basic tab of Table Clear includes the properties in the following table. Property Default Value Description Tablename empty Mandatory. Database table in the DBnetwork of the Start block where the block will clear data. Note: This table must belong to the DBNetwork of the Start block. For more information, see Start on page 117. Advanced properties The Advanced tab of Table Clear includes the properties in the following table. Property Default Value Description blockdebug off Debug level of the block. Before changing the default value, see Block debug property on page 327. start Table Clear Block IC Script. Alarms Connections Generates no alarms. Accepts the following connections: Input: 1 or more Output: 1 Issue 3.0 July

76 Standard blocks Table Search Description Basic properties Searches a relational database table using the Query by Example type of search. For details on the types of searches that are available, see IC Scripts Language Reference. The Basic tab of Table Search includes the properties in the following table. Property Default Value Description Field_N empty Name of the field in the database table where the block should search for values. You can specify up to 10 fields. Tablename empty Mandatory. Database table where the block will search for the record. Note: This table must belong to the DBNetwork of the Start block. For more information, see Start on page 117. Value_N empty Value to search for in the associated Field_N. For example, if you specify a database field in Field_1, enter the value that the block should retrieve from that field in Value_N. Advanced properties The Advanced tab of Table Search includes the properties in the following table. Property Default Value Description blockdebug off Debug level of the block. Before changing the default value, see Block debug property on page 327. ClearTable yes Clears the data from the previous database search. RecordCount $RecordCount Number of records found in the specified database fields with the specified values. 76 Media Workflow Reference

77 Application palette Property Default Value Description RecordKey $RecordKey If only one record is found with the specified values, holds the pkey for that record. If more than one record is found, or no records are found, script variable is empty. start Table Search Block IC Script. Alarms Connections Generates no alarms. Accepts the following connections: Input: 1 or more Output: 1 Issue 3.0 July

78 Standard blocks Content Analysis palette The Content Analysis palette contains blocks that are typically used in Analysis flows for Avaya IC systems that include Content Analyzer. For more information, see Analysis flows on page 189. This section includes the following topics which describe those blocks: Get Language on page 78. Get Matched Category on page 79. QA Outbound (QA Category) on page 81. Test Category on page 82. Get Language Description Prerequisites Sample workflow Basic properties Analyzes the text in the specified field of an contact to determine the language of the contact through Content Analyzer. This block also sets a routing hint for the language in the $language script variable. To use this block, you must define this variable as a script variable available to the entire workflow. For an example of how Get Language can be used in a workflow, see Analyze with Content Analyzer flow on page 214. The Basic tab of Get Language includes the properties in the following table. Property Default Value Description FieldToAnalyze $msgbody Script variable that holds a field in the contact. The block uses this variable to tell Content Analyzer which field to analyze for language. By default, the block uses the name of the script variable that holds the body. Server $ChangeMe Server alias name for the CA Operational server in IC Manager. Important: Do not specify the alias for the CA Admin server. 78 Media Workflow Reference

79 Content Analysis palette Advanced properties The Advanced tab of Get Language includes the properties in the following table. Property Default Value Description blockdebug off Debug level of the block. Before changing the default value, see Block debug property on page 327. DefaultLanguage en Two character ISO language code to be used for language if Content Analyzer does not return a value. The default value is en for English. start Get Language Block IC Script. Alarms Connections Generates no alarms. Accepts the following connections: Input: 1 or more Output: 1 Get Matched Category Description Sample workflow Analyzes the specified field in an contact, retrieves a collection of categories and corresponding scores, then saves the results in the ca_result table of the CCQ database. For an example of how Get Matched Category can be used in a workflow, see Analyze with Content Analyzer flow on page 214. Issue 3.0 July

80 Standard blocks Basic properties The Basic tab of Get Matched Category includes the properties in the following table. Property Default Value Description DefaultLanguage en Two character ISO language code to be used for language if Content Analyzer does not return a value. The default value is en for English. FieldToAnalyze $msgbody Script variable that holds a field in the contact. The block uses this variable to tell Content Analyzer which field to analyze for matched categories. By default, the block uses the name of the script variable that holds the body. KBName $ChangeMe Name of the Content Analyzer knowledge base to use to find categories. MatchThreshold 50 Minimum score value to return for matches. This value overrides the threshold value set in the Content Analyzer servers. MaxHits 5 Maximum number of categories to return. Server $ChangeMe Server alias name for the CA Operational server in IC Manager. Important: Do not specify the alias for the CA Admin server. Advanced properties The Advanced tab of Get Matched Category includes the properties in the following table. Property Default Value Description blockdebug off Debug level of the block. Before changing the default value, see Block debug property on page 327. start Get Matched Category Block IC Script. TopicList $ssctopiclist Script variable to hold results returned by Content Analyzer. This variable is also used by Test Category on page Media Workflow Reference

81 Content Analysis palette Alarms Connections Generates no alarms. Accepts the following connections: Input: 1 or more Output: 1 QA Outbound (QA Category) Description Sample workflow Basic properties Attempts to match the specified field in the with the one or more category and score pairs. If there is a match, sets the script variable qaforcategory to true. Saves the results to the ca_results table. For an example of how QA Category can be used in a workflow, see Outbound with Content Analyzer flow on page 224. The Basic tab of QA Category includes the properties in the following table. Property Default Value Description CategoryNameTo Match_N $ChangeMe Category to match with the field of the specified in the FieldToAnalyze property. Must be in the following form: TopicTreeName::LL:Category where: TopicTreeName is the name of the topic tree associated with KBName. LL is the 2 character language code which can be left empty. Category is the dot separated category to match. CategoryScore_N 0 CategoryScore_01 is mandatory to give a score for CategoryNameToMatch_01. Score to assign to the associated category. FieldToAnalyze $msgbody Script variable that holds a field in the contact. The block uses this variable to tell Content Analyzer which field to analyze for matched categories. By default, the block uses the name of the script variable that holds the body Issue 3.0 July

82 Standard blocks Property Default Value Description KBName $ChangeMe Name of the Content Analyzer knowledge base to use to find categories. Server $ChangeMe Server alias name for the CA Operational server in IC Manager. Important: Do not specify the alias for the CA Admin server. Advanced properties The Advanced tab of QA Category includes the properties in the following table. Property Default Value Description blockdebug off Debug level of the block. Before changing the default value, see Block debug property on page 327. DefaultLanguage en Two character ISO language code to be used for language if Content Analyzer does not return a value. The default value is en for English. start QA Category Block IC Script. TopicList $ssctopiclist Script variable to hold results returned by Content Analyzer. Alarms Connections Generates no alarms. Accepts the following connections: Input: 1 or more Output: 1 Test Category Description Prerequisites Searches the results returned by a Get Matched Category block for a particular category and score. This block must be preceded by a Get Matched Category block in the workflow. 82 Media Workflow Reference

83 Content Analysis palette Sample workflow Basic properties For an example of how Test Category can be used in a workflow, see Analyze with Content Analyzer flow on page 214. The Basic tab of Test Category includes the properties in the following table. Property Default Value Description CategoryList $ssctopiclist Name of script variable that holds content analysis results. This value must match the value entered in the TopicList property on the Advanced tab of the Get Matched Category block. CategoryTo Compare Home computing Content analysis category to search for in the script variable. This value must be identical to a topic in the topic tree. ScoreOperator >= Operator to use in the comparison. Use one of the following operators from the drop-down list: < for a match that is less than the ScoreToCompare <= for a match that is less than or equal to the ScoreToCompare <> for a match that is less than or greater than the ScoreToCompare = for a match that is equal to the ScoreToCompare > for a match that is greater than the ScoreToCompare >= for a match that is greater than or equal to the ScoreToCompare ScoreToCompare 97 Score value to use in the comparison. Example For example, if you want a particular category, regardless of the score, set the following values in the Basic tab: ScoreToCompare to 0 ScoreOperator to = CategoryToCompare to the desired category Issue 3.0 July

84 Standard blocks Advanced properties The Advanced tab of Test Category includes the properties in the following table. Property Default Value Description blockdebug off Debug level of the block. Before changing the default value, see Block debug property on page 327. start Test Category Block IC Script. Alarms Connections Generates no alarms. Has two named output connections: Yes: If the condition is satisfied, the workflow continues along the Yes connection. No: If the condition is not satisfied, the workflow continues along the No connection. Test Category accepts 1 or more input connections. 84 Media Workflow Reference

85 EDU palette EDU palette The EDU palette contains blocks that are typically used in media workflows that include EDUs, such as qualification workflows for contacts. This section includes the following topics which describe those blocks: Create EDU on page 85. Delete EDU Data on page 87. Fetch EDU on page 88. Get EDU Values on page 89. Set EDU on page 90. Test EDU Data on page 91. Write EDU on page 93. Create EDU Description Requests the EDU server to create a new record by issuing the method VDU.Create. With Create EDU, you can: Enter up to 10 initial names and values. Populate the EDU with these couples. Populate the EDU with couples that are set by any Set EDU blocks that precede this block and follow an earlier Create EDU block or an earlier Write EDU block. By default the request is sent to server EDU, passing Script variable newvdudata and storing the returned EDUID in Script variable vdu_id. You can modify these settings in the advanced properties. Create EDU clears the newvdudata sequence upon completion. Advanced properties allow automatic EDU termination if desired. Issue 3.0 July

86 Standard blocks Basic properties The Basic tab of Create EDU includes the properties in the following table. Property Default Value Description name_n empty Name of a field in the EDU. You can specify up to 10 names. value_n empty Value of the field in the EDU. For example, if you specify the name of an EDU field in name_10, enter the value of the field in value_10. Advanced properties The Advanced tab of Create EDU includes the properties in the following table. Property Default Value Description blockdebug off Debug level of the block. Before changing the default value, see Block debug property on page 327. maxdebuglength Maximum debug output length. For more information, see Avaya Workflow Designer User Guide. newvdudata $newvdudata Script variable where sequence of couples returned by EDU server is stored. servername VDU Name of the EDU server. start Create EDU Block IC Script. vdu_id $vdu_id Script variable obtained from event or method that invokes the workflow. vduterminate on If set to on, terminates the EDU. vdutouched true If set to true, lets you terminate the EDU. Alarms Connections Create EDU generates an alarm (QWorkflow.CreateVduError) if an EDUID is not returned. Accepts the following connections: Input: 1 or more Output: 1 86 Media Workflow Reference

87 EDU palette Delete EDU Data Description Basic properties Requests the EDU server to remove values from couples in an EDU record by issuing the method VDU.DeleteValues. You can enter up to 10 names of couples to delete. By default the request is sent to server EDU, passing Script variable vdu_id. If vdu_id is empty, the block tries to fill it from the data that arrived with the event or method that started this flow. It passes the sequence of strings containing names of couples to delete in Script variable deletevdudata. You can modify these settings in the advanced properties. Delete EDU Data clears the deletevdudata sequence upon completion. Advanced properties allow automatic EDU termination if desired. The Basic tab of Delete EDU Data includes the properties in the following table. Property Default Value Description name_n empty Name of a field in the EDU where you want to delete data. You can specify up to 10 names. Advanced properties The Advanced tab of Delete EDU Data includes the properties in the following table. Property Default Value Description blockdebug off Debug level of the block. Before changing the default value, see Block debug property on page 327. deletevdudata $deletevdu Data Script variable where sequence of couples returned by EDU server is stored. servername VDU Name of the EDU server. start Delete EDU Block IC Script. vdu_id $vdu_id Script variable obtained from event or method that invokes the workflow. vduterminate on If set to on, terminates the EDU. vdutouched true If set to true, lets you terminate the EDU. Issue 3.0 July

88 Standard blocks Alarms Connections Delete EDU Data generates an alarm (QWorkflow.DeleteVduError) if no EDUID can be determined. Accepts the following connections: Input: 1 or more Output: 1 Fetch EDU Description Sample workflow Basic properties Advanced properties Retrieves a record from the EDU server by issuing the method VDU.GetValues. By default the request is sent to server EDU, passing Script variable vdu_id. If vdu_id is empty, the block tries to fill it from the data that arrived with the event or method that started this flow. It stores the returned sequence of couples in Script variable vdudata. You can modify these settings in the advanced properties. Advanced properties allow automatic EDU termination if desired. For an example of how Fetch EDU can be used in a workflow, see Incoming Call flow on page 153. The Basic tab of Fetch EDU does not have any properties. The Advanced tab of Fetch EDU includes the properties in the following table. Property Default Value Description blockdebug off Debug level of the block. Before changing the default value, see Block debug property on page 327. maxdebuglength Maximum debug output length. For more information, see Avaya Workflow Designer User Guide. servername VDU Name of the EDU server. start Fetch EDU Block IC Script. vdu_id $vdu_id Script variable obtained from event or method that invokes the workflow. VduData $VduData Script variable where sequence of couples returned by EDU server is stored. 88 Media Workflow Reference

89 EDU palette Property Default Value Description vduterminate on If set to on, terminates the EDU. vdutouched true If set to true, lets you terminate the EDU. Alarms Connections Fetch EDU generates an alarm (QWorkflow.FetchVduError) if no EDUID can be determined, or if the request returns no data. Accepts the following connections: Input: 1 or more Output: 1 Get EDU Values Description Assigns the value of individual attributes of the EDU stored in the Script variable vdudata when the Fetch EDU block is used.! CAUTION: CAUTION: Use this block only when the number of EDU attributes that have to be assigned to Script variables increases as the workflow performs time critical functions, such as routing of calls in a large contact center. In such an environment, use a simple assignment statement with the method FindValue() on the IDL Data Object vdudata. Sample workflow Basic properties For an example of how Get EDU Values can be used in a workflow, see Incoming Call flow on page 153. The Basic tab of Get EDU Values includes the properties in the following table. Property Default Value Description Field_N empty Field in the EDU from which the block should retrieve data. You can specify up to 10 fields. Target_N $ChangeMe Target where the block should store values retrieved from the EDU field. For example, if you specify an EDU field in Field_10, enter the target for the data in Target_10. Issue 3.0 July

90 Standard blocks Advanced properties The Advanced tab of Get EDU Values includes the properties in the following table. Property Default Value Description blockdebug off Debug level of the block. Before changing the default value, see Block debug property on page 327. start Get ADU Block IC Script. Values vdudata $vdu_data Script variable where sequence of couples returned by the EDU server is stored. Alarms Connections Generates no alarms. Accepts the following connections: Input: 1 or more Output: 1 Set EDU Description Basic properties Assigns values to EDU couples for later storage in the EDU record. You can fill in up to 10 names and 10 values, which are added to a sequence of couples. This sequence may be written to the EDU server at a later time by a Write EDU block or Create EDU block. You can use multiple Set EDU blocks to add additional settings to the sequence before writing to the EDU. This block calls no external methods. By default this block adds couples to Script variable newvdudata. You can modify this variable using the block.s advanced properties. The Basic tab of Set EDU includes the properties in the following table. Property Default Value Description name_n empty Name of a field in the EDU. You can specify up to 10 names. value_n empty Value of the field in the EDU. For example, if you specify the name of an EDU field in name_10, enter the value of the field in value_ Media Workflow Reference

91 EDU palette Advanced properties The Advanced tab of Set EDU includes the properties in the following table. Property Default Value Description blockdebug off Debug level of the block. Before changing the default value, see Block debug property on page 327. newvdudata $newvdudata Script variable where sequence of couples returned by the EDU server is stored. start Set EDU Block IC Script. Alarms Connections Generates no alarms. Accepts the following connections: Input: 1 or more Output: 1 Test EDU Data Description Prerequisites Tests the value of an EDU data element and branches the workflow based on the result. You specify the EDU element to test, the type of test, the value to test against, and the mode of comparison. This block looks for the specified couple in the sequence of couples in Script variable vdudata. You can modify this setting in the advanced properties. This block is typically effective only when preceded by a Fetch EDU block. Issue 3.0 July

92 Standard blocks Basic properties The Basic tab of Test EDU Data includes the properties in the following table. Property Default Value Description comparisonmode alphanumeric Mode used to compare the value of the EDU data element against the specified value. Options are alphanumeric and numeric. operator = Operator to use in the test. Use one of the following operators from the dropdown list: < for a match that is less than the value <= for a match that is less than or equal to the value <> for a match that is less than or greater than the value = for a match that is equal to the value > for a match that is greater than the value >= for a match that is greater than or equal to the value exists for a match that shows only that the value exists in the EDU data element. value 97 Value to use in the comparison with the value of the EDU data element. vduelement empty Element of the EDU that you want to test. Advanced properties The Advanced tab of Test EDU Data includes the properties in the following table. Property Default Value Description blockdebug off Debug level of the block. Before changing the default value, see Block debug property on page 327. start Get ADU Values Block IC Script. vdudata $vdu_data Script variable where sequence of couples returned by the EDU server is stored. 92 Media Workflow Reference

93 EDU palette Alarms Connections Generates no alarms. Has two named output connections: Yes: If the condition is satisfied, the workflow continues along the Yes connection. No: If the condition is not satisfied, the workflow continues along the No connection. Test EDU accepts 1 or more input connections. Write EDU Description Sample workflow Basic properties Advanced properties Writes a record to a field in the EDU by issuing the method VDU.SetValues. The values it sends are typically set by preceding Set EDU blocks. By default the request is sent to server EDU, passing Script variable vdu_id. If vdu_id is empty, the block tries to fill it from the data that arrived with the event or method that started this flow. It passes the sequence of couples in Script variable newvdudata. You can modify these settings through the block.s advanced properties. Advanced properties allow automatic EDU termination, if desired. For an example of how Write EDU can be used in a workflow, see IV Chat flow on page 173. The Basic tab of Write EDU does not have any properties. The Advanced tab of Write EDU includes the properties in the following table. Property Default Value Description blockdebug off Debug level of the block. Before changing the default value, see Block debug property on page 327. maxdebuglength Maximum debug output length. For more information, see Avaya Workflow Designer User Guide. newvdudata $deletevdu Data Script variable where sequence of couples returned by EDU server is stored. servername VDU Name of the EDU server. start Write EDU Block IC Script. Issue 3.0 July

94 Standard blocks Property Default Value Description vdu_id $vdu_id Script variable obtained from event or method that invokes the workflow. vduterminate on If set to on, terminates the EDU. vdutouched true If set to true, lets you terminate the EDU. Alarms Connections Write EDU generates an alarm (QWorkflow.WriteVduError) if no EDUID can be determined. Accepts the following connections: Input: 1 or more Output: 1 94 Media Workflow Reference

95 palette palette The palette contains the following blocks that are typically used in Analysis flows and qualification workflows for contacts. For more information, see Analysis flows on page 189 and contact routing flows on page 179. This section includes the following topics which describe those blocks: Add Component on page 95. Auto Response on page 97 Bounce on page 98. Dismiss on page 99. Get Agent Quota on page 100. Get Suggested Response on page 101. IC Analyzed on page 103. IC Outbound Response on page 103. Route on page 104. Set Alert on page 105. Smart Auto Ack on page 106. Add Component Description Sample workflow Specifies attachments and additional recipients for the outbound contact. If you want to add more than one address to a field in the outbound , separate the addresses with semicolons. If you want to include multiple file attachments, separate the directory path and file names of the attachments with semicolons. For an example of how Add Component can be used in a workflow, see Outbound with Keywords flow on page 207. Issue 3.0 July

96 Standard blocks Basic properties The Basic tab of Add Component includes the properties in the following table. Property Default Value Description BCC Addresses empty Adds these addresses to the BCC field of the outbound . CC Addresses $cc addres ses Adds these addresses to the CC field of the outbound . FileAttachments $fileattachments Adds these attachments to the outbound . To include an attachment: Store the file on the machine that hosts the Workflow server. Specify the full directory path of each file. To Addresses empty Adds these addresses to the To field of the outbound . Advanced properties The Advanced tab of Add Component includes the properties in the following table. Property Default Value Description blockdebug off Debug level of the block. Before changing the default value, see Block debug property on page 327. start Add Component Block IC Script. Alarms Connections Generates no alarms. Accepts the following connections: Input: 1 or more Output: 1 96 Media Workflow Reference

97 palette Auto Response Description Sample workflow Prerequisites Basic properties Sets a route disposition of Auto Response, then specifies the content to include in the subject line and text of the reply. For an example of how Auto Response can be used in a workflow, see Analyze with Content Analyzer flow on page 214. To use this block, you must set a value for either ResolveWithText or TemplateName. If you set values for both of those properties, Avaya IC uses the value for TemplateName and ignores the value for ResolveWithText. The Basic tab of Auto Response includes the properties in the following table. Property Default Value Description ForwardAddress empty An address that should receive a copy of the automatic response returned to the sender. This property is optional. ResolveWithText empty Text to use in the Auto Response. Note: If you use this property, you cannot use TemplateName. TemplateName empty Name of the Response Template to use. Note: If you use this property, you cannot use ResolveWithText. Advanced properties The Advanced tab of Auto Response includes the properties in the following table. Property Default Value Description blockdebug off Debug level of the block. Before changing the default value, see Block debug property on page 327. DefaultEncoding empty Default language encoding to use for the response template. DefaultLanguage empty Two character ISO language code to be used for language. For example, en for English. start Auto Response Block IC Script. Issue 3.0 July

98 Standard blocks Alarms Connections Generates no alarms. Accepts the following connections: Input: 1 or more Output: 1 Bounce Description Sample workflow Basic properties Sets a route disposition of Bounce for contacts, then specifies the reason for the bounce. When a workflow sends an contact to a Bounce block, the workflow notifies the IC server that the contact needs to be returned to the sender. For an example of how Bounce can be used in a workflow, see Analyze with Keywords flow on page 196. The Basic tab of Bounce includes the properties in the following table. Property Default Value Description BounceReason 1 Status ID that represents a reason to include in the text, such as "no such recipient". ForwardAddress empty An address that should receive a copy of the bounce message returned to the sender. This property is optional. TemplateName empty Name of the Response Template to use. Advanced properties The Advanced tab of Bounce includes the properties in the following table. Property Default Value Description blockdebug off Debug level of the block. Before changing the default value, see Block debug property on page 327. start Bounce Block IC Script. 98 Media Workflow Reference

99 palette Alarms Connections Generates no alarms. Accepts the following connections: Input: 1 or more Output: 1 Dismiss Description Sample workflow Basic properties Sets a route disposition of Dismiss for an contact, then specifies the reason that the contact is dismissed. When a workflow sends an contact to a Dismiss block, the workflow notifies the IC server that the contact does not need to be handled by an agent. For an example of how Dismiss can be used in a workflow, see Analyze with Keywords flow on page 196. The Basic tab of Dismiss includes the properties in the following table. Property Default Value Description ResolveWithStatus 1 Status ID that represents a reason to include in the text, such as "no such recipient". ForwardAddress empty An address that should receive a copy of the dismiss message returned to the sender. This property is optional. Advanced properties The Advanced tab of Dismiss includes the properties in the following table. Property Default Value Description blockdebug off Debug level of the block. Before changing the default value, see Block debug property on page 327. RouteResponseTo IntendedAgent false start Dismiss Block IC Script. If the original contact is addressed to a specific agent, whether the agent should receive a copy of the dismiss message. Issue 3.0 July

100 Standard blocks Alarms Connections Generates no alarms. Accepts the following connections: Input: 1 or more Output: 1 Get Agent Quota Description Sample workflow Basic properties Retrieves the value of the ReviewQuota property from the agent.s profile, then saves the value in the script variable qaquotavalue. If there is no value, uses the value in the DefaultQuotaValue property of this block. This block then generates a random number between 1 and 100, then saves the value in the script variable currentquotascore. For an example of how Get Agent Quota can be used in a workflow, see Outbound with Keywords flow on page 207. The Basic tab of Get Agent Quota includes the properties in the following table. Property Default Value Description DefaultQuotaValue 0 Default quota value to use if none is found for the agent. Property ReviewQuota Value must be ReviewQuota for this block to fetch the correct value. PropertySection /Agent Value must be /Agent for this block to fetch the correct value. Advanced properties The Advanced tab of Get Agent Quota includes the properties in the following table. Property Default Value Description blockdebug off Debug level of the block. Before changing the default value, see Block debug property on page 327. start Get Agent Quota Block IC Script. 100 Media Workflow Reference

101 palette Alarms Connections Generates no alarms. Accepts the following connections: Input: 1 or more Output: 1 Get Suggested Response Description Sample workflow Basic properties Queries Web Self-Service with the keywords for suggested responses on that subject. For an example of how Get Suggested Response can be used in a workflow, see Analyze with Keywords flow on page 196. The Basic tab of Get Suggested Response includes the properties in the following table. Property Default Value Description Language empty Language to use for the query. Must be a two character ISO language code. If you do not set this field, the block uses en for English. MaxDocs 5 Maximum number of suggested responses to return. MaxDocSize 1000 Maximum size in Kilobytes of the suggested responses to return. This property filters out responses that are larger than the maximum size. When this happens, the Alarm monitor displays an alarm, and the information is added to the WebACD server log file. MinScore 25 Minimum confidence score for all returned suggested responses. The query will not return any responses with a lower confidence score. Issue 3.0 July

102 Standard blocks Advanced properties The Advanced tab of Get Suggested Response includes the properties in the following table. Property Default Value Description AdditionalKeywords empty Additional keywords to use in the search. You can enter literals in this field. To include multiple keywords, use a space or a semi-colon as a delimiter. blockdebug off Debug level of the block. Before changing the default value, see Block debug property on page 327. start Get Suggested Block IC Script. Response TopicList $sscchangeme Script variable to hold results returned from the search for suggested responses. For example, enter $ssctopiclist. UseRoutingHints false Set to true if you want to use all of the routing hints gathered by the Set Routing Hints blocks earlier in the workflow as keywords. UseTopicListKey words UseTopicListTopic Path false false Set to true if you want to add the keywords assigned to the Content Analyzer categories in the Knowledge Base to the collection of keywords already identified by AdditionalKeywords, UseRoutingHints and UseTopicListTopicPath. Set to true if you want to add the Topic path assigned to the Content Analyzer categories in the Knowledge Base to the collection of keywords already identified by AdditionalKeywords, UseRoutingHints, and UseTopicListKeywords. Alarms Connections Generates no alarms. Accepts the following connections: Input: 1 or more Output: Media Workflow Reference

103 palette IC Analyzed Description Sample workflow Basic properties Advanced properties Saves the values from the $scroutinghints script variable into the qw_qualifier table, then invokes the IC .Analyzed method to notify the IC server that the flow is complete. For an example of how IC Analyzed can be used in a workflow, see Analyze with Keywords flow on page 196. The Basic tab of IC Analyzed does not have any properties. The Advanced tab of IC Analyzed includes the properties in the following table. Property Default Value Description blockdebug off Debug level of the block. Before changing the default value, see Block debug property on page 327. start IC Analyzed Block IC Script. Alarms Connections Generates no alarms. Accepts the following connections: Input: 1 or more Output: 1 IC Outbound Response Description Sample workflow Saves the values from the $scroutinghints script variable into the qw_qualifier table. Sets sendforapproval = true if any routing hints were actually set in the workflow. Invokes the IC .OutboundResponse method to notify the IC server that the outbound analysis flow is complete. For an example of how IC Outbound Response can be used in a workflow, see Outbound with Keywords flow on page 207. Issue 3.0 July

104 Standard blocks Basic properties Advanced properties The Basic tab of IC Outbound Response does not have any properties. The Advanced tab of IC Outbound Response includes the properties in the following table. Property Default Value Description blockdebug off Debug level of the block. Before changing the default value, see Block debug property on page 327. start IC Outbound Response Block IC Script. Alarms Connections Generates no alarms. Accepts the following connections: Input: 1 or more Output: 1 Route Description Sample workflow Basic properties Sets a route disposition of Route. For an example of how Route can be used in a workflow, see Analyze with Keywords flow on page 196. The Basic tab of Route includes the properties in the following table. Property Default Value Description ForwardAddress empty An address that should receive a copy of the contact. This property is optional. 104 Media Workflow Reference

105 palette Advanced properties The Advanced tab of Route includes the properties in the following table. Property Default Value Description blockdebug off Debug level of the block. Before changing the default value, see Block debug property on page 327. RouteResponseTo IntendedAgent false start Route Block IC Script. If you set the value of this property to true, the Route disposition overrides any previous setting of the routeresponsetoagent script variable set by the IC server. Alarms Connections Generates no alarms. Accepts the following connections: Input: 1 or more Output: 1 Set Alert Description Sample workflow Basic properties Sets an alert in the Notification server. For an example of how Set Alert can be used in a workflow, see Outbound with Keywords flow on page 207. The Basic tab of Set Alert includes the properties in the following table. Property Default Value Description DelayDuration HOUR The unit of time associated with the DelayLength. The drop-down list includes options for DAY, HOUR, and MINUTE. DelayLength 3 The length of the delay that the Notification server waits to send the alert. Issue 3.0 July

106 Standard blocks Advanced properties The Advanced tab of Set Alert includes the properties in the following table. Property Default Value Description blockdebug off Debug level of the block. Before changing the default value, see Block debug property on page 327. start Set Alert Block IC Script. vdudata $vdudata A sequence of couples that contains the contents of the current EDU. Set this value to the variable in the IC Script that contains the contents of the current EDU. Assign the same value as the vdudata property in a Get EDU Values block. Alarms Connections Generates no alarms. Accepts the following connections: Input: 1 or more Output: 1 Smart Auto Ack Description Sample workflow Performs the following tasks for the specified types: Specifies a response template for Auto Acknowledgement. Checks the response template and the language encoding of the contact against the qem_template table for a match. - If there is a match, sets the pkey of the record from the qem_template table in the EDU field rlm_pkey. - If there is no match, makes another attempt with the value specified in the DefaultEncoding property if that value is different. - If there is still no match, sets a default of 0. For an example of how Smart Auto Ack can be used in a workflow, see Analyze with Keywords flow on page Media Workflow Reference

107 palette Basic properties The Basic tab of Smart Auto Ack includes the properties in the following table. Property Default Value Description TemplateName empty Name of the Response Template to use. Advanced properties The Advanced tab of Smart Auto Ack includes the properties in the following table. Property Default Value Description blockdebug off Debug level of the block. Before changing the default value, see Block debug property on page 327. DefaultEncoding empty Default language encoding to use for the response template. DefaultLanguage en Two character ISO language code to be used for language. The default is en for English. start Smart Auto Ack Block IC Script. Alarms Connections Generates no alarms. Accepts the following connections: Input: 1 or more Output: 1 Issue 3.0 July

108 Standard blocks General palette The General palette contains the following: Blocks that can be used in any workflow Blocks that are typically used only in media workflows This section includes the following topics which describe those blocks: Comment on page 108. Config Parameter on page 109. Demo on page 110. Get Input Parameters on page 111. Initialize Global on page 112. On Exit on page 113. Raise Alarm on page 114. Set Output Parameters on page 115. Set Default Values on page 116. Start on page 117. Stop on page 118. Test Data on page 118. Comment Description Sample workflow Basic properties Advanced properties Alarms Connections Lets you place free-form comments in the Work Area of a workflow. This block is not compiled and does not affect workflow functionality. For an example of how Comment can be used in a workflow, see IV Chat flow on page 173. The Basic tab of Comment does not have any properties. The Advanced tab of Comment does not have any properties. Generates no alarms. Has no connections. 108 Media Workflow Reference

109 General palette Config Parameter Description Basic properties Adds a custom configuration parameter to the Workflow server. It is typically part of an initialization flow that runs at server startup, and allows the server to: Recognize a new configuration parameter entered in IC Manager. Verify and adjust the value. Store the value in the global sequence of couples for access from other blocks. Config Parameter invokes no external methods. The Basic tab of Config Parameter includes the properties in the following table. Property Default Value Description configname empty Name of the configuration parameter. default empty Default value for the configuration parameter. required no Whether the parameter is required. Advanced properties The Advanced tab of Config Parameter includes the properties in the following table. Property Default Value Description blockdebug off Debug level of the block. Before changing the default value, see Block debug property on page 327. comparisonmode alphanumeric Mode used to compare the value of the configuration parameter. Options are alphanumeric and numeric. limitrange no Whether to limit the range of the comparison. maximum empty Maximum value. minimum empty Minimum value. start Config Param Block IC Script. Alarms Config Parameter generates: A high-priority or emergency alarm (QWorkflow.ConfigParamError) if it cannot properly interpret the parameter setting entered in IC Manager. Issue 3.0 July

110 Standard blocks A low-priority alarm (QWorkflow.ConfigParamWarning) if it adjusts the value based on criteria specified in the properties. Connections Accepts the following connections: Input: 1 or more Output: 1 Demo Description Supports examples used in training courses and in the Avaya Workflow Designer User Guide. Important:! Important: Do not use this block in production workflows. Basic properties The Basic tab of Demo includes the properties in the following table. Property Default Value Description demoalarmpriority low Priority of the alarm raised by the block. demostring empty Text to be included in the alarm. Advanced properties The Advanced tab of Demo includes the properties in the following table. Property Default Value Description blockdebug off Debug level of the block. Before changing the default value, see Block debug property on page 327. start DemoBlock Block IC Script. Alarms Connections Demo issues an alarm for test purposes. Configure this alarm in the block properties. Accepts the following connections: Input: 1 or more Output: Media Workflow Reference

111 General palette Get Input Parameters Description Sample workflow Basic properties Finds the values of the input parameters sent by the method that invoked the flow and assigns the values to the Script variables. For an example of how Get Input Parameters can be used in a workflow, see Incoming Call flow on page 153. The Basic tab of Get Input Parameters includes the properties in the following table. Property Default Value Description Parameter_N empty Parameter that the block should retrieve. You can specify up to 10 fields. Target_N $ChangeMe Target where the block should store the values of parameters that were retrieved. Advanced properties The Advanced tab of Get Input Parameters includes the properties in the following table. Property Default Value Description blockdebug off Debug level of the block. Before changing the default value, see Block debug property on page 327. start Get Input Parameters Block IC Script. Alarms Connections Generates no alarms. Accepts the following connections: Input: 1 or more Output: 1 Issue 3.0 July

112 Standard blocks Initialize Global Description Basic properties Creates and initializes a couple in the global sequence of couples. Globals hold non-persistent data that spans multiple flows, and multiple instances of flows, such as default routing criteria, or a count of voice contacts of a particular type. This block can be used in an initialization flow. Initialize Global invokes no external methods. Globals may be referenced in the property settings of other blocks by preceding the name with a percent sign (%). The Basic tab of Initialize Global includes the properties in the following table. Property Default Value Description globalname empty Name of the global. value empty Value of the global. This property is optional. Advanced properties The Advanced tab of Initialize Global includes the properties in the following table. Property Default Value Description blockdebug off Debug level of the block. Before changing the default value, see Block debug property on page 327. start InitGlobal Block IC Script. Alarms Connections Generates no alarms. Accepts the following connections: Input: 1 or more Output: Media Workflow Reference

113 General palette On Exit Description Sample workflow Basic properties Advanced properties Executes when the flow ends, whether the flow completes normally or is interrupted. This block has no connections to other blocks. This block can terminate the EDU and provide extra debugging capability when needed. On Exit invokes VDU.Terminate on the current EDUID if other blocks in the flow have touched the EDU. By default the request is sent to server EDU, passing Script variable vdu_id. If vdu_id is empty, the block tries to fill it from the data that arrived with the event or method that started this flow. You can modify these settings in the advanced properties. In debug mode, this block prints the name of the block that executed just prior to On Exit. This feature is useful for debugging flows. For an example of how On Exit can be used in a workflow, see Incoming Call flow on page 153. The Basic tab of On Exit does not have any properties. The Advanced tab of On Exit includes the properties in the following table. Property Default Value Description blockdebug off Debug level of the block. Before changing the default value, see Block debug property on page 327. start OnExit Block IC Script. vdu_id $vdu_id Script variable obtained from event or method that invokes the workflow. vduservername VDU Name of the EDU server. vduterminate on If set to on, terminates the EDU. vdutouched true If set to true, lets you terminate the EDU. Alarms Connections Generates no alarms. Has no connections to any other blocks. Issue 3.0 July

114 Standard blocks Raise Alarm Description Basic properties Raises an alarm explicitly by issuing the method Alarm.Alarm. Specifies the name, priority, and descriptive test that accompany the alarm. At runtime, the Workflow server prepends the specified alarm name with the text QWorkflow. For example, an alarm named MyAlarm has a designation of QWorkflow.MyAlarm at runtime. The Basic tab of Raise Alarm includes the properties in the following table. Property Default Value Description alarmname empty Mandatory. Name of the alarm. description empty Mandatory. Description of the alarm. priority low Mandatory. Priority of the alarm. Advanced properties The Advanced tab of Raise Alarm includes the properties in the following table. Property Default Value Description blockdebug off Debug level of the block. Before changing the default value, see Block debug property on page 327. start RaiseAlarm Block IC Script. Alarms Connections The purpose of this block is to generate an alarm. This block does not generate additional alarms. Accepts the following connections: Input: 1 or more Output: Media Workflow Reference

115 General palette Set Output Parameters Description Sample workflow Basic properties Sets the output arguments that are to be returned as a sequence of couples when the flow ends. For an example of how Set Output Parameters can be used in a workflow, see IV Chat flow on page 173. The Basic tab of Set Output Parameters includes the properties in the following table. Property Default Value Description ArgName empty Name of an argument to be returned. You can specify up to 10 names. ArgValue empty Value of the argument. Advanced properties The Advanced tab of Set Output Parameters includes the properties in the following table. Property Default Value Description blockdebug off Debug level of the block. Before changing the default value, see Block debug property on page 327. start Set Output Args from Block Properties Block IC Script. Alarms Connections Generates no alarms. Accepts the following connections: Input: 1 or more Output: 1 Issue 3.0 July

116 Standard blocks Set Default Values Description Assigns the values given in the value property of the block to the corresponding Script variable given against the VarName property of the block. This block is also known as the Set Values block.! CAUTION: CAUTION: Do not use this block when the workflow performs time-critical functions, such as routing of calls in a large contact center. If you do not use many input parameters, use the simple assignment statement with the = operator at the appropriate place in the block where the Script variable is used. Sample workflow Basic properties For an example of how Set Default Values can be used in a workflow, see the Set Values block in the Client Login flow on page 239. The Basic tab of Set Default Values includes the properties in the following table. Property Default Value Description Value_N empty Value to be assigned to the script variable. VarName_N $ChangeMe Name of the script variable. Advanced properties The Advanced tab of Set Default Values includes the properties in the following table. Property Default Value Description blockdebug off Debug level of the block. Before changing the default value, see Block debug property on page 327. start Set Default Values Block IC Script. Alarms Connections Generates no alarms. Accepts the following connections: Input: 1 or more Output: Media Workflow Reference

117 General palette Start Description Database connection Starts a flow. Only one Start block can exist in a given flow. You use this block to set the debug level for the flow. Start invokes no external methods. All workflows require a Start block, including Prompter agent script workflows. The DBNetwork property of the Start block enables the block and the workflow to obtain a unique database network session for database access. This unique database network session is essential for all workflows that need to access data in the database. The database network for each workflow must be a database network in the Interaction Center application. The Interaction Center application is part of the ccq.adl file that you use to configure the CCQ database. The focuses in the Interaction Center application are the database networks. For more information about database networks and how to access databases from workflows, see Avaya Workflow Designer User Guide. Note: Note: Avaya recommends that you always set the DBNetwork property in the Start block to ensure that the DCO session for the workflow is set at the beginning and is set only once in the flow. Timeout property The Start block also includes a ToolkitTimeout property that sets the number of seconds to pass before the workflow times out. For Prompter flows, the HTTP Timeout setting in the HTTP Connector is passed to the flow as sys_scripttimeout. The workflow uses sys_scripttimeout as the ToolkitTimeout property. This timeout allows an agent to wait for the amount of time represented by ToolkitTimeout before navigating to the next page in a Prompter agent script flow. Important:! Important: Avaya recommends that you do not alter the ToolkitTimeout property. Alarms Connections Generates no alarms. Has one output connection. Issue 3.0 July

118 Standard blocks Stop Description Basic properties Advanced properties Marks a planned exit point from a flow. Multiple Stop blocks may exist in a single flow. Stop invokes no external methods. The Basic tab of Stop has no properties. The Advanced tab of Stop includes the properties in the following table. Property Default Value Description blockdebug off Debug level of the block. Before changing the default value, see Block debug property on page 327. debugmessage empty If blockdebug is set to on, message to add to the workflow log when the Stop block runs. start Stop Block IC Script. Alarms Connections Generates no alarms. Has four input connections. Test Data Description Tests the value of any EDU element, such as a Script variable or string entered in the ValueToCompare property of the block. You can specify the EDU element to test, the type of test, the value to test against, and the mode of comparison.! CAUTION: CAUTION: Do not use this block when the workflow performs time-critical functions, such as routing of calls in a large contact center. If you need to do a large number of tests before a decision has to be made for the workflow to continue, develop a block with a Select...Case statement. For information about VBA programming statements, see IC Scripts VBA Scripting Reference. Sample workflow For an example of how Test Data can be used in a workflow, see the Num Records = 1 block in the Incoming Call flow on page Media Workflow Reference

119 General palette Basic properties The Basic tab of Test Data includes the properties in the following table. Property Default Value Description comparisonmode alphanumeric Mode used to compare the value of the data element against the specified value. Options are alphanumeric and numeric. operator = Operator to use in the comparison. Use one of the following operators from the drop-down list: < for a match that is less than the valuetocompare <= for a match that is less than or equal to the valuetocompare <> for a match that is less than or greater than the valuetocompare = for a match that is equal to the valuetocompare > for a match that is greater than the valuetocompare >= for a match that is greater than or equal to the valuetocompare valuetocompare 97 Value to use in the comparison with the value of the data element being tested. WhatToTest empty Element that you want to test. Advanced properties The Advanced tab of Test Data includes the properties in the following table. Property Default Value Description blockdebug off Debug level of the block. Before changing the default value, see Block debug property on page 327. start Test Data Block IC Script. Alarms Connections Generates no alarms. Has two named output connections: Yes: If the condition is satisfied, the workflow continues along the Yes connection. No: If the condition is not satisfied, the workflow continues along the No connection. Test Data accepts 1 or more input connections. Issue 3.0 July

120 Standard blocks Routing palette The Routing palette contains the following blocks, typically used in routing and qualification workflows for contacts of all media types: Add Routing Hints on page 120. Complete Qualification on page 122. Create Agent Desktop Data on page 123. Fetch Routing Hints on page 124. Map Hints to Queue on page 126. Set Chat Wait Treatment on page 129. Set Route Parameters on page 131. Set Routing Hint on page 133. Add Routing Hints Description Prerequisites Sample workflow Adds routing hints to the collection of routing hints for the contact. This block adds the routing hint value to the $scroutinghints variable that is used by the Map Hints to Queue block. The type of routing hint added by this block depends upon the type of contact. For example, a voice contact typically uses the DNIS value for a routing hint, and an contact typically uses the address in the To field of the contact. To use this block, add and configure the routing hints in the RoutingHint table of the Directory server. For more information, see IC Installation and Configuration and IC Administration Volume 1: Servers & Domains. For an example of how Add Routing Hints can be used in a workflow, see the qualification workflows, including the Incoming Call flow on page 153 and the Qualify flow on page Media Workflow Reference

121 Routing palette Basic properties The Basic tab of Add Routing Hints includes the properties in the following table. Property Default Value Description name_n intent Up to ten routing hint names. Each routing hint name must map to: A routing hint in the RoutingHint table of the Directory server. The script variable that is the value of the equivalent value_n. value_n $ToAddress Up to ten script variables that hold routing hint values. Each script variable value must: Map to the equivalent name_n. Be created and have a value added by an Input Parameters block. Advanced properties The Advanced tab of Add Routing Hints includes the properties in the following table. Property Default Value Description blockdebug off Debug level of the block. Before changing the default value, see Block debug property on page 327. newvdudata $scroutinghints Script variable which holds the values of the routing hints added by this block. Important: The same script variable must be used by all subsequent blocks in the workflow that require access to routing hint values. start Add Routing Hint Block IC Script. Alarms Connections Generates no alarms. Accepts the following connections: Input: 1 or more Output: 1 Issue 3.0 July

122 Standard blocks Complete Qualification Description Sample workflow Basic properties Advanced properties Completes the qualification of chat contacts and contacts in qualification workflows for Avaya IC standard routing. This block: 1. Calls the WebACD server with the method, WACD.Route. 2. Delivers all routing information collected by the workflow, including the value of the queue set by the Map Hints to Queue block and, for chat contacts, the Chat Wait Treatment. 3. Transfers control of the contact back to the WebACD server for routing to an agent or device. For an example of how Complete Qualification can be used in a workflow, see the chat qualification workflows and the qualification workflows, including Qualify Chat flow on page 164 and the Qualify flow on page 180. The Basic tab of Complete Qualification does not have any properties. The Advanced tab of Complete Qualification includes the properties in the following table. Property Default Value Description blockdebug off Debug level of the block. Before changing the default value, see Block debug property on page 327. contacthandle $contacthandle Script variable that holds the taskid used by the WebACD server for a chat contact or an contact. This information identifies the contact when the workflow calls the WebACD server after the qualification is complete. RouteParameters $sscplaidscript Script variable that holds the route parameters for the contact. servername WACD The name of the WebACD server. start Complete Qualification Block IC Script. 122 Media Workflow Reference

123 Routing palette Alarms Connections Generates no alarms. Accepts the following connections: Input: 1 or more Output: 1 Create Agent Desktop Data Description Sample workflow Basic properties Advanced properties Uses the EDU information to create the data that Avaya Agent and other agent desktop applications use for screen pops. This block: Assigns values to EDU couples. The values provide information about the contact that is later stored in the EDU record. This sequence may be written to the EDU server at a later time by a Write EDU or Create EDU block. Adds the AgentDesktop container to EDU and writes data to EDU using both EDU data and Customer record data, if it exists. For an example of how the Create Agent Desktop Data block can be used in a workflow, see the Incoming Call flow on page 153. The Basic tab of Create Agent Desktop Data does not have any properties. The Advanced tab of Create Agent Desktop Data includes the properties in the following table. Property Default Value Description blockdebug off Debug level of the block. Before changing the default value, see Block debug property on page 327. CreateContactOn ScreenPop CustomerLookup PhoneFormat true =(000) Opens the contact and customer information in the agent desktop application through a screen pop. Specifies the default format for customer phone numbers. The default uses the North American format. VduData $VduData Script variable where sequence of couples returned by EDU server is stored. start Create Agent Desktop Data Block IC Script. Issue 3.0 July

124 Standard blocks Alarms Connections Generates no alarms. Accepts the following connections: Input: 1 or more Output: 1 Fetch Routing Hints Description Sample workflow Basic properties For chat contacts and contacts only, fetches routing hints for the contact that were set during pre-qualification. This block automatically executes different code for chat qualification workflows and qualification workflows. This block: 1. Fetches the routing hints set during pre-qualification for the contact, as follows: For chat contacts, checks the routinghint.globalhint container in the EDU for the contact for the routing hint that was associated with the Web pages the customer visited, then matches that value with the routing hints in the RoutingHint table of the Directory server. For contacts, uses the value of the msgid field in the EDU to identify the msgid value and to fetch the hints identified in the analysis flow from the CCQ database, then writes the number of records to the NumRecords value. 2. Adds the value of the routing hints to the $scroutinghints script variable. For an example of how Fetch Routing Hints can be used in a workflow, see the chat qualification workflows and the qualification workflows, including Qualify Chat flow on page 164 and the Qualify flow on page 180. The Basic tab of Fetch Routing Hints does not have any properties. 124 Media Workflow Reference

125 Routing palette Advanced properties The Advanced tab of Fetch Routing Hints includes the properties in the following table. Property Default Value Description AdvocateEnabled false Determines the type of Avaya IC routing for which the workflow needs to qualify the contact. Tip: If the Avaya IC system includes Business Advocate, change the value to true. blockdebug off Debug level of the block. Before changing the default value, see Block debug property on page 327. MsgId empty For qualification only. String variable that contains the message ID found in the EDU. Depending on how you use the block in the workflow, this variable can be $RootMsgId or $MsgId. For more information, see the Fetch Routing Hints blocks in the Qualify flow on page 180. NumRecords $RecordCount For qualification only. String variable that contains the number of routing hint records found in the appropriate table in the CCQ database. RoutingHints $scroutinghints SeqCouple variable that contains the results of the routing hint query. This variable is used by the other blocks that work with routing hints, such as Set Routing Hints and Map Hints to Queue. start Fetch Routing Hints Block IC Script. Issue 3.0 July

126 Standard blocks Alarms Generates the alarms described in the following table: Alarm No RoutingHint record found for: hintvalue Advocate qualifier not set for RoutingHint: hintvalue Advocate qualifier in incorrect format: string Description An INFO alarm that can occur during chat qualification. This alarm occurs if a hintvalue in the routinghint.globalhint.* EDU container does not exist in the RoutingHint table. This alarm indicates that a valid routing hint does not exist in the RoutingHint table for the routing hint association on the Web page. To resolve, you can add the routing to the routing hint table, or delete the association from the Web page. An INFO alarm that can occur during chat qualification. This alarm indicates that a qualifier has not been created for a routing hint that is associated with a Web page. An INFO alarm that can occur during chat qualification. This alarm occurs if the value of the Category/Qualifier field in a record in the RoutingHint table record is not in the correct format. The block displays and logs the offending string is with the alarm. The correct format is Category/qualifier with no spaces. Connections Accepts the following connections: Input: 1 or more Output: 1 Map Hints to Queue Description Maps the hints collected in a script variable $scroutinghints to a queue in the RoutingHint table of the Directory server. If no queues are matched, then the contact is routed to the queue in the DefaultQueueID property. For more information about how routing hints work in Avaya IC, see Routing hints on page 29. Note: Note: For Business Advocate workflows, use the Map to Qualifier block. For more information, see Map to Qualifier on page Media Workflow Reference

127 Routing palette Sample workflow Example: single queue For an example of how the Map Hints to Queue block can be used in a workflow, see Incoming Call flow on page 153. You can map the hints to retrieve only one queue for each contact. For example, a contact center uses the following hints: sales and support. The RoutingHint table is configured to map the hints to the queues, as shown in the following table. Routing hint sales sales sales en sp Associated queue sales@defaulttenant sales_english@defaulttenant sales_spanish@defaulttenant sales_english@defaulttenant sales_spanish@defaulttenant For a contact which has hints identified for sales and en, Map Hints to Queue will: 1. Search the records in the RoutingHints table. For voice, the block only searches the Name field. For and chat, the block searches the Name field and the Tenant field. 2. Retrieve all queues that exactly match the hints of en and sales. For and chat, the tenant must be an exact match to the tenant_key value in the root of the EDU or the field must be empty. For example, the block would not retrieve the queues for sales@defaulttenant and sales_spanish@defaulttenant because these queues do not match the en hint. Example: multiple queues You can map the same hints to more than one queue. With this configuration, the block would retrieve more than one queue for a contact. Based on statistics found in the ADUs for the queues, the block selects the least loaded queue for the contact. Issue 3.0 July

128 Standard blocks Basic properties The Basic tab of Map Hints to Queue includes the properties in the following table. Property Default Value Description DefaultQueueID empty Mandatory. The default queues must exist in Avaya IC. For more information, see Routing hints on page 29. For , the default value is: For chat, the default value is For voice, the default value is Advanced properties The Advanced tab of Map Hints to Queue includes the properties in the following table. Property Default Value Description blockdebug off Debug level of the block. Before changing the default value, see Block debug property on page 327. RouteQueueID $RouteQueueID Script variable which holds the ID of the selected queue. RoutingHints $scroutinghints Script variable which holds the hints to be mapped to queues. start Map Hints to Queues Block IC Script. TenantKey $tenant_key Script variable that holds the value from the tenant_key field in the EDU for chat and Media Workflow Reference

129 Routing palette Alarms Generates the alarms described in the following table. Alarm No RoutingHint record found for: hintvalue Advocate qualifier not set for RoutingHint: hintvalue Advocate qualifier in incorrect format: string Description INFO alarm for chat contacts only. The block generates this alarm if the hint value found in the routinghint.globalhint EDU container does not exist in the RoutingHint table of the Directory server. This alarm indicates that a previously valid routing hint has been deleted but the Web page has not been updated. INFO alarm for chat contacts only. The block generates this alarm if the routing hint from the Web page does not have the corresponding Advocate Category/Qualifier field set. INFO alarm for chat contacts only. The block generates this alarm if the value of the Category/Qualifier field in a RoutingHint table record is not in the correct format. The block outputs the offending string with the alarm. The correct format is Category/qualifier with no spaces. Connections Accepts the following connections: Input: 1 or more Output: 1 Set Chat Wait Treatment Description Sample workflow For chat contacts only, sets the wait treatment style for the chat contact. Each Set Chat Wait Treatment block represents one Web page to be displayed to a customer waiting to chat with an agent. You can use a series of Set Chat Wait Treatment blocks to create a script with a sequence of Say Text messages and Web pages that the workflow pushes to customers in queue. For an example of how this block can be used in a flow, see Qualify Chat flow on page 164 and Qualify Chat flow for Business Advocate on page 271. Issue 3.0 July

130 Standard blocks Basic properties The Basic tab of Set Chat Wait Treatment includes the properties in the following table. Property Default Value Description PushURL empty Mandatory. URL of Web page to be displayed to customers. SayText empty Mandatory. Message to be displayed to customer (for example, "Wait"). WaitTime empty Mandatory. Length of time in seconds that the workflow displays this wait treatment sequence to the customer. Enter a value of -1 to play this step in the sequence indefinitely. Advanced properties The Advanced tab of Set Chat Wait Treatment includes the properties in the following table. Property Default Value Description blockdebug on Debug level of the block. Before changing the default value, see Block debug property on page 327. ChatWaitSequence empty Script variable that holds all of the steps in the wait sequence. This variable must be identical in all Set Chat Wait Treatment blocks in a workflow. Important: Assign this variable to the ConnectionData property of the Post Qualification block. start Set Chat Wait Treatment Block IC Script. Alarms Connections Generates no alarms. Accepts the following connections: Input: 1 or more Output: Media Workflow Reference

131 Routing palette Set Route Parameters Description Route parameters Sample workflow Basic properties Sets route parameters for contacts and chat contacts. The parameters set by this block depend upon which type of contact is qualified by the workflow. This block retrieves and sets values for the route parameters. The route parameters are: Name of the preferred agent Queue where the contact is to be routed Workgroups associated with the queue Priority of the contact in the queue For an example of how Set Route Parameters can be used in a workflow, see the chat qualification workflows and the qualification workflows, including the Qualify Chat flow on page 164 and the Qualify flow on page 180. The Basic tab of Set Route Parameters includes the properties in the following table. Property Default Value Description DefaultWorkgroup Default Default workgroup associated with the the queue where the contact is to be routed. Priority normal Default priority of the contact in the queue. The options in the drop-down list are: high low normal urgent RouteQueueID $RouteQueueId Script variable that includes the pkey of the queue where the contact is to be routed. Wait 300 Default wait time of the contact for each workgroup The minimum wait is at least 10 seconds. Issue 3.0 July

132 Standard blocks Advanced properties The Advanced tab of Set Route Parameters includes the properties in the following table. Property Default Value Description blockdebug off Debug level of the block. Before changing the default value, see Block debug property on page 327. Channel $MediaType Script variable that holds the media type of the contact. IVChatWorkgroup empty For Avaya IC systems that include Voice Chat. Specifies the workgroup for agents who can handle Chat & VOIP voice chat contacts. Important: The value of this property must be the name of a valid workgroup. This workgroup must include agents who can handle contacts from the voice and chat channels. PVChatWorkgroup empty For Avaya IC systems that include Voice Chat. Specifies the workgroup for agents who can handle Chat & Phone voice chat contacts. Important: The value of this property must be the name of a valid workgroup. This workgroup must include agents who can handle contacts from the voice and chat channels. RouteParameters $sscplaidscript Script variable that holds the route parameters for the contact. This variable is used by the Complete Qualification block. start Route Parameters Block IC Script. Alarms Connections Generates no alarms. Accepts the following connections: Input: 1 or more Output: Media Workflow Reference

133 Routing palette Set Routing Hint Description Sample workflow Basic properties Sets a value in the $scroutinghints script variable for the category or keyword found by a test block, such as Test Category on page 82. For an example of how Set Routing Hint can be used in a workflow, see the Set Routing Hint (approvalrequired) block in the Outbound with Keywords flow on page 207. The Basic tab of Set Routing Hint includes the properties in the following table. Property Default Value Description RoutingHintField empty Mandatory. Name of the routing hint. Value empty Value of the routing hint. Advanced properties The Advanced tab of Set Routing Hint includes the properties in the following table. Property Default Value Description blockdebug off Debug level of the block. Before changing the default value, see Block debug property on page 327. start Set Routing Hint Block IC Script. Alarms Connections Generates no alarms. Accepts the following connections: Input: 1 or more Output: 1 Issue 3.0 July

134 Standard blocks Telephony palette The Telephony palette contains the following blocks, typically used in media workflows for voice contacts: Hangup Call on page 134. Transfer Call on page 135. Hangup Call Description Hangs up phone for the current voice contact by issuing the method TS.Hangup or TS.HangupVDU. Hangup Call does not end the workflow. By default the request is sent to server TS, passing Script variable vdu_id. If vdu_id is empty, the block tries to fill it from the data that arrived with the event or method that started this flow. If vdu_id is not empty and an EDUID is determined, this block calls TS.HangupVDU. If not, it calls TS.Hangup. You can modify these settings in the advanced properties. Note: Note: At this time, the Hangup Call block is only qualified in Avaya Definity, Avaya MultiVantage, and Aspect telephony environments. Basic properties Advanced properties The Basic tab of Hangup Call does not have any properties. The Advanced tab of Hangup Call includes the properties in the following table. Property Default Value Description blockdebug off Debug level of the block. Before changing the default value, see Block debug property on page 327. servername TS Name of the Telephony server. start Hangup Call Block IC Script. vdu_id $vdu_id Script variable obtained from event or method that invokes the workflow. 134 Media Workflow Reference

135 Telephony palette Alarms Connections Generates no alarms. Accepts the following connections: Input: 1 or more Output: 1 Transfer Call Description Routes or transfers a voice contact by issuing the method TS.Transfer or TS.Route. You specify the destination (as a literal or variable). By default the request is sent to server TS, passing Script variable vdu_id. If vdu_id is empty, the block tries to fill it from the data that arrived with the event or method that started this flow. The block determines which method to use by the name of the event that launched the flow: If the event was TS.IncomingCall, the method called is TS.Route. If another event launches the flow, the method called is TS.Transfer. You can modify these settings and behaviors in the advanced properties. Note: Note: At this time, Transfer Call is qualified in Avaya Definity, Avaya MultiVantage, and Aspect telephony environments. Sample workflow Basic properties For an example of how the Transfer Call block can be used in a workflow, see Incoming Call flow on page 153. The Basic tab of Transfer Call includes the properties in the following table. Property Default Value Description destination empty Route point (VDN) of the telephony switch. Can be a literal value or a script variable which holds the value. Issue 3.0 July

136 Standard blocks Advanced properties The Advanced tab of Transfer Call includes the properties in the following table. Property Default Value Description blockdebug off Debug level of the block. Before changing the default value, see Block debug property on page 327. globaldefault $DEFAULT_DEST Global default for the destination. localdefault empty Local default for the destination. servername TS Name of the Telephony server. start Transfer Call Block IC Script. tsmethod <automatic> Method to be issued to the Telephony server to route the contact. vdu_id $vdu_id Script variable obtained from event or method that invokes the workflow. Alarms Connections Generates an alarm (QWorkflow.TransferCallError) if no EDUID can be determined. Accepts the following connections: Input: 1 or more Output: Media Workflow Reference

137 Tools palette Tools palette The Tools palette contains blocks that are typically used in media workflows. This section includes the following topics which describe those blocks: Build SeqCouple on page 137. Build SeqString on page 138. Build String on page 139. Copy SeqCouple on page 140. Find Value in SeqCouple on page 141. Format String on page 142. Keyword Search 1 on page 143. Keyword Search 3 on page 145. Parse SeqCouple on page 146. Parse SeqSeqCouple on page 147. Build SeqCouple Description Basic properties Builds a sequence of couples from the specified pairs of names and values. The sequence of couples can include up to twelve pairs of names and values. The Basic tab of Build SeqCouple includes the properties in the following table. Property Default Value Description name_n empty Name of a property or data element to be included in the sequence of couples. value_n empty Value of property or data element. Issue 3.0 July

138 Standard blocks Advanced properties The Advanced tab of Build SeqCouple includes the properties in the following table. Property Default Value Description blockdebug off Debug level of the block. Before changing the default value, see Block debug property on page 327. EmptyFirst yes Delete the current content of the output sequence string before building the sequence of couples. Output $ssoutput Output sequence string for the sequence of couples built by the block. start BuildSeqCouple Block IC Script. Alarms Connections Generates no alarms. Accepts the following connections: Input: 1 or more Output: 1 Build SeqString Description Basic properties Builds a sequence of text strings from the specified values. The sequence of strings can include up to twelve values. The Basic tab of Build SeqString includes the properties in the following table. Property Default Value Description value_n empty Value of text string. 138 Media Workflow Reference

139 Tools palette Advanced properties The Advanced tab of Build SeqString includes the properties in the following table. Property Default Value Description blockdebug off Debug level of the block. Before changing the default value, see Block debug property on page 327. EmptyFirst yes Delete the current content of the output file before building the sequence of strings. Output $scoutput Output file for the sequence of strings built by the block. start Build SeqString Block IC Script. Alarms Connections Generates no alarms. Accepts the following connections: Input: 1 or more Output: 1 Build String Description Basic properties Builds a text string from a series of specified values for substrings. The text string can include up to 10 substrings. The Basic tab of Build String includes the properties in the following table. Property Default Value Description Result $sresult Text string built by the block. SubString_N $schangeme Value of substring. Issue 3.0 July

140 Standard blocks Advanced properties The Advanced tab of Build String includes the properties in the following table. Property Default Value Description blockdebug off Debug level of the block. Before changing the default value, see Block debug property on page 327. start Build String Block IC Script. Alarms Connections Generates no alarms. Accepts the following connections: Input: 1 or more Output: 1 Copy SeqCouple Description Basic properties Copies the named couple from the sequence of couples specified as Source to the sequence of couples specified as Destination. The block can copy up to twelve values to another sequence of couples. The Basic tab of Copy SeqCouple includes the properties in the following table. Property Default Value Description name_n empty Name of the couple to be copied. Advanced properties The Advanced tab of Copy SeqCouple includes the properties in the following table. Property Default Value Description blockdebug off Debug level of the block. Before changing the default value, see Block debug property on page 327. CopyEmpty no Copies the couple if the value is empty. Destination $scoutput Sequence of couples where the couple is to be copied. EmptyFirst no Delete the current content of the output file before copying the couples. 140 Media Workflow Reference

141 Tools palette Property Default Value Description Source $scin Sequence of couples from which the the couple is to be copied. start Build SeqCouple Block IC Script. Alarms Connections Generates no alarms. Accepts the following connections: Input: 1 or more Output: 1 Find Value in SeqCouple Description Basic properties Searches a sequence of couples for a specific couple, then writes the value for that couple to the Value property if it is not NULL. This block: 1. Searches the specified sequence of couples for the specified couple. 2. Extracts the value of the couple. 3. If the value is: Not NULL, the workflow exits through the "Found" named connection. NULL, or if the specified couple is not found, the workflow exits through the "Not Found" named connection. The Basic tab of Find Value in SeqCouple includes the properties in the following table. Property Default Value Description CoupleNameToFind empty Mandatory. The name of the couple that you want the block to find in the sequence of couples. Issue 3.0 July

142 Standard blocks Property Default Value Description SeqCoupleName empty Mandatory. The sequence of couples that you want the block to search for the named couple. Value empty Mandatory. Contains the results of the search, either the value associated with the CoupleNameToFind property or NULL. Advanced properties The Advanced tab of Find Value in SeqCouple includes the properties in the following table. Property Default Value Description blockdebug off Debug level of the block. Before changing the default value, see Block debug property on page 327. start Find Value in SeqCouple Block IC Script. Alarms Connections Generates no alarms. Has two named output connections: Found: If the CoupleNameToFind name was found and had a value that was not NULL, the workflow continues along this connection. Not Found: If the CoupleNameToFind is not found, or has a value of NULL, the workflow continues along this connection. Find Value in SeqCouple accepts one or more input connections Format String Description Sample workflow Formats a text string into a specified format. For an example of how the Format String block can be used in a workflow, see the Format ANI block in the Incoming Call flow on page Media Workflow Reference

143 Tools palette Basic properties The Basic tab of Format String includes the properties in the following table. Property Default Value Description Format empty The format that you want to use for the text string. For example, to use this block to format an ANI into the telephone number format used in North America, enter (000) Result $sresult Formatted text string created by the block. ValueToFormat $schangeme Name of the string variable to be formatted. For example, to format the ANI for a voice contact, enter $VoiceANI. Advanced properties The Advanced tab of Format String includes the properties in the following table. Property Default Value Description blockdebug off Debug level of the block. Before changing the default value, see Block debug property on page 327. start Format String Block IC Script. Alarms Connections Generates no alarms. Accepts the following connections: Input: 1 or more Output: 1 Keyword Search 1 Description Search for a keyword within the script variable specified in the property FieldToSearch. You can enter any valid regular expression in the property SearchPattern. You can only use this block to search for one valid regular expression in one field of the contact. You can add additional Keyword Search 1 blocks to search for another expression or for the same expression in a different field. Issue 3.0 July

144 Standard blocks Sample workflow Basic properties For an example of how Keyword Search 1 can be used in a workflow, see Analyze with Keywords flow on page 196. The Basic tab of Keyword Search 1 includes the properties in the following table. Property Default Value Description FieldToSearch empty Field that the block should search. This field is typically in an item such as an contact. For example, enter $subject to search the subject line of an contact. SearchPattern1 empty Text string in the field for which the block searches. For example, enter "You've Won!!" to search for that text in the subject line of an contact. Advanced properties The Advanced tab of Keyword Search 1 includes the properties in the following table. Property Default Value Description blockdebug off Debug level of the block. Before changing the default value, see Block debug property on page 327. start Keyword Search Regex 1 Block IC Script. Alarms Connections Generates no alarms. Has two named output connections: SearchPattern1: If the expression in the property SearchPattern1 is found, the workflow continues along this connection. False: If the expression in the property SearchPattern1 is not found, the workflow continues along this connection. Keyword Search 1 accepts 1 or more input connections. 144 Media Workflow Reference

145 Tools palette Keyword Search 3 Description Sample workflow Basic properties Search for up to three keywords within the script variable defined for the property FieldToSearch. You can enter any valid regular expression in the properties SearchPattern1, SearchPattern2, and SearchPattern3. You can add additional Keyword Search 3 blocks to search for different expressions or for the same expressions in a different field. For an example of how Keyword Search 3 can be used in a workflow, see Analyze with Keywords flow on page 196. The Basic tab of Keyword Search 3 includes the properties in the following table. Property Default Value Description FieldToSearch empty Field in the target item to search. For example, enter $subject to search the subject line of an contact. SearchPattern1 empty Text string in the field for which the block searches. For example, enter "You've Won!!" to search for that text in the subject line of an contact. SearchPattern2 empty Text string in the field for which the block searches. SearchPattern3 empty Text string in the field for which the block searches. Advanced properties The Advanced tab of Keyword Search 3 includes the properties in the following table. Property Default Value Description blockdebug off Debug level of the block. Before changing the default value, see Block debug property on page 327. start Keyword Search Regex 3 Block IC Script. Issue 3.0 July

146 Standard blocks Alarms Connections Generates no alarms. Has four named connections: SearchPattern1: If the expression in the property SearchPattern1 is found, the workflow continues along this connection. SearchPattern2: If the expression in the property SearchPattern2 is found, the workflow continues along this connection. SearchPattern3: If the expression in the property SearchPattern3 is found, the workflow continues along this connection. False: If the expressions in the above properties are not found, the workflow continues along this connection. Keyword Search 3 accepts 1 or more input connections. Parse SeqCouple Description Basic properties Parses a sequence of couples to retrieve values from specified objects and adds them to a specified target. The block can parse and retrieve up to ten values. The Basic tab of Parse SeqCouple includes the properties in the following table. Property Default Value Description Field_N empty Name of the couple in the sequence of couples from which a value is to be retrieved. SeqCouple $scchangeme Sequence of couples to parse. Target_N $scchangeme Target where the block stores the value retrieved from the sequence of couples. Advanced properties The Advanced tab of Parse SeqCouple includes the properties in the following table. Property Default Value Description blockdebug off Debug level of the block. Before changing the default value, see Block debug property on page 327. start Parse SeqCouple Block IC Script. 146 Media Workflow Reference

147 Tools palette Alarms Connections Parse SeqCouple generates an alarm with the following values if the sequence of couples does not include a value for a specified object: Alarm text is "Input Data is Empty". Alarm priority is High. Accepts the following connections: Input: 1 or more Output: 1 Parse SeqSeqCouple Description Basic properties Parses a sequence of sequence of couples to retrieve values from specified objects and add them to a specified target. The block can parse and retrieve up to ten values. The Basic tab of Parse SeqSeqCouple includes the properties in the following table. Property Default Value Description Field_N empty Object in the sequence of sequence of couples from which a value is to be retrieved. OutSeqCouple $scoutseq Variable for target sequence of couples. Couple RecordNumber 1 Identifies the sequence of couples in the sequence of sequence of couples. For example, the default of 1, retrieves values from the first sequence of couples. SeqSeqCouple $sscchangeme Sequence of sequence of couples to parse. Target_N $schangeme Target where the block stores the value retrieved from the sequence of sequence of couples. Issue 3.0 July

148 Standard blocks Advanced properties The Advanced tab of Parse SeqSeqCouple includes the properties in the following table. Property Default Value Description blockdebug off Debug level of the block. Before changing the default value, see Block debug property on page 327. start Parse SeqSeqCouple Block IC Script. Alarms Connections Parse SeqSeqCouple generates the following alarms: An alarm with the following values if the sequence of couples does not include a value for a specified object: - Alarm text is "Input Data is Empty". - Alarm priority is High. An alarm with the following values if the number of records does not match the value in the RecordNumber property: - Alarm text is "Record Number X is out of range". - Alarm priority is High. Accepts the following connections: Input: 1 or more Output: Media Workflow Reference

149 Telephony in Avaya IC Chapter 4: Voice contact routing flows Avaya IC uses voice contact routing flows to route incoming voice contacts. This section describes how routing works for Telephony in Avaya IC, and the sample voice contact routing flow provided with Avaya IC. Topics include: Telephony in Avaya IC on page 149. Prerequisites for the Incoming Call flow on page 151. Customization of the Incoming Call flow on page 152. Incoming Call flow on page 153. Note: Note: If your Avaya IC system uses Business Advocate to route voice contacts, use the contact routing flows for Business Advocate. For more information, see Qualify Voice flow for Business Advocate on page 263. Telephony in Avaya IC Telephony in Avaya IC is a combination of components that handle data about incoming voice contacts. Workflows use this information to route contacts, to provide an agent with information to assist them with the contact, and to store the information in a database. Because the activities in each contact center are unique, the use of the data gathered by the Telephony system is unique to each contact center. This section describes one way that Telephony components handle and route voice contacts, and the information that the components use to perform this task. Topics include: Routing process for voice contacts on page 150. Incomingcall events on page 151. Issue 3.0 July

150 Voice contact routing flows Routing process for voice contacts As shown in the following figure, each Telephony component plays a part in routing incoming voice contacts to an agent desktop. When the telephony switch receives a voice contact: 1. The telephony switch notifies the Telephony server. The server enables communication between the switch and the Telephony system. The switch passes relevant information about the voice contact to the server, including: a. ANI Telephone number of the caller b. DNIS Telephone number at the contact center that the caller dialled 2. When notified of an incoming call, the Telephony server sends a request to the EDU server to create an EDU for the call. The EDU contains a detailed record of the contact. For more information, see Avaya Workflow Designer User Guide and Electronic Data Unit Server Programmer Guide. 3. The Telephony server also sends an Incomingcall event to various other components, including the Workflow server. 150 Media Workflow Reference

151 Prerequisites for the Incoming Call flow Incomingcall events The Telephony server sends an Incomingcall event to the Workflow server with the EDUID for this contact. The Workflow server runs all flows. When you configure the Workflow server, you specify which contact routing flow should run when an Incomingcall event arrives. For information on how to configure the Workflow server, see IC Administration Volume 1: Servers & Domains. You must synchronize your contact center s telephone switch, IVR, and contact routing flows to correctly hand off contact information to the appropriate component. For programming information, see the documentation for the switch and IVR. There are several other components in the Telephony system that can be involved in routing a contact, but an understanding of all components is not required for a general understanding of contact routing flows. For more information, refer to the complete Telephony documentation set. Prerequisites for the Incoming Call flow For the Incoming Call flow to run: 1. Create a Default Voice Queue to match the property in the Map Hints to Queue block. For more information, see IC Installation and Configuration. 2. Configure the Voice channel and association in the Workflow server. 3. Configure the Workflow server to use the Web Routing flow update_qw_cache as a synchronous startup flow. This flow creates the global variables that associate queues to workgroups. For more information about how to perform the steps in IC Manager, see IC Administration Volume 1: Servers & Domains. Issue 3.0 July

152 Voice contact routing flows Customization of the Incoming Call flow You do not need to configure or customize blocks to use the sample Incoming Call flow. If you want to change the way that the workflow routes voice contacts, you can modify the properties in the existing blocks, or add and configure new blocks to the workflow. This section includes the following topics: Modifying block properties on page 152. Adding blocks on page 152. Modifying block properties You can customize the Incoming Call flow by modifying the properties of blocks in the workflow. You can modify the values for the properties of blocks in this workflow, if you want to route voice contacts to a particular ACD queue or a particular agent. You can base the decision to route a voice contact to a particular agent or queue on the value of any of the elements of the EDU data, such as the DNIS. For example, you can modify the value of the DefaultQueueID property in the Map Hints to Queue block. When you modify this property, you change the queue that the workflow uses if the block cannot match the voice contact to a queue through routing hints. Adding blocks You can customize the Incoming Call flow with additional blocks. For example, you can add new blocks to the workflow if you want the Incoming Call flow to handle prequalification data from an IVR. 152 Media Workflow Reference

153 Incoming Call flow Incoming Call flow The Incoming Call contact routing flow routes incoming voice contacts. An IncomingCall event sent by the Telephony server invokes the Incoming Call workflow. The sample Incoming Call flow is shown in the following figure: Group the blocks of the sample Incoming Call flow into several steps to see how the workflow processes an incoming voice contact. For example, this flow contains the following groups of blocks: 1. Input parameters and EDU values on page Contact information on page Routing hints on page Transfer voice contact on page Stop flow on page 157. Issue 3.0 July

154 Voice contact routing flows Input parameters and EDU values When Avaya IC receives a voice contact, the Workflow server starts the Incoming Call flow. The first group of blocks gets EDU values for the contact, as shown in the following figure The Incoming Call flow uses the following blocks to perform these functions: Step Block Name Description Start Flow 1 Get Input Parameters Starts the workflow. Incorporates the code for getting a unique database network session for database access through its DBNetwork property. Retrieves values for the input parameters listed on the Basic tab and enters the values in the specified symbols 2 Fetch EDU Fetches the EDU specified in the input argument from the IncomingCall event that invoked the workflow. 3 Get EDU Values Retrieves the value of the EDU attributes ani and dnis from the EDU data fetched in Step 1. 4 Set EDU Assigns a value of $digits to the digits field in the EDU. 5 Write EDU Writes the value of $digits that was assigned by the Set EDU block to the digits field in the EDU. 154 Media Workflow Reference

155 Incoming Call flow Contact information After the Incoming Call flow gets input parameters and EDU values, the flow sets additional values for the incoming voice contact. The values set by the second group of blocks, shown in the following figure provide more information to assist the agent with the customer The flow uses the following blocks to perform these functions: Step Block Name Description 6 Format ANI Formats the ANI of the contact for searches. 7 Fetch Customer Record 1. Checks the Customer table of the CCQ database for a record that matches the ANI of the contact. 2. Sets a NumRecords value for the number of records that match the ANI. 3. If only one Customer record is available, retrieves the specified values from the Customer record. To modify the values that the block retrieves from the Customer record, add or modify a pair of Field_N and Value_N parameters on the Basic tab. Each field must correspond to a field in the Customer table. 8 NumRecords=1 Tests the NumRecords value set by the Fetch Customer Record block to see if the value is 1. If the answer is: Yes, the value is 1, proceeds to Step 9, Fetch EDU. No, the value is not 1, proceeds to Step 10, Create Agent Desktop Data. Issue 3.0 July

156 Voice contact routing flows Step Block Name Description 9 Fetch EDU Fetches the EDU data again. The workflow can then use both the EDU data and the Customer data retrieved by the Fetch Customer Record block. 10 Create Agent Desktop Data Uses the EDU data and Customer data to create the data that Avaya Agent and other agent desktop applications use for screen pops. If the Fetch Customer Record block found more than one Customer record, or no Customer records, this block uses only the values in the EDU. Routing hints This group of blocks, shown in the following figure, uses routing hints from the EDU to determine which agent or queue should receive the contact. The routing hints are the DNS and the last VDN from the EDU The flow uses the following blocks to perform these functions: Step Block Name Description 11 Add Routing Hints (DNIS) 1. Checks the EDU for the DNIS of the voice contact. 2. Adds the DNIS value to the $scroutinghints variable that is used by the Map Hints to Queue block. Note: To use routing hints, you must add them to the RoutingHint table in IC Manager. For more information, see IC Installation and Configuration and IC Administration Volume 1: Servers & Domains. 12 Map Hints to Queue 1. Maps the hints collected in the $scroutinghints script variable to a routing hint in the RoutingHint table of the Directory server. 2. Uses the routing hints to identify a queue to which the contact should be routed. 156 Media Workflow Reference

157 Incoming Call flow Transfer voice contact This block transfers the voice contact to an agent or queue, as shown in the following figure. You can set the Route Queue ID to a device number or a queue name, depending on how you configure your Avaya IC system. 13 The flow uses the following blocks to perform these functions: Step Block Name Description 13 Transfer Call Calls the Telephony server with the routing information collected by the workflow, including the value of the queue set by the Map Hints to Queue block. Important: Do not change the value of the destination property. The value of the destination property must be $RouteQueueId to ensure that the workflow routes the voice contact to the queue determined by the Map Hints to Queue block in Step 12, Map Hints to Queue. Stop flow The Stop block marks the exit point for the workflow. After the Stop block, the Workflow server executes the On Exit block. Issue 3.0 July

158 Voice contact routing flows 158 Media Workflow Reference

159 Prerequisites for the Qualify Chat flow Chapter 5: Chat contact routing flows Avaya IC uses chat contact routing flows to route chat contacts. This section describes the sample chat contact routing flow provided with Avaya IC. Topics include: Prerequisites for the Qualify Chat flow on page 159. Customization of the Qualify Chat flow on page 160. Qualify Chat flow on page 164. Note: Note: If your Avaya IC system uses Business Advocate to route voice contacts, use the contact routing flows for Business Advocate. For more information, see Qualify Chat flow for Business Advocate on page 271. Prerequisites for the Qualify Chat flow For the Qualify Chat flow to run: 1. Create routing hints in the RoutingHints table of the Directory server. 2. Associate the routing hints with Web Self-Service documents. 3. Create at least one queue for the Avaya IC site that hosts the WebACD server. 4. Set the property Site for the WebACD server in IC Manager. 5. Configure the Chat channel and association in the Workflow server. 6. Configure the Workflow server to use the Web Routing flow update_qw_cache as a synchronous startup flow. This flow creates the global variables that associate queues to workgroups. For more information about how to perform the steps in IC Manager, see IC Administration Volume 1: Servers & Domains. Issue 3.0 July

160 Chat contact routing flows Customization of the Qualify Chat flow You can route chat contacts to a specific agent or to a chat queue. You can configure the Qualify Chat workflow to base the decision to route a chat contact to a particular agent or queue on the value of any of the elements of the EDU data, such as language. This section includes the following topics: Modifying block properties on page 160. Adding blocks on page 160. Using localizable on-hold treatments on page 160. Modifying block properties You can customize the Qualify Chat flow by modifying the properties of blocks in the workflow. For example, you can modify the value of the DefaultQueueID property in the Map Hints to Queue block. When you modify this property, you change the queue that the workflow uses if the block cannot match the chat contact to a queue through routing hints. Adding blocks You can customize the Qualify Chat flow with additional blocks. For example, you can add the following additional blocks: Set Wait Treatment blocks to add more steps or pages to the Wait Treatment displayed to the customers. Add Routing Hints blocks to use more routing hints to route chat contacts to agents. Using localizable on-hold treatments You can create an on-hold treatment for chat contacts that automatically localizes the message. Web Management automatically sends a system message to customers while they wait to talk to an agent. This system message is the on hold treatment. You can configure the on hold treatment to automatically substitute the message with a phrase in the language that the customer selects. 160 Media Workflow Reference

161 Customization of the Qualify Chat flow For example, you can send an on hold treatment to customers that reads: English Welcome to MyStore! Spanish Recepción a MyStore! French Bienvenue à MyStore! Avaya IC can automatically substitute a phrase in the correct language if: The On Hold Treatment in the Qualify Chat workflow contains template variables of the form $mytemplatevariable$. For every $mytemplatevariable$ in the Qualify Chat workflow, you must add a corresponding chat.phrases.mytemplatevariable in the Web Management MultiTenant configuration metadata. The ICM server substitutes the template variables for the metadata properties. You enter the translations for the metadata phrase in the Web Management MultiTenant configuration Web pages. This section includes the following steps that to create an on hold treatment that Web Management automatically localizes for the customer: 1. Adding the metadata properties on page Updating the tenant properties on page Customizing the Qualify Chat workflow on page 163. Adding the metadata properties! CAUTION: CAUTION: If you incorrectly add new metadata, you can cause problems with your Web Management system. Contact CRM Technical Support or Avaya Professional Services for assistance. To add the metadata properties: 1. In IC Manager, select Services > MultiTenancy Administration. 2. In your Web browser, navigate to the following URL Issue 3.0 July

162 Chat contact routing flows 3. On the Add Metadata page, enter the properties for the new metadata shown in the following table. Property Metadata name Default value Description Tenant Property Language Property Value Full name of the chat phrase, such as chat.phrases.mytemplatevariable Phrase in English for the on hold treatment, such as Welcome to MyStore! Custom description of the metadata property. Accept the default. Select Language Property. Repeat step 3 to customize the metadata value for all desired languages. Updating the tenant properties To update the tenant properties: 1. In IC Manager, select Services > MultiTenancy Administration. 2. Click Tenant Properties in the Navigation bar. 3. Select the tenant to customize. 4. Select the language from the Language drop-down list. For example, to update the tenant properties for Spanish, select Spanish (es) 5. Select chat from the list of property categories. 6. Find the chat phrase metadata that you created in Adding the metadata properties on page 161. For example, find chat.phrases.mytemplatevariable 7. Clear the Inheritance checkbox. 8. Enter the value for the selected language in the field next to the metadata. For example, for Spanish enter Recepción a MyStore! 9. Select Update. Repeat these steps for each desired language. If you want to use a different phrase for each tenant, repeat these steps for each supported tenant. 162 Media Workflow Reference

163 Customization of the Qualify Chat flow Customizing the Qualify Chat workflow To customize the Qualify Chat workflow: 1. In Workflow Designer, select Project > Open and open the wacd project. By default this project is in: IC_INSTALL_DIR\IC61\design\IC\Flows\Avaya\wacd\wacd.prj 2. Double-click the Qualify Chat workflow (qualifychat) in the Project bar. 3. Select the Set Chat Wait Treatment block. 4. In the Property Sheet, select the Basic tab. 5. Select the field next to the SayText parameter. 6. Replace the default with the name of the template variable. For example, if you entered chat.phrases.mytemplatevariable in the metadata, change the default to read $mytemplatevariable$. Note: Note: Workflow Designer interprets values that use a dollar sign for the first character as a Workflow variable. If you plan to use only the name of the template variable in the Say parameter, use a special character, such as a space or underscore, for the first character. 7. Select File > Save and save the workflow. 8. Select Build > Build Flow Set to build the workflow. 9. Reload the workflows in the Workflow server that processes chat contacts. Issue 3.0 July

164 Chat contact routing flows Qualify Chat flow The Qualify Chat contact routing flow routes incoming chat contacts. A wacd.qualifychat event sent by the WebACD server starts the Qualify Chat flow. The sample Qualify Chat flow is shown in the following figure. 164 Media Workflow Reference

165 Qualify Chat flow You can group the blocks of the sample Qualify Chat flow into several steps to see how the workflow processes an incoming chat contact. For example, this flow contains the following groups of blocks: 1. EDU values and input parameters on page Customer lookup on page Customer preferences on page Routing hints on page Route parameters and wait treatments on page Complete chat qualification on page Stop flow on page 172. You must modify the properties of some of these blocks to customize the workflow to run in your system. For example, you need to modify the value of the property PushURL in the Set Route Step block to ensure that the web page displayed to the customer in a chat contact is the page that you want your customers to see. EDU values and input parameters When Avaya IC receives a chat contact, the Workflow server starts the Qualify Chat flow. The first group of blocks gets EDU values and input parameters for the contact, as shown in the following figure The flow uses the following blocks to perform these functions: Step Block Name Description Start Flow Starts the workflow. Incorporates the code for getting a unique database network session for database access through its DBNetwork property. 1 Fetch EDU Fetches the EDU specified in the input argument from the wacd.qualifychat event that invoked the workflow. Issue 3.0 July

166 Chat contact routing flows Step Block Name Description 2 Get EDU Values Retrieves the value of the EDU attributes that are specified in the Field properties on the Basic tab. The EDU attributes include the following: type Assigns the value of the channel type of the contact to the $MediaType script variable. languagecode Assigns the value of the language for the contact from the EDU to the $language script variable. tenant_key Assigns the value for the tenant from the EDU to the $tenant_key script variable. preferredagentname If the customer record includes the agent ID for a preferred agent, assigns the value for the preferred agent to the $PreferredAgent script variable. customerid If the customer logged in to the Website with a valid Avaya IC customer ID, assigns the value of the customer ID to the $CustomerKey script variable. 3 Get Input Parameters Retrieves values for the input parameters listed on the Basic tab and enters the values in the specified symbols Customer lookup After the flow sets the initial parameters, the next group of blocks searches the Customer table in your database for information about the customer, as shown in the following figure Media Workflow Reference

167 Qualify Chat flow The flow uses the following blocks to perform these functions: Step Block Name Description 4 Is the Customer Key Empty? 5 Fetch Customer Record Tests the Customer key in the Customer table to determine whether a record exists for the customer. If the Customer key does not exist, the flow proceeds to Step 8, Create Agent Desktop Data. Retrieves the specified values from the associated fields in the Customer record. To modify the values that the block retrieves from the Customer record, add or modify a pair of Field_N and Value_N parameters on the Basic tab. The field must correspond to a field in the Customer table. 6 NumRecords=1 Tests the NumRecords value set by the Fetch Customer Record block to see if the value is 1. If the answer is: Yes, the value is 1, proceeds to Step 7, Fetch EDU. No, the value is not 1, proceeds to Step 8, Create Agent Desktop Data. 7 Fetch EDU Fetches the EDU data again. The workflow can then use both the EDU data and the Customer data retrieved by the Fetch Customer Record block. 8 Create Agent Desktop Data Uses the EDU data and Customer data to create the data that Avaya Agent and other agent desktop applications use for screen pops. If the Fetch Customer Record block found more than one Customer record, or no Customer records, this block uses only the values in the EDU. Issue 3.0 July

168 Chat contact routing flows Customer preferences This group of blocks adds the language selected by the customer on the Website as a routing hint, and determines whether the customer record includes a preferred agent, as shown in the following figure The flow uses the following blocks to perform these functions: Step Block Name Description 9 Add routing hints Adds a routing hint for language to the collection of routing hints for the chat contact. The language routing hint is set when the customer selects a language on the Website. 10 Is Preferred Agent Empty? Tests the customer record to see if the record contains a value for Preferred Agent. If the Preferred Agent is: Empty, the customer has no preferred agent, and the workflow continues with Step 11, Fetch Routing Hints (chat). Not empty, the customer has a preferred agent, and the workflow omits Steps 11 through 14 and continues with Step 15, Set route parameters. 168 Media Workflow Reference

169 Qualify Chat flow Routing hints This group of blocks uses the routing hints from the EDU to determine which agent or queue should receive the contact, as shown in the following figure The flow uses the following blocks to perform these functions: Step Block Name Description 11 Fetch Routing Hints (chat) 12 ivchatenabled?? media=ivchat pvchatenabled?? media=pvchat 1. Uses the routinghint.globalhint.n.hintvalue to fetch the intent routing hint for the chat contact that was associated with the Web pages the customer visited. 2. Adds the value of the intent routing hint to the $scroutinghints script variable. A series of blocks which tests the following EDU fields to determine whether the customer would like to have a Voice Chat with an agent: ivchatenabled pvchatenabled media Issue 3.0 July

170 Chat contact routing flows Step Block Name Description 13 Add routing hints Adds a routing hint for a Voice Chat to the collection of routing hints for the chat contact, as follows: If ivchatenabled = true and media = ivchat, the blocks add the routing hint media=ivchat for a Chat & VOIP contact. If pvchatenabled = true and media=pvchat, the blocks add the routing hint media = pvchat for a Chat & Phone callback. 14 Map Hints to Queue 1. Maps the hints collected in the $scroutinghints script variable to a routing hint in the RoutingHint table of the Directory server. 2. Uses the routing hints to identify a queue to which the contact should be routed. For example, if the chat contact contains hints with the values sales and computers, the flow uses these values to filter all entries in the RoutingHint table and to route the contact to the chat queue for sales of computers. Route parameters and wait treatments This group of blocks sets the route parameters for the contact and assigns one or more wait treatments to the contact, as shown in the following figure Media Workflow Reference

171 Qualify Chat flow The flow uses the following blocks to perform these functions: Step Block Name Description 15 Set route parameters 16 Set Chat Wait Treatment Retrieves and sets values for the following properties: Name of the preferred agent Default chat queue Default workgroup for the chat queue Priority of the chat in the queue Sets the pkey queue of the queue where the flow routes the chat contact so that Avaya IC can collect statistics for the contact. This pkey is set to 0 if the flow routes the contact to a preferred agent. You can specify values for the properties in the Basic tab. Use a series of Set Chat Wait Treatment blocks to create a script with a sequence of Say Text messages and Web pages that the workflow pushes to customers in queue. To use this block, set the following properties on the Basic tab: PushURL URL of Web page displayed to customers SayText Message displayed to customer (for example, "Wait") WaitTime Length of time the workflow waits to display the wait treatment sequence. Complete chat qualification This block transfers the chat contact to an agent or device, as shown in the following figure. 17 The flow uses the following block to perform this function: Step Block Name Description 17 Complete Qualification Calls the WebACD server with the routing information collected by the workflow, including the value of the queue set by the Map Hints to Queue block and the Chat Wait Treatment. Issue 3.0 July

172 Chat contact routing flows Stop flow The Stop block marks the exit point for the workflow. After the Stop block, the Workflow server executes the On Exit block. 172 Media Workflow Reference

173 IV Chat flow Chapter 6: Voice chat contact routing flows Avaya IC uses voice chat contact routing flows to route chat contacts that an agent or customer decides to conduct as a voice chat contact. The voice chat flows route the chat contact to the voice channel and create a hub EDU that links the EDU for the chat contact with the EDU for the voice contact. This section describes the voice chat contact routing flows provided with Avaya IC. The sample voice chat flows include: IV Chat flow on page 173. Incoming IV Chat flow on page 176. IV Chat flow If a customer or an agent decides to conduct all or part of a chat contact with Voice Chat, Web Agent issues a servlet that invokes the IV Chat flow. This workflow performs the following tasks: Gathers the values that the Incoming IV Chat flow needs to route the IV chat contact. Sets the value in the EDU that identifies the chat contact as an IV chat. Issue 3.0 July

174 Voice chat contact routing flows The sample IV Chat flow is shown in the following figure The steps of the sample IV Chat flow use the following blocks: Step Block Name Description Start Flow 1 Get ADU from Agent Login ID Starts the workflow. Incorporates the code for getting a unique database network session for database access through its DBNetwork property. Retrieves the ADU record associated with the agent s login ID. The flow uses the ADU to select the proper gateway for the IV chat contact. 2 DS Get VMM List Retrieves a list of active Voice Media Managers (VMMs) from the Directory server. 3 Raise Alarm Raises an alarm if there are no active VMMs, then exits the flow through the Stop block. 174 Media Workflow Reference

175 IV Chat flow Step Block Name Description 4 VMM Round Robin Selection 5 DS Get Gateway List 1. Checks the global variable for the last VMM to determine which VMM was returned first for the previous IV Chat contact. 2. Determines the active VMM to which the flow should first route the current contact. For example, if your system has 2 VMMs, and the flow returned VMM1, VMM2 for the previous IV chat contact, the flow returns VMM2, VMM1 for the current contact. The Workflow server maintains a global variable for the last VMM. If the Workflow server stops, this value is reset. 3. Retrieves a list of active gateways from the Directory server. The active gateways must be in the same ACD as the agent. 4. Generates the ivchattochat key which the flow stores in the EDU, then passes in the ANI field of the Incoming IV Chat flow. 6 Raise Alarm Raises an alarm if there are no active gateways, then exits the flow through the Stop block. 7 Gateway Round Robin Selection 5. Sets a global variable for the active gateways to determine: - Current load on each gateway - Total number of IV chats 6. Determines the gateway to which the flow should first route the IV chat contact. The flow bases this decision on the values in the global variable and the list of active gateways The Workflow server maintains the global variable for the gateways. If the Workflow server stops, this value is reset. 8 Set EDU Sets the value of the ivchattochat key in the ivchat Agent field of the EDU. This value identifies this EDU as a chat for the IV Chat session. The flow passes this value in the ANI field of the Incoming IV Chat flow. 9 Write EDU Writes the value set in Step 8. Issue 3.0 July

176 Voice chat contact routing flows Step Block Name Description 10 Set Output Parameters Stop Returns a SeqCouple which includes: List of gateways where the flow can route the IV chat contact List of VMMs where the flow can route the IV chat contact The SeqCouple contains the following values: Generic Value Timeout MaxGatewayToTry ivchattochatkey For each gateway, the output includes the following values: IPAddress Port RoutePoint For each VMM, the output includes the following values: IPAddress Port Ends the workflow. Incoming IV Chat flow All IV Chat contacts start out as chat contacts. Therefore, an IV Chat contact has two EDUs: Chat EDU from the initial contact with the agent through a chat request Voice EDU when the IV Chat request routes the contact to the agent s telephone The Incoming IV Chat flow routes an incoming IV chat contact. This flow retrieves an EDU for the voice contact, then finds the EDU for the chat task, and links the two EDUs as related tasks. 176 Media Workflow Reference

177 Incoming IV Chat flow The sample Incoming IV Chat flow is shown in the following figure The steps of the sample IV Chat flow use the following blocks: 2 Step Block Name Description Start Flow 1 Find Chat EDU based on ivchattochat key Starts the workflow. Incorporates the code for getting a unique database network session for database access through its DBNetwork property. Retrieves the chat EDU created when the IV Chat contact first entered the Avaya IC system as a chat contact. 2 Link EDUs 1. Links the voice EDU for the IV Chat contact with the chat EDU for the chat contact. 2. Creates a hub EDU. 3 Set EDU Sets a value of the voice EDU as a related task of the chat EDU. 4 Write EDU Writes the related task value to the voice EDU record. 5 Set EDU Sets a value of the chat EDU as a related task of the voice EDU. 6 Write EDU Writes the related task value to the chat EDU record. Issue 3.0 July

178 Voice chat contact routing flows Step Block Name Description 7 Transfer Call Transfers the IV Chat contact to the agent who originally received the chat contact. Stop Ends the workflow. 178 Media Workflow Reference

179 Prerequisites for the Qualify flow Chapter 7: contact routing flows Avaya IC uses contact routing flows to route contacts. This section describes the sample contact routing flow provided with Avaya IC. Topics include: Prerequisites for the Qualify flow on page 179. Customization of the Qualify flow on page 180. Qualify flow on page 180. Note: Note: If your Avaya IC system uses Business Advocate to route voice contacts, use the contact routing flows for Business Advocate. For more information, see Qualify flow for Business Advocate on page 281. Prerequisites for the Qualify flow For the Qualify flow to run: 1. Create routing hints in the RoutingHints table of the Directory server. 2. Create at least one queue for the Avaya IC site that hosts the WebACD server. 3. Set the property Site for the WebACD server in IC Manager. 4. Configure the channel and association in the Workflow server. 5. Configure the Workflow server to use the Web Routing flow update_qw_cache as a synchronous startup flow. This flow creates the global variables that associate queues to workgroups. For more information about how to perform the steps in IC Manager, see IC Administration Volume 1: Servers & Domains. Issue 3.0 July

180 contact routing flows Customization of the Qualify flow You can customize the Qualify flow by modifying the properties of blocks in the workflow. You can modify the values for the properties of blocks in this workflow, if you want to route contacts to a particular queue or a particular agent. You can base the decision to route an contact to a particular agent or queue on the value of any of the elements of the EDU data, such as the To address. For example, you can modify the value of the DefaultQueueID property in the Map Hints to Queue block. When you modify this property, you change the queue that the workflow uses if the block cannot match the contact to a queue through routing hints. Qualify flow The Qualify flow routes incoming contacts. A wacd.qualify event sent by the WACD server invokes this flow. 180 Media Workflow Reference

181 Qualify flow The sample Qualify flow is shown in the following figure. Group the blocks of the sample Qualify flow into several steps to see how the workflow processes an incoming chat contact. For example, this flow contains the following groups of blocks: 1. EDU values and input parameters on page Customer lookup on page Agent desktop data on page Preferred agent on page Routing hints on page qualification on page Stop Flow on page 187. Issue 3.0 July

182 contact routing flows EDU values and input parameters When Avaya IC receives an contact, the Workflow server starts the Qualify flow. The first group of blocks gets EDU values and input parameters for the contact, as shown in the following figure The flow uses the following blocks to perform these functions: Step Block Name Description Start Flow Starts the workflow. Incorporates the code for getting a unique database network session for database access through its DBNetwork property. 1 Fetch EDU Fetches the EDU that specified in the input argument from the wacd.qualify event that invoked the workflow. 2 Get EDU Values Retrieves values for the EDU attributes listed on the Basic tab. 3 Get Input Parameters Retrieves values for the input parameters listed on the Basic tab and enters the values in the specified symbols Customer lookup After the flow sets the initial parameters, the next group of blocks searches the Customer table in your database for information about the customer, as shown in the following figure Media Workflow Reference

183 Qualify flow The flow uses the following blocks to perform these functions: Step Block Name Description 4 CustomerFetched? Tests the Customer key in the Customer table to determine whether a record exists for the customer. If the Customer key does not exist, the flow proceeds to Step 8, Create Agent Desktop Data. 5 Fetch Customer Record Retrieves the specified values from the associated fields in the Customer record. To modify the values that the block retrieves from the Customer record, add or modify a pair of Field_N and Value_N parameters on the Basic tab. The field must correspond to a field in the Customer table. 6 RecordCount = 1 Tests the NumRecords value set by the Fetch Customer Record block to see if the value is 1. If the answer is: Yes, the value is 1, proceeds to Step 7, FetchEDU. No, the value is not 1, proceeds to Step 8, Create Agent Desktop Data. 7 FetchEDU Fetches the EDU data again. The workflow can then use both the EDU data and the Customer data retrieved by the Fetch Customer Record block. Agent desktop data After the flow searches the database, the next block creates the data required for Avaya Agent and other agent desktop applications, as shown in the following figure. 8 Issue 3.0 July

184 contact routing flows The flow uses the following blocks to perform these functions: Step Block Name Description 8 Create Agent Desktop Data Uses the EDU data and Customer data to create the data that Avaya Agent and other agent desktop applications use for screen pops. If the Fetch Customer Record block found more than one Customer record, or no Customer records, this block uses only the values in the EDU. Preferred agent After the flow sets the label and EDU fields for the contact, this block determines whether or not the customer record includes a preferred agent to handle all contacts from the customer, as shown in the following figure: 9 The flow uses the following block to perform these functions: Step Block Name Description 9 Is Preferred Agent Empty? Tests the preferredagentname field of the EDU to see if the record contains a value for Preferred Agent. This field normally has a value only when the contact is a customer reply to a request from an agent for more information. If the value of Preferred Agent is: Empty, proceeds to Step 10, Fetch Routing Hints (msgid) Includes an entry, proceeds to Step 17, Set Route Parameters Routing hints This group of blocks, shown in the following figure, checks the routing hints available for the contact and the type of the contact. Then, the group of blocks uses the intent 184 Media Workflow Reference

185 Qualify flow hint and the routing hints gathered in the Analysis workflows to determine which agent or queue should receive the contact. For more information about Analysis workflows, see Analysis flows on page The flow uses the following blocks to perform these functions: Step Block Name Description 10 Fetch Routing Hints (msgid) 1. Uses the msgid to fetch the hints identified in the analysis flow. 2. Adds them to the $scroutinghints script variable. 11 Type = SUP Tests the EDU to determine if the type of the contact is SUP. An type of SUP, indicates that the contact is an outbound in response to a customer contact. If the type is: SUP, proceeds to Step 12, Fetch Routing Hints (rootmsgid) Not SUP, proceeds to Step 12, Found Routing Hints? 12 Fetch Routing Hints (rootmsgid) If the type of the contact is SUP: Uses the rootmsgid from the contact to fetch the collection of routing hints from the original contact. Adds those routing hints to the collection of routing hints for the current outbound in the $scroutinghints script variable. Typically, this collection already includes a hint of QA=approvalrequired or QA=suspectcontent. After this step is complete, the flow proceeds to Step 15, Map Hints to Queue. Issue 3.0 July

186 contact routing flows Step Block Name Description 13 Found Routing Hints? Tests whether the value of HintsAvailable is Yes. If the value is: Yes, proceeds to Step 16, Map Hints to Queue No, proceeds to Step 14, Add Routing Hints 14 Add Routing Hints Adds the value of the To Address field in the contact to the collection of routing hints in the $scroutinghints script variable. The workflow uses this block if no other routing hints exist for the contact. For example, no routing hints would exist if an analysis flows was not run for this contact. Therefore, this block makes sure that the contact has at least one routing hint to determine the correct queue for the contact. 15 Map Hints to Queue If type is SUP or the analysis flow did not associate routing hints with the contact, the $scroutinghints script variable contains either the routing hints from the original contact, or the value of the To Address field. With these routing hints, the workflow uses this block to: 1. Map the hints collected in the $scroutinghints script variable to a routing hint in the RoutingHint table of the Directory server. 2. Use the routing hints to identify a queue to which the contact should be routed. 16 Map Hints to Queue If type is not SUP and the analysis flow associated routing hints with the contact, the $scroutinghints script variable contains the routing hints from the analysis. With these routing hints, the workflow uses this block to: 1. Map the hints collected in the $scroutinghints script variable to a routing hint in the RoutingHint table of the Directory server. 2. Use the routing hints to identify a queue to which the contact should be routed. 186 Media Workflow Reference

187 Qualify flow qualification This group of blocks, shown in the following figure, sets the route parameters for the WebACD server, then transfers control of the contact back to the WebACD server for routing to an agent or device The flow uses the following block to perform this function: Step Block Name Description 17 Set Route Parameters 18 Complete Qualification Uses the following parameters to create a script to route the contact: Name of preferred agent Pkey of the queue where the contact is to be routed Workgroups associated with the queue where the is to be routed Priority for queue to use for the contact Wait time for the contact in the queue Note: If the is to be routed to a preferred agent, the block can set the pkey of the queue to zero. Transfers control of the contact back to the WebACD server for routing to an agent or device. Stop Flow The Stop block marks the exit point for the workflow. After the Stop block, the Workflow server executes the On Exit block. Issue 3.0 July

188 contact routing flows 188 Media Workflow Reference

189 Types of Analysis flows Chapter 8: Analysis flows Avaya Interaction Center (Avaya IC) uses analysis flows to determine information about contacts that is useful to your contact center and execute actions based on that information. Avaya IC uses this information to correctly process contacts according to the business rules that you implement in your routing flows. This section describes how Avaya IC uses workflows to analyze and the sample Analysis flows provided with Avaya IC. Topics include: Types of Analysis flows on page 189. Customization of Analysis flows on page 193. Process of Analysis flows on page 195. Analyze with Keywords flow on page 196. Outbound with Keywords flow on page 207. Analyze with Content Analyzer flow on page 214. Outbound with Content Analyzer flow on page 224. Types of Analysis flows Your Management system can include a set of analyze and outbound analysis flows. Workflow Designer includes two sets of sample analysis flows. You only need to use one of these sets. The configuration of your Avaya IC system determines which set of analysis flows you use in your contact center. If desired, you can combine the two types of analysis in your contact center, and use one type for inbound contacts and the other type for outbound contacts. The following topics describe the two sets of sample analysis flows provided with Avaya IC: analysis with keywords on page analysis with Content Analyzer on page 190 Issue 3.0 July

190 Analysis flows analysis with keywords If your Avaya IC does not include Content Analyzer, you can analyze contacts with keywords. If your Avaya IC system does not include Content Analyzer, use the following sample flows that analyze contacts with keywords: Analyze with Keywords flow on page 196 Outbound with Keywords flow on page 207 analysis with Content Analyzer Avaya Content Analyzer (Content Analyzer) is an optional component of Avaya IC that analyzes the text of contacts to determine the intent of the sender. Content Analyzer is an intelligent way to classify an contact before routing to an agent or queue. If your Avaya IC system includes Content Analyzer, use the following sample flows to analyze contacts: Analyze with Content Analyzer flow on page 214 Outbound with Content Analyzer flow on page 224 This section describes Content Analyzer, how you can use the results from Content Analyzer in workflows, and the requirements for Content Analyzer. Topics include: Purpose of Content Analyzer on page 190. How to use results from Content Analyzer on page 191. Required components for Content Analyzer on page 191. Prerequisites for workflows with Content Analyzer on page 192. Purpose of Content Analyzer Content Analyzer helps your Avaya IC system achieve the following goals: Identify the primary language of an contact. Automatically respond to a significant number of contacts without agent interaction. Route contacts to the agent who is the best qualified to handle them. Assist agents by presenting a selection of suggested responses to the contact. Content Analyzer is more than keyword matching. It conducts linguistic analysis on the text of an contact and matches the concepts in the text to your pre-determined topics. As 190 Media Workflow Reference

191 Types of Analysis flows you continue to use Content Analyzer, you can conduct incremental training of the knowledge bases to improve accuracy and increase the percentage of contacts that receive automatic responses. How to use results from Content Analyzer You can use the results from Content Analyzer to perform one or more of the following functions: Make decisions within a workflow. For example, you can customize a workflow to use the results of Content Analyzer to make decisions based on: - The topic with the highest confidence factor - The value of the confidence factor for each returned topic - Whether there is a specific topic associated with the contact - The number of topics in the results Process contacts. For example, you can use the results of Content Analyzer to: - Select and send an automatic response to the customer from a series of pre-defined messages - Route the contact to a specific workgroup or agent with the appropriate skills to handle the topic, the language, or both - Provide a list of suggested responses for the agent to select Start an agent script flow to help the agent respond to the contact Screen the responses sent by agents to customers Required components for Content Analyzer Content Analyzer does not function properly if your system does not include all of the required components. Servers, including: - Content Analyzer Administration server - Content Analyzer Operation server - server - Workflow server Intelligent processing using workflows built in Workflow Designer Administration in IC Manager, including creation and maintenance of topic trees, sample sets, and knowledge bases. For more information, see IC Administration Volume 1: Servers & Domains. Issue 3.0 July

192 Analysis flows Prerequisites for workflows with Content Analyzer Before you customize workflows for Content Analyzer, you need to do the following in IC Manager: Create topic trees Create or define a set of samples associated with the topics Create a knowledge base Train (validate) the knowledge base with sample sets and save the trained knowledge base Configure a production Content Analyzer server with the trained knowledge base and start the server For more information, see IC Administration Volume 1: Servers & Domains. Purpose of Analysis flows analysis flows do not just analyze the content of contacts. These flows also implement other features. The following topics describe the features that you can implement for different types of contacts: Features to implement for inbound contacts on page 192. Features to implement for outbound contacts on page 193. Features to implement for inbound contacts analysis flows can implement the following features for inbound contacts: Customer identification Language identification Automatic acknowledgement of an contact Automatic response to an contact Suggested responses assist agents with the reply to an contact Routing hints that help the servers route contacts to the appropriate agent or queue screening to filter out junk mail 192 Media Workflow Reference

193 Customization of Analysis flows Features to implement for outbound contacts analysis flows can implement the following features for outbound contacts: screening to identify objectionable content Quality assurance to let supervisors review some or all outbound contacts File attachments to add standard attachments to all outbound contacts Additional addresses to route copies of all outbound contacts to internal or external recipients Alerts to notify agents if a response is not received in the specified time Customization of Analysis flows You can customize the sample analysis flows by modifying the properties of blocks in the workflow. You can modify the values for the properties of blocks in this workflow, if you want to route contacts to a particular queue or a particular agent. This section includes the following topics with examples of how to customize an analysis flow: Adding routing hints on page 193. Modifying block properties on page 194. Adding blocks on page 194. Detecting loops on page 194. Adding routing hints Add more routing hints with the Set Routing Hint block so that the appropriate queues are found in the RoutingHint table. For more information about setting up routing hints, see Chat contact routing flows on page 159. Issue 3.0 July

194 Analysis flows Modifying block properties You can customize the analysis flows by modifying the properties of blocks in the workflow. For example, you can set the properties of the following blocks to route the contact according to custom logic: - Route block - Auto Response block - Dismiss block - Bounce block Adding blocks You can add blocks to the analyze flow to retrieve contacts from the task list of a customer s preferred agent. For example, add blocks that activate a timer and specify a backup agent. The contact can be queued to the backup agent if the preferred agent has not opened the contact before the timer expires. You can also raise the priority of the contact when it is queued to the backup agent. Tip: Tip: The customization of workflows can affect the performance of your Avaya IC system. Avaya recommends that you engage Avaya Professional Services for complex customization, such as the implementation of after hours logic. Detecting loops You can customize an analysis flow to work with the IC server to detect and prevent the loops that can be caused by automatic responses to templates sent automatically in response to queries. With this customization, the IC server will not automatically respond to or get into a loop if the recipient of an template response has an auto-response (such as an Out Of Office notification) configured for their account. To prevent an loop, you need to add a Test Data block to the analysis flow that compares the EDU value " count" with the desired loop count. If the value of " count" is less than the desired loop count, then the workflow moves to the Smart Auto Ack block, and responds with an template. If the value of " count" is greater than or equal to the desired loop count, then the workflow bypasses the Smart Auto Ack block. 194 Media Workflow Reference

195 Process of Analysis flows To customize an analysis flow to avoid loops: 1. Modify the Get EDU Values block to retrieve the value of " count" from the EDU and store it in a script variable such as $ Count 2. Add a Test Data block to the workflow before the Smart Auto Ack block. Configure the Test Data block as follows: a. On the Basic tab of this block, set the following values: valuetocompare property to the desired loop count. WhatToTest property to the script variable set for " count" in the Get EDU Values block. Operator property to >= b. Use two output connectors: One to the Smart Auto Ack block if the count is less than the desired loop count. One to the block following the Smart Auto Ack block if the count is greater than or equal to the desired loop count. After you customize the analysis flow, configure the IC server for message loops. For more information, see IC Administration Volume 1: Servers & Domains. Process of Analysis flows You can use analysis flows on inbound and outbound contacts. analysis begins when an contact reaches the server: 1. When the server receives an contact, the server checks its Run Analyze Flow property: If you have enabled this property, the server issues an Analyze event, then the Workflow server invokes whichever of the following analyze flows that you specified in the server configuration: - Analyzenoca If the Avaya IC configuration uses analysis with keywords - Analyzeca If the Avaya IC configuration uses Content Analyzer If you have not enabled this property, the server passes the contact to the WebACD server (go to Step 5). You set the Run Analyze Flow property on the Analysis tab of the server in IC Manager. For more information, see IC Administration Volume 1: Servers & Domains. Issue 3.0 July

196 Analysis flows 2. The analyze flow analyzes the text in the contact according to the rules that you set up in the flow. The flow performs several functions, such as inserting routing hints into the qw_qualifier table in your IC Repository database. 3. When the analyze flow completes, the flow invokes the method IC .Analyzed, which returns control of the contact to the server. 4. The server processes the contact, then passes the to the WebACD server. 5. When the WebACD server receives the contact, the server issues a qualify event. 6. The qualify event invokes the Qualify flow. For more information about the Qualify flow, see Qualify flow on page When the Qualify flow completes, the flow returns control of the contact to the WebACD server. 8. When the WebACD server receives the contact, the server routes the contact to the receiver determined by the Qualify flow, such as: The preferred agent The preferred queue! CAUTION: CAUTION: analysis flows should not make requests to the Workflow server that runs the flow. Use script.start to start a flow. Analyze with Keywords flow The sample Analyze with Keywords flow is analyzenoca.qfd. This flow: Identifies attributes of incoming contacts Attempts to set a route disposition, such as dismiss or bounce Sets routing hints if none of these route dispositions are appropriate Searches the Web Self-Service knowledge base and assigns a context-sensitive acknowledgment template Returns control of the contact to the server for routing For this flow, the routing hints are keywords in the subject line of the , such as the name of a product. You can customize the flow to check any field in the , including the body. The Qualify flow uses the routing hints to determine where to route the contact. 196 Media Workflow Reference

197 Analyze with Keywords flow The server invokes the Analyze with Keywords flow if you specify this flow in the Run Analyze Flow property of the server. The sample Analyze with Keywords flow is shown in the following figure. The Analyze with Keywords flow is relatively complex. However, you can group the blocks into several steps to see what the flow does with an incoming contact. For example, this flow contains the following groups of blocks: 1. EDU values and input parameters on page type on page analysis on page Routing hints on page Suggest responses on page Route disposition on page analyzed on page Stop flow on page 207. Issue 3.0 July

198 Analysis flows You must modify the properties of some of these blocks to customize the workflow to set the routing hints and route dispositions that meet your contact center s needs. EDU values and input parameters The first group of blocks in this flow gets EDU values and input parameters for the contact. The flow uses the following blocks to perform these functions. Step Block Name Description Start Flow Starts the workflow. 1 Fetch EDU Fetches the EDU from the EDU server based on the current EDUID. 2 Get EDU Values Retrieves values for the EDU attributes listed on the Basic tab. 3 Get Input Parameters Retrieves values for the input parameters listed on the Basic tab and enters the values in the specified symbols type This group of blocks tests the EDU of the contact for the following types: NOR New inbound contact REQ Customer or external agent reply to an agent s request for more information RPL Customer or external agent reply to an agent s earlier response OUT Outbound contact 198 Media Workflow Reference

199 Analyze with Keywords flow The following figure shows this group of blocks The flow uses the following blocks to perform these functions: Step Block Name Description 4 Type = NOR Tests the EDU to determine if the type of the contact is NOR. If the type is NOR, proceeds to Step 8, Keyword Search Type = REQ Tests the EDU to determine if the type of the contact is REQ. If the type is REQ, proceeds to Step 16, Smart AutoAck. 6 Type = RPL Tests the EDU to determine if the type of the contact is RPL. If the type is RPL, proceeds to Step 16, Smart AutoAck. 7 Type = OUT Tests the EDU to determine if the type of the contact is OUT. If the type is OUT, proceeds to Step 16, Smart AutoAck. analysis This group of blocks analyzes the text in the contact. The sample flow analyzes text in the subject line of the contact. You can configure the flow to search another field in contacts, such as the body, To, or From. This group also determines whether the contact originated from the customer Web site. If the contact did originate from the Web site, the flow retrieves the customer key from the Customer record. For example, if a customer requests a fax response from the Web site, Avaya IC inserts a dummy address in the From field of the that requests the fax. This flow, Issue 3.0 July

200 Analysis flows therefore, uses the customer s registration information to retrieve the customer s fax number and related information from the database. The group of blocks that performs analysis is shown in the following figure Media Workflow Reference

201 Analyze with Keywords flow The flow uses the following blocks to perform these functions. You must match the keywords that you specify in the Keyword Search 3 block with values in Set Routing Hints blocks. Step Block Name Description 8 Keyword Search 1 Filters out junk mail. This block searches the subject line for the keyword that you specify in the Basic tab. For example, you can configure the block to search for a valid regular expression, such as the phrase "You ve won", in the subject line of contacts. If the keyword is: In the text Flow proceeds to Step 17, Bounce, and bounces the Not in the text Flow proceeds to Step 9, WebSite ? Note: You can only use this block to search for one valid regular expression in one field of the contact. You can add additional Keyword Search 1 blocks to search for another expression or for the same expression in a different field of the contact. 9 WebSite ? Tests whether the contact originated from the customer Web site. This block checks the header of the contact to determine whether the X-AIC flag variable is set to true. This variable is populated from the current .header.x-aic field. If that value is: True came from the Web site. Flow proceeds to Step 11, AICCustKey= NULL? False did not come from the Web site. Flow proceeds to Step 10, Fetch Customer Record 10 Fetch Customer Record 11 AICCustKey= NULL? Determines whether the sender is a known customer. If the sender is a known customer, retrieves the record from the CCQ database and inserts it in the customerinfo container of the EDU. When the customer record is retrieved, proceeds to Step 13, Keyword Search 3 Tests whether the value of the script variable AICCustKey is NULL. That value is assigned from the EDU field current .header.x-aiccustomerkey If the value is NULL, the came from a guest user at the Web site. Flow proceeds to Step 10, Fetch Customer Record. If the value is not NULL, the came from a registered user at the Web site. Flow proceeds to Step 12, Fetch Customer Record. Issue 3.0 July

202 Analysis flows Step Block Name Description 12 Fetch Customer Record Determines whether the sender is a known customer. If the sender is a known customer, retrieves the record from the CCQ database and inserts it in the EDU. 13 Keyword Search 3 Looks for the specified keywords in the subject line of the . For example, if you specify "printers" as the value for SearchPattern1, the block routes the contact to a Set Routing Hint block that has a value of Printers. If the keywords are: In the text Flow proceeds to Step 14, Set Routing Hints Not in the text Flow proceeds to Step 19, Route, to set the route disposition Note: You can specify up three keywords in one field of the contact. You can add additional Keyword Search 3 blocks to search for additional keywords or for the same keywords in a different field of the contact. Routing hints This group of blocks sets a value in the $scroutinghints script variable and creates a record in the qw_qualifier table for the value of the keyword found in Step 13, Keyword Search 3. The sample flow includes two Set Routing Hint blocks, as shown in the following figure. This flow must have a Set Routing Hint block for each keyword value in the Keyword Search block at Step Media Workflow Reference

203 Analyze with Keywords flow The flow uses one or more of the following blocks to perform this function. Modify the Value property on the Basic tab of each block to match one of the keywords in the Keyword Search block at Step 13. Step Block Name Description 14 Set Routing Hints Sets a value in the $scroutinghints script variable for the keyword found in Step 13 and saves the name and value of the routing hint in the qw_qualifier table of the CCQ database. To use this block, set the following properties in the Basic tab: RoutingHintField The name of the routing hint. Value The value to set in the routing hint field. Suggest responses This group of blocks, shown in the following figure: Searches the Web Self-Service knowledge base for topics that match the keywords Assigns a context-sensitive template for the response Create and maintain response templates in the Template Administration in IC Manager. For more information, see IC Administration Volume 1: Servers & Domains Issue 3.0 July

204 Analysis flows The flow uses the following blocks to perform this function. Step Block Name Description 15 Get Suggested Response Queries Web Self-Service with the keywords for suggested responses on that subject. To use this block, set the following properties: Basic tab: - Language The language to use for the query. Must be a two character ISO language code. If you do not set this field, the block uses en for English. - MaxDocs Maximum number of suggested responses to return. - MaxDocSize Maximum size in Kilobytes of the suggested responses to return. This property filters out responses that are larger than the maximum size. When this happens, the Alarm monitor displays an alarm, and the information is added to the WebACD server log file. - MinScore Minimum confidence score for all returned suggested responses. The query will not return any responses with a lower confidence score. Advanced tab: - AdditionalKeywords Enter additional keywords to use in the search. - TopicList Enter a script variable to hold results returned from the search for suggested responses. - UseRoutingHints Set to true to use the keywords from the Set Routing Hints block. - UseTopicListKeywords Set to false. - UseTopicListTopicPath Set to false. 204 Media Workflow Reference

205 Analyze with Keywords flow Step Block Name Description 16 Smart AutoAck The flow contains two SmartAutoAck blocks. One works with contacts with REQ, RPL, and OUT types at Steps 5, 6, and 7. The other follows the Get Suggested Response block in Step Specifies a response template for Auto Acknowledgement. 2. Checks the response template and the language encoding of the contact against the qem_template table for a match. - If there is a match, sets the pkey of the record from the qem_template table in the EDU field rlm_pkey. - If there is no match, makes another attempt with the value specified in the DefaultEncoding property if that value is different. - If there is still no match, sets a default of 0. To use this block, set the following properties: Basic tab: - TemplateName Name of the Response Template to use Advanced tab: - DefaultEncoding Default language encoding to use for the response template After this block, the flow proceeds to Step 19, Route. Route disposition The next group of blocks in the flow, shown in the following figure, sets the route disposition for the contacts. These blocks are not consecutive in the flow, but they perform similar functions for different types of contacts Issue 3.0 July

206 Analysis flows The flow uses the following blocks to perform this function. Step Block Name Description 17 Bounce Sets a route disposition of Bounce, as a result of the keyword search in Step 8, Keyword Search 1. To use this block, set the following properties in the Basic tab: BounceReason Status ID that represents a reason to include in the text, such as "no such recipient". ForwardAddress An address that should receive a copy of the bounce message that is returned to the sender (optional). TemplateName Name of the Response Template to use. After this block, the flow proceeds to Step 20, IC Analyzed. 18 Dismiss Sets a route disposition of Dismiss. To use this block, set the following properties in the Basic tab: ResolveWithStatus Status ID that represents a reason to include in the text, such as "no such recipient". ForwardAddress An address that should receive a copy of the bounce message that is returned to the sender (optional) After this block, the flow proceeds to Step 20, IC Analyzed. 19 Route Sets a route disposition of Route: To use this block, set the following properties: Basic tab: - ForwardAddress An address that should receive a copy of the contact (optional) Advanced tab: - RouteResponseToIntendedAgent If the value is set to true, the Route disposition overrides any previous setting of the Script.variable.routeresponsetoagent variable set by the server Tip: Tip: Use Template Administration in IC Manager to configure the text that matches the status ID for the ResolveWithStatus and BounceReason properties. For more information, see IC Administration Volume 1: Servers & Domains. 206 Media Workflow Reference

207 Outbound with Keywords flow analyzed This block in the flow, shown in the following figure, notifies the server that the Analyze with Keywords flow is complete. 20 The flow uses the following block to perform this function. Step Block Name Description 20 IC Analyzed Saves the values from the $scroutinghints script variable into the qw_qualifier table Invokes the IC .Analyzed method to notify the server that the Analyze with Keywords flow is complete Stop flow The Stop block marks the exit point for the workflow. After the Stop block, the Workflow server executes the On Exit block. Outbound with Keywords flow The sample Outbound with Keywords flow is outboundnoca.qfd. The server invokes the Outbound with Keywords flow for outbound contacts if you specify this flow in the Run Outbound Flow property of the server. The Outbound with Keywords flow provides post-processing for outbound contacts. For example, this flow specifies outbound contacts that need to be routed to a supervisor for approval before they are sent to the recipient. The Qualify flow uses the routing hints gathered by the Outbound with Keywords flow to determine how to route the contact. Issue 3.0 July

208 Analysis flows The sample Outbound with Keywords flow is shown in the following figure. You can group the blocks of the Outbound with Keywords flow into several steps to see what the flow does with an outbound contact. For example, this flow contains the following groups of blocks: 1. EDU values and input parameters on page type on page Set alert on page components on page Approval by supervisor on page Outbound response on page Stop flow on page 214. You must modify the properties of some of these blocks to customize the workflow to set the routing hints and route dispositions that meet your contact center s needs. 208 Media Workflow Reference

209 Outbound with Keywords flow EDU values and input parameters The first group of blocks in this flow gets EDU values and input parameters for the contact. The flow uses the following blocks to perform these functions: Step Block Name Description Start Flow Starts the workflow. Incorporates the code for getting a unique database network session for database access through its DBNetwork property. 1 Fetch EDU Fetches the EDU from the EDU server based on the current EDUID. 2 Get EDU Values Retrieves values for the EDU attributes listed on the Basic tab. 3 Get Input Parameters Retrieves values for the input parameters listed on the Basic tab and enters the values in the specified symbols type This group of blocks tests the EDU of the contact for the following types: NOR New outbound contact REQ Customer or external agent reply to an agent s request for more information SME contact from a subject matter expert or another person who has been designated as an external agent The following figure shows this group of blocks Issue 3.0 July

210 Analysis flows The flow uses the following blocks to perform these functions: Step Block Name Description 4 Reply Type = SME Tests the EDU to determine if the reply type of the contact is SME. If the reply type is SME, proceeds to Step 7, Set Alert. 5 Reply Type = REQ Tests the EDU to determine if the reply type of the contact is REQ. If the reply type is REQ, proceeds to Step 7, Set Alert. If the reply type is not REQ, proceeds to Step 10, Get Agent Quota. 6 Reply Type = NOR Tests the EDU to determine if the reply type of the contact is NOR. If the reply type is NOR, proceeds to Step 9, Add Component. If the reply type is none of the above, proceeds to Step 10, Get Agent Quota. Set alert This block, shown in the following figure, sets an alert in the Notification server. The alert reminds the agent who sent the outbound if no response is received within the number of hours or days specified in this block Media Workflow Reference

211 Outbound with Keywords flow The flow uses the following block to perform this function: Step Block Name Description 7 Set Alert Sets an alert in the Notification server to send a notification to an agent who requested SME help within a specified time period. The alert is not sent if the agent receives a response from the SME within the time period specified on the Basic tab. To use this block, set the following properties: In the Basic tab: - DelayDuration A choice of Minute, Hour, and Day. If you do not specify a duration, the default is Minute. - DelayLength The length of the delay that the Notification server waits to send the alert. For example, if you select Hour for DelayDuration and 3 for DelayLength, the Notification server will send an alert in 3 hours. In the Advanced tab: - vdudata A sequence of couples that contains the contents of the current EDU. You must set this value to the variable in the IC Script that contains the contents of the current EDU. You must assign the same value as you did to the vdudata property in Step 2, Get EDU Values block. 8 Set Alert Failed? 1. Tests to make sure that the notification was set. 2. If the attempt to set the notification failed: - The block raises an alarm. - The workflow exits without returning to the server. - The server reruns the workflow and continues these attempts until the problem with the Notification server has been corrected and the workflow can complete. components This block, shown in the following figure, adds file attachments and addresses for additional recipients to outbound . 9 Issue 3.0 July

212 Analysis flows The flow uses the following block to perform this function: Step Block Name Description 9 Add Component Specifies attachments and additional recipients for the outbound contact. If you want to add more than one address to a field or more than one attachment, separate the entries with semicolons. To use this block, set the following properties in the Basic tab: BCC Addresses Adds addresses to the BCC field To Addresses Adds addresses to the To field CC Addresses Adds addresses to the CC field FileAttachments Adds these attachments to the outbound . To include an attachment: - Store the file on the machine that hosts the Workflow server - Specify the full directory path of each file Approval by supervisor This group of blocks, shown in the following figure, determines whether the outbound needs to be sent to a supervisor for approval before the is sent to the recipient Media Workflow Reference

213 Outbound with Keywords flow The flow uses the following blocks to perform these functions: Step Block Name Description 10 Get Agent Quota 1. Retrieves the value of the ReviewQuota property from the agent s profile, then saves the value in the script variable qaquotavalue. If there is no value, uses the value in the DefaultQuotaValue property of this block. 2. Generates a random number between 1 and 100, then saves the value in the script variable currentquotascore. To use this block, set the following property in the Basic tab: DefaultQuotaValue Default quota value to use if none is found for the agent. 11 QA Quota? Compares the script variables qaquotavalue and currentquotascore to determine whether the outbound needs to be forwarded to a supervisor for approval. If the answer is no, proceeds to Step 13, IC Outbound Response. If the answer is yes, proceeds to Step 12, Set Routing Hint. 12 Set Routing Hint (approvalrequired) Sets the approvalrequired routing hint to true and saves the name of QA and value of approval required in the qw_qualifier table of the CCQ database. To use this block, set the following properties in the Basic tab: RoutingHintField The name of the routing hint. Value The value to set in the routing hint field. Outbound response This block, shown in the following figure, notifies the server that the Outbound with Keywords flow is complete. 13 Issue 3.0 July

214 Analysis flows The flow uses the following block to perform this function: Step Block Name Description 13 IC Outbound Response Invokes the IC .OutboundResponse method to notify the server that the Outbound with Keywords flow is complete. Stop flow The Stop block marks the exit point for the workflow. After the Stop block, the Workflow server executes the On Exit block. Analyze with Content Analyzer flow The sample Analyze with Content Analyzer flow is analyzeca.qfd. For each incoming contact, the Analyze with Content Analyzer flow performs the following steps: 1. Analyzes text in an contact. The sample flow analyzes text in the body field of an contact. You can configure the flow to analyze another field. Content Analyzer does not analyze the content of attachments to contacts, whether or not the attachments contain text. 2. Identifies the language in which the contact is written. For a list of supported languages, see IC Installation Planning and Prerequisites. 3. Classify the text, through service call to Content Analyzer, to one or more predefined topics with text-to-topic matching likelihood scores. This score represents the percentage likelihood (or confidence factor) that the text and the intent of the contact belongs to that topic. 4. Uses the score and the training that you give Content Analyzer to determine how the intent of the contact matches your pre-defined topics. 5. Outputs a list of topics that match the text of the contact, and a confidence factor for each topic, then stores the topics in the EDU. 6. Returns control of the contact to server for routing. 214 Media Workflow Reference

215 Analyze with Content Analyzer flow The sample Analyze with Content Analyzer flow is shown in the following figure. The Analyze with Content Analyzer flow is relatively complex. However, you can group the blocks into several steps to see what the flow does with an incoming contact. For example, this flow contains the following groups of blocks: 1. EDU values and input parameters on page type on page Test for Website on page analysis with Content Analyzer on page Test category on page Routing hints on page Route disposition on page analyzed on page Stop flow on page 224. Issue 3.0 July

216 Analysis flows EDU values and input parameters The first group of blocks in this flow gets EDU values and input parameters for the contact. The flow uses the following blocks to perform these functions: Step Block Name Description Start Flow Starts the workflow. 1 Fetch EDU Fetches the EDU from the EDU server based on the current EDUID. 2 Get EDU Values Retrieves values for the EDU attributes listed on the Basic tab. 3 Get Input Parameters Retrieves values for the input parameters listed on the Basic tab and enters the values in the specified symbols type This block tests the EDU of the contact for an type of NOR New inbound contact. The following figure shows this block. 4 The flow uses the following blocks to perform these functions: Step Block Name Description 4 Type = NOR Tests the EDU to determine if the type of the contact is NOR. The block ignores other types as they do not relate to new inbound contacts. If the type is: NOR, proceeds to Step 5, WebSite ?. Not NOR, proceeds to Step 14, Route. 216 Media Workflow Reference

217 Analyze with Content Analyzer flow Test for Website This group of blocks, shown in the following figure, determines whether the contact originated from the customer Web site. If the contact did originate from the Web site, the flow retrieves the customer key from the Customer record. For example, if a customer requests a fax response from the Web site, Avaya IC inserts a dummy address in the From field of the that requests the fax. This flow, therefore, uses the customer s registration information to retrieve the customer s fax number and related information from the database The flow uses the following blocks to perform these functions. Step Block Name Description 5 WebSite ? Tests whether the contact originated from the customer Web site. This block checks the header of the contact to determine whether the X-AIC flag variable is set to true. This variable is populated from the current .header.x-aic field. If that value is: True came from the Web site. Flow proceeds to Step 7, AICCustKey=NULL? False did not come from the Web site. Flow proceeds to Step 6, Fetch Customer Record 6 Fetch Customer Record Determines whether the sender is a known customer. If the sender is a known customer, retrieves the record from the CCQ database and inserts it in the customerinfo container of the EDU. When the customer record is retrieved, proceeds to Step 9, Get Language Issue 3.0 July

218 Analysis flows Step Block Name Description 7 AICCustKey=NULL? 8 Fetch Customer Record Tests whether the value of the script variable AICCustKey is NULL. That value is assigned from the EDU field current .header.x-aiccustomerkey If the value is NULL, the came from a guest user at the Web site. Flow proceeds to Step 6, Fetch Customer Record. If the value is not NULL, the came from a registered user at the Web site. Flow proceeds to Step 8, Fetch Customer Record Uses the value of AICCustKey to fetch the customer record from the database and inserts it into the customerinfo container in the EDU. The value of AICCustKey is the pkey of the customer record. analysis with Content Analyzer This group of blocks, shown in the following figure, analyzes the content of the with Content Analyzer Media Workflow Reference

219 Analyze with Content Analyzer flow The flow uses the following blocks to perform these functions. Step Block Name Description 9 Get Language 1. Analyzes the text of the contact. 2. Determines the language of the with Content Analyzer 3. Sets a routing hint for the language in the $scroutinghints script variable. To use this block, set the following properties: Basic tab: - Server The server alias name. You must enter the alias name that you give the CA Operational server in IC Manager. Do not specify the alias for the CA Admin server. Advanced tab: - DefaultLanguage The default 2 character ISO language code to be used for language if Content Analyzer does not return a value. For example, enter en for English. 10 Get Matched Category Analyzes the body of the contact, retrieves a collection of categories and corresponding scores, then saves the results in the ca_result table of the CCQ database. To use this block, set the following properties: Basic tab: - DefaultLanguage Default 2 character ISO language code to be used for language if Content Analyzer does not return a value. For example, enter en for English. - FieldToAnalyze Name of the script variable that holds the body. - KBName Name of the Content Analyzer knowledge base to use. - MatchThreshold Minimum score value to return for matches. This value overrides the threshold value set in the Content Analyzer servers. - MaxHits Maximum number of categories to return. - Server The server alias name. You must enter the alias name that you give the CA Operational server in IC Manager. Do not specify the alias for the CA Admin server. Issue 3.0 July

220 Analysis flows Test category This group of blocks, shown in the following figure, tests the categories returned in Step 10, Get Matched Category. If the category returns a Yes, use a Set Routing Hints block to set the category as a routing hint. The sample flow includes three Test Category blocks, as shown in the following figure. 11 The flow uses one or more of the following blocks to perform this function. Step Block Name Description 11 Test Category Searches the results returned by Step 10, Get Matched Categoryfor a particular category and score. To use this block, set the following properties on the Basic tab: CategoryList Name of script variable that holds content analysis results. The value entered here must be the same as the value entered in the TopicList property of the Get Matched Category block. CategoryToCompare Content analysis category to search for. This value must be identical to a topic in the topic tree. ScoreOperator Operator to use in the comparison ScoreToCompare Score value to use in the comparison Tip: If you want a particular category, regardless of the score, set: - ScoreToCompare to 0 - ScoreOperator to >= - CategoryToCompare to the desired category 220 Media Workflow Reference

221 Analyze with Content Analyzer flow Routing hints This group of blocks, shown in the following figure, creates a record in the qw_qualifier table with the routing hint that you specify in the block. Base the routing hint on the value of the category that was tested in Step 11, Test Category. The sample flow includes two Set Routing Hint blocks, as shown in the following figure. 12 The flow uses one or more of the following blocks to perform this function, Step Block Name Description 12 Set Routing Hints Sets a value in the $scroutinghints script variable for the category that was tested in Step 11, Test Category and saves the name and value of the routing hint in the qw_qualifier table of the CCQ database. To use this block, set the following properties in the Basic tab: RoutingHintField The name of the routing hint. Value The value to set in the routing hint field. Suggested response This block, shown in the following figure: Searches the Web Self-Service knowledge base for topics that match the information returned by Content Analyzer. Sets the default language for the response. If no default language is set, selects English Sets the default tenant. If no default tenant is set, selects default. Assigns a context-sensitive template for the response. Issue 3.0 July

222 Analysis flows You create and maintain response templates in the Template Administration in IC Manager. For more information, see IC Administration Volume 1: Servers & Domains. 13 The flow uses the following block to perform this function. Step Block Name Description 13 Get Suggested Response Queries Web Self-Service for topics that match the information returned by Content Analyzer. To use this block, set the following properties: Basic tab: - Language The language to use for the query. Must be a two character ISO language code. If you do not set this field, the block uses en for English. - MaxDocs Maximum number of suggested responses to return. - MaxDocSize Maximum size in Kilobytes of the suggested responses to return. This property filters out responses that are larger than the maximum size. When this happens, the Alarm monitor displays an alarm, and the information is added to the WebACD server log file. - MinScore Minimum confidence score for all returned suggested responses. The query will not return any responses with a lower confidence score. Advanced tab: - AdditionalKeywords Enter additional keywords to use in the search. - TopicList Enter a script variable to hold results returned from the search for suggested responses. - UseRoutingHints Set to true to use the keywords from the Set Routing Hints block. - UseTopicListKeywords Set to true. - UseTopicListTopicPath Set to true if you want to use Topic Paths that you create in Content Analyzer. To use this property, you must set TopicListKeywords to true. 222 Media Workflow Reference

223 Analyze with Content Analyzer flow Route disposition The next group of blocks in the flow, shown in the following figure, sets the route disposition for the contacts. These blocks are not consecutive in the flow, but they perform similar functions for different types of contacts The flow uses the following blocks to perform this function. Step Block Name Description 14 Route Sets a route disposition of Route: To use this block, set the following properties: Basic tab: - ForwardAddress An address that should receive a copy of the contact (optional) Advanced tab: - RouteResponseToIntendedAgent If the value is set to true, the Route disposition overrides any previous setting of the Script.variable.routeresponsetoagent variable set by the server After this block, the flow proceeds to Step 16, IC Analyzed. 15 Auto Response Sets a route disposition of Auto Response, then specifies the content to include in the subject line and text of the reply. To use this block, set the following properties in the Basic tab: ForwardAddress An address that should receive a copy of the automatic response (optional). ResolveWithText Text to use in the Auto Response. If you use this property, you cannot use TemplateName. TemplateName Name of the Response Template to use. If you use this property, you cannot use ResolveWithText. Note: You must set a value for either ResolveWithText or TemplateName. After this block, the flow proceeds to Step 16, IC Analyzed. Issue 3.0 July

224 Analysis flows analyzed This block in the flow, shown in the following figure, notifies the IC server that the Analyze with Content Analyzer flow is complete. 16 The flow uses the following block to perform this function. Step Block Name Description 16 IC Analyzed Saves the values from the $scroutinghints script variable into the qw_qualifier table Invokes the IC .Analyzed method to notify the server that the Analyze with Content Analyzer flow is complete. Stop flow The Stop block marks the exit point for the workflow. After the Stop block, the Workflow server executes the On Exit block. Outbound with Content Analyzer flow The sample Outbound with Content Analyzer flow is outboundca.qfd. The server invokes this flow for outbound contacts if you specify this flow in the Run Outbound Flow property of the server. The Outbound with Content Analyzer flow provides post-processing for outbound contacts. For example, this flow sets routing hints for outbound contacts that need to be routed to a supervisor for approval before they are sent to the recipient. The Qualify flow uses the routing hints to determine how to route the contact. 224 Media Workflow Reference

225 Outbound with Content Analyzer flow The sample Outbound with Content Analyzer flow is shown in the following figure. You can group the blocks of the Outbound with Content Analyzer flow into several steps to see what the flow does with an outbound contact. For example, this flow contains the following groups of blocks: 1. EDU values and input parameters on page type on page Set alert on page component on page Approval category on page Approval by supervisor on page Routing hints on page outbound response on page Stop flow on page 233. You must modify the properties of some of these blocks to customize the workflow to set the routing hints and route dispositions that meet your contact center s needs. Issue 3.0 July

226 Analysis flows EDU values and input parameters The first group of blocks in this flow gets EDU values and input parameters for the contact. The flow uses the following blocks to perform these functions: Step Block Name Description Start Flow Starts the workflow. Incorporates the code for getting a unique database network session for database access through its DBNetwork property. 1 Fetch EDU Fetches the EDU from the EDU server based on the current EDUID. 2 Get EDU Values Retrieves values for the EDU attributes listed on the Basic tab. 3 Get Input Parameters Retrieves values for the input parameters listed on the Basic tab and enters the values in the specified symbols type This group of blocks tests the EDU of the contact for the following types: NOR New inbound contact REQ Customer or external agent reply to an agent s request for more information SME contact from a subject matter expert or another person who has been designated as an external agent OUT Outbound contact 226 Media Workflow Reference

227 Outbound with Content Analyzer flow The following figure shows this group of blocks The flow uses the following blocks to perform these functions: Step Block Name Description 4 Type = SME Tests the EDU to determine if the type of the contact is SME. If the reply type is SME, proceeds to Step 8, Set Alert. 5 Type = REQ Tests the EDU to determine if the type of the contact is REQ. If the reply type is REQ, proceeds to Step 8, Set Alert. 6 Type = NOR Tests the EDU to determine if the type of the contact is NOR. If the reply type is NOR, proceeds to Step 10, Add Component. 7 Type = OUT Tests the EDU to determine if the type of the contact is OUT. If the type is OUT, proceeds to Step 10, Add Component. If the type is none of the above, proceeds to Step 12, Get Agent Quota. Issue 3.0 July

228 Analysis flows Set alert This block, shown in the following figure, sets an alert in the Notification server. The alert reminds the agent who sent the outbound if no response is received within the number of hours or days specified in this block. 8 9 The flow uses the following block to perform this function: Step Block Name Description 8 Set Alert Sets an alert in the Notification server to send a notification to an agent who requested SME help. To use this block, set the following properties: In the Basic tab: - DelayDuration A choice of Minute, Hour, and Day. Default is Minute. - DelayLength The length of the delay that the Notification server waits to send the alert. In the Advanced tab: - vdudata A sequence of couples that contains the contents of the current EDU. You must set this value to the variable in the IC Script that contains the contents of the current EDU. You must assign the same value as you did to the vdudata property in Step 2, Get EDU Values block. 9 Set Alert Failed? 1. Tests to make sure that the notification was set. 2. If the attempt to set the notification failed: - The block raises an alarm. - The workflow exits without returning to the server. - The server reruns the workflow and continues these attempts until the problem with the Notification server has been corrected and the workflow can complete. After this step, proceeds to Step 16, IC Outbound Response. 228 Media Workflow Reference

229 Outbound with Content Analyzer flow component This block, shown in the following figure, adds file attachments and addresses for additional recipients to outbound The flow uses the following block to perform this function: Step Block Name Description 10 Add Component Specifies attachments and additional recipients for the outbound contact. If you want to add more than one address to a field in the outbound , separate the addresses with semicolons. To use this block, set the following properties in the Basic tab: BCC Addresses Adds these addresses to the BCC field of the outbound To Addresses Adds these addresses to the To field of the outbound CC Addresses Adds these addresses to the CC field of the outbound FileAttachments Adds these attachments to the outbound . To include an attachment: - Store the file on the machine that hosts the Workflow server - Specify the full directory path of each file Tip: To include multiple file attachments, separate the directory path and file names of the attachments with semicolons. Approval category This group of blocks, shown in the following figure, determines whether the Content Analyzer category requires that the outbound be sent to a supervisor for approval before the is sent to the recipient. You can configure and train one or more topics in a topic tree, or the entire knowledge base to identify the controlled topics that require review. For example, you can use this Issue 3.0 July

230 Analysis flows group of blocks to identify whether the outbound contains objectionable text or proprietary text that should not be shared with the customer. This section of the Outbound with Content Analyzer flow performs content analysis on the outbound to determine if its intent relates to a controlled topic. If the outbound contains a controlled topic, the flow redirects the to a supervisor for review The flow uses the following blocks to perform these functions: Step Block Name Description 10 QA Category Attempts to match the specified field in the with one or more category and score pairs. If there is a match, sets the script variable qaforcategory to true. Saves the results to the ca_results table. To use this block, set the following properties: Basic tab: - CategoryNameToMatch_N Category to match. Must be in the form: TopicTreeName::LL:Category where TopicTreeName is the name of the topic tree associated with KBName, LL is the 2 character language code which can be left empty and Category is the dot separated category to match. You must complete CategoryNameToMatch_01. - CategoryScore_N At least CategoryScore_01 must be entered for this block. - FieldToAnalyze Script variable that holds text to be analyzed. - KBName Name of Knowledge Base to use. - Server The server alias name. You must enter the alias name that you give the CA Operational server in IC Manager. Do not specify the alias for the CA Admin server. Basic tab: - DefaultLanguage Default 2 character ISO language code to be used for language if Content Analyzer does not return a value. For example, enter en for English. 230 Media Workflow Reference

231 Outbound with Content Analyzer flow Step Block Name Description 11 QA For Category? Tests whether the contact should be sent to a supervisor for approval. If the answer is: No, proceeds to Step 12, Get Agent Quota Yes, proceeds to Step 14, Set Routing Hint (suspectcontent) Approval by supervisor This group of blocks, shown in the following figure, determines whether outbound from the agent needs to be sent to a supervisor for approval before the is sent to the recipient. The approval quota is based on the value of the ReviewQuota property in the /Agent section of the agent s profile. You can set this value in the IC Manager. For more information, see IC Administration Volume 2: Agents, Customers, & Queues The flow uses the following blocks to perform these functions: Step Block Name Description 12 Get Agent Quota 1. Retrieves the value of the ReviewQuota property from the /Agent section of the agent s profile, then saves the value in the script variable qaquotavalue. If there is no value, uses the value in the DefaultQuotaValue property of this block. 2. Generates a random number between 1 and 100, then saves the value in the script variable currentquotascore. To use this block, set the following property in the Basic tab: DefaultQuotaValue Default quota value to use if none is found for the agent. 13 QA Quota Compares the script variables qaquotavalue and currentquotascore to determine whether the outbound needs to be forwarded to a supervisor for approval. If the answer is no, proceeds to Step 16, IC Outbound Response. Issue 3.0 July

232 Analysis flows Routing hints This group of blocks, shown in the following figure, sets the routing hints for outbound , according to: Whether the message requires supervisor approval Why the message requires supervisor approval The flow uses the following blocks to perform these functions: Step Block Name Description 14 Set Routing Hint (suspectcontent) 15 Set Routing Hint (approvalrequired) Marks the to be sent to a supervisor for approval, as follows: 1. Sets the value of suspectcontent for the QA routing hint. 2. Saves the name and value of the routing hint with the msgid of the contact in the qw_qualifier table of the CCQ database. To use this block, set the following properties in the Basic tab: RoutingHintField The name of the routing hint. Value The value to set in the routing hint field. If no routing hint added in Step 14, then marks the to be sent to a supervisor for approval, as follows: 1. Sets the value of approvalrequired for the QA routing hint. 2. Saves the name and value of the routing hint with the msgid of the contact in the qw_qualifier table of the CCQ database. 232 Media Workflow Reference

233 Outbound with Content Analyzer flow outbound response This block, shown in the following figure, notifies the server that the Outbound with Content Analyzer flow is complete. 16 The flow uses the following block to perform this function: Step Block Name Description 16 IC Outbound Response Invokes the IC .OutboundResponse method to notify the server that the Outbound with Keywords flow is complete. Stop flow The Stop block marks the exit point for the workflow. After the Stop block, the Workflow server executes the On Exit block. Issue 3.0 July

234 Analysis flows 234 Media Workflow Reference

235 Chapter 9: Blender Flows! CAUTION: CAUTION: Blender flows include system blocks and system functionality. Changes to these workflows can interfere with the function and performance of Avaya IC systems. If you plan to customize the sample Blender flows in an Avaya IC system, carefully review the blocks and their function in the sample workflows. Blender flows apply business rules to contact routing in the Avaya IC multimedia environment. These flows also set guidelines that: Match the requests, history, and value of each contact with the skills and current workload of individual agents Allow agents to handle more than one contact at a time, either within a single media type or across multiple media types This section describes the sample blender flows installed with Workflow Designer. These workflows are part of the Blender flowset. This section includes the following topics: Blender flows in Avaya IC on page 236. Setting task loads with Blender flows on page 237. Initialization flow on page 237. Client Login flow on page 239. State flow on page 243. Blender system flows on page 251. For information about the locations of these sample contact routing flows, see Sample Blender flows on page 23. Issue 3.0 July

236 Blender Flows Blender flows in Avaya IC Blender flows are invoked by the Blender server. The Blender server monitors ADUs and evaluates ADU.Change events. If an ADU.Change event includes a field specified in the server Initialization flow, the blender server invokes a QWorkflow.Run method on the Workflow server and activates the appropriate flow set. If the ADU.Change event includes more than one specified field, the Blender server runs the appropriate flow for each field in the event. For example, if the Initialization flow contains the state field and the name of the workflow to be run when the value of state changes, the Blender server monitors changes to the value of the ADU field state. When an agent who handles voice contacts logs in to Avaya Agent and becomes Available: 1. The Client Login workflow logs the agent in and updates the agent s <media>.currentload values (setting the value of voice.currentload to 1). 2. The state field is added to the ADU.Change event for that agent. 3. The Blender server receives the ADU.Change event and looks at the change in the value of the state field. 4. The Blender server executes the State workflow (which is mapped to the state field in the Initialization flow). 5. The Blender client on the agent desktop gets the ADU.Change event, sees that the agent s voice.currentload is 1, and issues a Ts.Ready command to the Telephony server to advise the Telephony server that an agent is available to handle a contact from a voice queue. For information about the operation and configuration of the Blender server, see IC Administration Volume 1: Servers & Domains. Note: Note: While a search is in progress, the WAITINGFORDATA event fires periodically to allow an agent to interrupt the search. When this happens, another event or timer may attempt to execute a search in the same thread. For example, this conflict can occur during simultaneous database searches, or when more than one contact arrives simultaneously at the agent s desktop. 236 Media Workflow Reference

237 Setting task loads with Blender flows Setting task loads with Blender flows When an administrator creates an agent s Avaya IC account in IC Manager, the administrator sets the agent s privileges, including the task load and ceiling for all media channels and for each media channel, and the agent s work mode. According to an agent s account privileges and the configuration of Avaya Agent, an agent can work in either of the following modes: Manual mode Agents control availability across all media channels and set the task load for each media channel up to the maximum set by the administrator. In manual mode, the workflows for setting <media>.load do not run. Automatic mode Blender flows set an agent s task load for each media channel and control the number of contacts handled simultaneously by an agent. ADU fields include the following task load information: ADU Field Name Description Set by load Maximum number of currently assigned contacts across all media channels. Administrator Agent ceiling Limit on load across all media channels. Administrator <media>.load Maximum number of currently assigned contacts for a specific media. Administrator Workflow <media>.ceiling Limit on load for the media channel. Administrator <media>.currentload Field that controls the number of simultaneous contacts for a media channel in automatic mode. Workflow Initialization flow! CAUTION: CAUTION: Be careful when you customize the Initialization flow. If this workflow cannot run, the Blender server does not start. At startup, the Blender server runs the Initialization flow on the Workflow server. When this workflow is run, the Workflow server returns a list of ADU fields for the Blender server to monitor and a map of the relationships between the ADU fields and specific workflows. The Issue 3.0 July

238 Blender Flows Blender server uses this information to determine which flow to run when a client assigns to the Blender server. You specify the name of the initialization flow in the Initialization Flow configuration parameter in IC Manager. The Blender server uses the information returned by the Initialization flow as follows: 1. Blender server monitors the designated fields in all active ADUs. 2. When there is any change in an active ADU, the Blender server evaluates the ADU.Change event to determine if the event includes a field specified in the Initialization flow. 3. If the event includes a monitored field, the Blender server uses the relationship map in the Set Output Parameters block of the Initialization flow to determine which workflow needs to be run. 4. The Blender server invokes a QWorkflow.Run method on the Workflow server and activates the appropriate workflow. The sample Initialization flow and the Basic properties for the Set Output Parameters block are shown in the following figure Media Workflow Reference

239 Client Login flow The steps of the sample Initialization flow use the following standard routing blocks: Step Block Name Description Start Flow 1 Set Output Parameter Stop Flow Starts the workflow. Incorporates the code for getting a unique database network session for database access through its DBNetwork property. Monitors the following fields in the ADU that are included in an ArgName field on the Basic tab: state chat.state .state voice.state chat.forceserverfailed .forceserverfailed voice.forceserverfailed If the change event includes a change to one of these fields, runs the workflow listed in the equivalent ArgValue field on the Basic tab. For example, if the change event includes a change to the chat.state field in ArgName_02, this workflow runs the channel_state field, which is listed in ArgValue_02. Ends the workflow. Client Login flow The Blender server invokes the Client Login flow when an agent logs in to Avaya Agent. This flow determines the agent s blending preferences.! CAUTION: CAUTION: Be careful when customizing the Client Login flow. If this workflow cannot run, the Blender server issues a high priority alarm and the agent s login attempt fails. This section includes the following topics: ADU values in the Client Login flow on page 240. Example: adding agent attribute to ADU on page 240. Steps in sample Client Login flow on page 241. Issue 3.0 July

240 Blender Flows ADU values in the Client Login flow The media and agent task load values and ceiling values for an agent determine the blending preferences. These values are initially set in IC Manager when an Avaya IC account is created for an agent. The administrator can define default values to be assigned to all new agent accounts or specify different values for particular agents. The values are stored in the Channel and Employee tables in the IC Repository database. By default, the Client Login flow retrieves the database values from the tables and sets the ADU field attributes, shown in the following table. Avaya IC can change the attribute values with other blender flows, such as the State flow. ADU Field Name Description Set by load Maximum number of currently assigned contacts across all media channels. Administrator Agent ceiling Limit on load across all media channels. Administrator <media>.load Maximum number of currently assigned contacts for a specific media. Administrator Workflow <media>.ceiling Limit on load for the media channel. Administrator By default, IC Manager sets the initial task load values at 1. This setting allows an agent to log in to Avaya Agent in AuxWork mode, and ensures that Avaya Agent starts up completely before any contacts are routed to the agent. Example: adding agent attribute to ADU In addition to the media and agent task load for an agent, you can add agent attributes to the ADU. For example, you can use this workflow to include the address of an agent. After you make these changes, compile and test the customized workflow. To use the Client Login flow to add the address of an agent to the ADU: 1. Open the Client Login flow. 2. On the Property Sheet for the Employee and Channel block: a. In EmployeeTblField_06, enter . b. In Target_06, replace $ChangeMe with $ address. 3. On the Property Sheet for the Set Output Parameters block: a. In ArgName_18, enter address. b. In ArgValue_18, enter $ address. 240 Media Workflow Reference

241 Client Login flow Steps in sample Client Login flow The sample Client Login flow is shown in the following figure. The numbers for each block refer to the steps in the flow described in the following table The steps of the sample Client Login flow use the following blocks from various palettes of the Catalog bar. Modify the properties of a block to customize the workflow. Step Block Name Description Start Flow Starts the workflow. Incorporates the code for getting a unique database network session for database access through its DBNetwork property. 1 Set Values Sets the default values for the client s blending preferences. The default values are used if the preferences are not in the database, or if the database is unavailable. Issue 3.0 July

242 Blender Flows Step Block Name Description 2 Get Input Parameters Retrieves values for the input parameters listed on the Basic tab and enters the values in the specified symbols 3 Clean State cache Cleans the cache of agent and channel state records from previous contacts that the agent handled. 4 Employee and Channel Gets the values of task and channel related fields from record in the Employee table for the agent who logged in. Checks the fields listed in the EmployeeTblField sections of the Basic tab, including: taskload taskceiling advocateflag site_key lrmid_key Tip: To include additional fields in the ADU for an agent, add fields from the agent record in the Employee table to the values of EmployeeTblField_N and Target_N on the Basic tab. 5 Test if Record Found Tests whether the Employee and Channel block found a record for the agent in the Employee table. If the value is: No Flow proceeds to Step 6, Raise Alarm Yes Flow proceeds to Step 7, Channel Ceiling Load 6 Raise Alarm Raises an alarm if no record was found in the Employee table for the agent, then proceeds to Step 8, Set Output Parameters. 7 Channel Ceiling Load 8 Set Output Parameters Stop Flow Stores the task load and ceiling values in a global cache named agentloadinfo@<agent_aduid>. Assigns the values retrieved from the Employee table to the ADU attributes. If no values were retrieved, assigns the default values from Step 1 to the ADU attributes. Tip: To include additional fields in the ADU for an agent, add fields from the agent record in the Employee table to the values of ArgName_N and ArgValue_N on the Basic tab. Ends the workflow. 242 Media Workflow Reference

243 State flow State flow The Blender server invokes the State flow when the server learns about any changes to the value of the ADU attribute state. For example, when an agent who handles voice contacts logs in to Avaya Agent and becomes Available, the value of the state field in that agent s ADU changes. After the server receives the ADU.Change event, the server invokes a QWorkflow.Run method on the Workflow server and activates the flow set with the State flow. Note: Note: For the State flow to run, the Initialization flow must contain a relationship between the ADU attribute state and the State flow. The State flow can change an agent's media and agent task load values by looking at an agent s state. The possible agent states are: Agent State loggedout available auxwork outbound inittransition initauxwork initinbound initoutbound initvoicebusy Description Agent is not currently logged in. Agent is available for handling contacts (in one or all media channels). Agent is performing auxiliary work. Agent is handling outbound voice calls and cannot accept inbound contacts from any media channel. Agent is making a request to enter one of the following "init" states: initauxwork initoutbound initvoicebusy Agent is making a request to enter auxwork state. Agent has completed handling outbound voice calls and is transitioning into available state. Agent is transitioning to outbound state. Agent will be handling voice chat or callback contact and cannot accept voice contacts. Issue 3.0 July

244 Blender Flows The sample State flow is shown in the following figure. The State flow is relatively complex. However, you can group the blocks into several steps to see how the flow handles changes to an ADU. For example, this flow contains the following groups of blocks: 1. Input parameters on page ADU values on page Agent state on page Inittransition state on page Available state on page Stop flow on page Media Workflow Reference

245 State flow Input parameters The first group of blocks, shown in the following figure, gets input parameters from the ADU about the agent s state. 1 The flow uses the following blocks to perform these functions: Step Block Name Description Start Flow 1 Get Input Parameters Starts the workflow. Incorporates the code for getting a unique database network session for database access through its DBNetwork property. Retrieves the value of the state field from the ADU. To add other fields to the input parameters that this block retrieves, add or modify a pair of Parameter_N and Target_N parameters on the Basic tab. The parameter must correspond to a field in the ADU. ADU values This group of blocks, shown in the following figure, performs the following tasks: Obtains the EmployeeKey for the agent from the Agent Load cache. If this attempt is not successful, the blocks re-create the cache from the ADU. Issue 3.0 July

246 Blender Flows Updates the Agent State cache in the Workflow server for the agent search capabilities The flow uses the following blocks to perform these functions: Step Block Name Description 2 Ceiling Load Obtains the following values from a global cache named agentloadinfo@<agent_aduid>: Task load for each media Task ceiling for each media EmployeeKey for the agent 3 Test Data Tests the value of GetAgentInfoFromADU. If the value is: Yes, proceeds to Step 4, Fetch ADU Record No, proceeds to Step 7, Update Agent State Cache 4 Fetch ADU Record Fetches the ADU data using the value of the input parameter adu_id. 5 Get ADU Values Retrieves the following values from the ADU: .ceiling .load chat.ceiling chat.load voice.ceiling voice.load load ceiling agent_key 6 Channel Ceiling Store the values retrieved from the ADU in a workflow server global cache named agentloadinfo@<adu_id>. 7 Update Agent State Cache Updates the agent state cache with the ADU values. 246 Media Workflow Reference

247 State flow Agent state After the flow stores the values in the cache, the next group of blocks, shown in the following figure, tests the value from the ADU state field. 8 9 The flow uses the following blocks to perform these functions: Step Block Name Description 8 state = "inittransition"? Tests the value in the state field. If the value is: inittransition Flow proceeds to Step, Inittransition state Not inittransition Flow proceeds to Step 9, state = "available"? 9 state = "available"? Tests the value in the state field. If the value is: Available, proceeds to Step 14, Transition Not Available, proceeds to Stop flow Issue 3.0 July

248 Blender Flows Inittransition state If the State flow determines that the agent is in inittransition state, the next group of blocks, shown in the following figure, sets the agent values, including the contact load The flow uses the following blocks to perform these functions: Step Block Name Description 10 Transition Retrieves the value of the transition flag from the ADU. 11 transition = "initinbound"? Tests the value of the transition flag. If the value is: Initinbound Flow proceeds to Step 16, Set Current Load = Load Not Initinbound Flow proceeds to Step 12, transition = "initauxwork"? 248 Media Workflow Reference

249 State flow Step Block Name Description 12 Following series of Test blocks: transition = "initauxwork"? transition = "initoutbound"? transition = "initchatbusy"? transition = "init busy"? transition = "initvoicebusy"? 13 Set Load and Current Load to 0 Tests the value of the transition flag. If the value of the transition flag does not match the value tested by the block, proceeds to the next transition block. If no transition block finds a match, proceeds to Stop flow. If the value of the transition flag matched the value tested by the block, proceeds to Step 13, Set Load and Current Load to 0. Note: When the state is inittransition and the transition is initinbound, the agent must be treated as available except that you do not need to set auxwork.n.endtime in the EDU. 1. Sets the following values to 0: - <media>.load - <media>.currentload 2. Proceeds to Stop flow Issue 3.0 July

250 Blender Flows Available state If the State flow determines that the agent is Available, the next group of blocks, shown in the following figure, set the task loads for the media equal to the value of the task ceiling for each channel The flow uses the following blocks to perform these functions: Step Block Name Description 14 Transition Retrieves the value of the transition flag from the ADU. 15 transition = "noop"? Tests the value of the transition flag. If the value is: Not Noop, proceeds to Step 16, Set Current Load = Load Noop, proceeds to Stop flow 16 Set Current Load = Load Sets the value of <media>.currentload to the same value as <media>.load in the Workflow server global cache named agentloadinfo@<adu_id>. The value of <media>.load must be equal to or greater than 0. This value cannot be an empty string. 250 Media Workflow Reference

251 Blender system flows Step Block Name Description 17 Adjust Current Load/Load based on ChannelState Compares the following information and adjusts the task load and ceiling values for the agent if desired. AgentKey AgentState ChatState ChatCurrentLoad ChatLoad State CurrentLoad Load VoiceState VoiceCurrentLoad VoiceLoad 19 Ceiling Load Store the load and ceiling values retrieved from the ADU in a workflow server global cache named agentloadinfo@<adu_id>. 23 Set Load (per DB of 1) and currentload as 1 Sets the following values: <media>.load to 1 <media>.currentload 1 auxworkendtimename Stop flow The Stop block marks the exit point for the workflow. After the Stop block, the Workflow server executes the On Exit block. Blender system flows The Blender flowset also includes some system workflows. These workflows are also invoked by the Blender server.! CAUTION: CAUTION: Do not customize or modify the Blender system workflows. Changes to these workflows will interfere with the performance of the Avaya IC system. This section includes the following topics which describe the Blender system flows: Client Logout flow on page 252. Issue 3.0 July

252 Blender Flows Channel State flow on page 253. Channel Server Failure flow on page 255. Client Logout flow The Blender server invokes the Client Logout flow when an agent logs out of Avaya Agent.! CAUTION: CAUTION: Do not customize the Client Logout flow. If this workflow cannot run, the Blender server issues a high priority alarm and the agent cannot logout. The Client Logout flow is shown in the following figure. The Client Logout flow performs the following steps when an agent logs out of Avaya IC: 1. Agent logs out of Avaya IC. 2. Blender server invokes the Client Logout workflow. 3. The Client Logout workflow: a. Fetches the agent key from the input data that was sent into the workflow. b. Uses the agent key to remove the following information about that agent from variables within the global cache of the Workflow server: agent state, channel state, and agent workload. 252 Media Workflow Reference

253 Blender system flows Channel State flow The Blender server invokes the Channel State flow when the server learns about any changes to the value of one or more of the following ADU attributes: chat.state .state voice.state For example, when an agent who is already logged in becomes available for the voice channel, the value of the voice.state field in the ADU for that agent changes. After the server receives the ADU.Change event, the server invokes a QWorkflow.Run method on the Workflow server and activates the flow set with the Channel State flow. For the Channel State flow to run, the Initialization flow must contain a relationship between the ADU attribute <media>.state and the Channel State flow. Issue 3.0 July

254 Blender Flows! CAUTION: CAUTION: Do not customize the Channel State flow. If this workflow cannot run, the Blender server issues a high priority alarm. The sample Channel State flow is shown in the following figure. The State flow performs the following steps after a channel state changes and the Blender server invokes the flow: 1. Retrieves input parameters from the ADU about the agent s state, including the values of the following fields: chat.state .state voice.state 2. Obtains the EmployeeKey for the agent from the Agent Load cache. If this attempt is not successful, the blocks re-create the cache from the ADU. 254 Media Workflow Reference

255 Blender system flows 3. Updates the Agent State cache in the Workflow server for the agent search capabilities. 4. After the flow stores the values in the cache, the workflow: a. Tests the value of the <media>.state field for each media b. Uses the value of the Channel State to determine whether the Channel Load and Current Load.for the agent needs to be increased or decreased Channel Server Failure flow The Blender server invokes the Channel Server Failure flow when one of the following fields changes in the ADU for an agent: chat.forceserverfailed .forceserverfailed voice.forceserverfailed These fields are set when an Avaya IC client application recognizes that an Avaya IC channel server has failed. The channel servers include the Telephony server, the server, and the WebACD server. When a <media>.forceserverfailed field changes, the Blender server does not verify the failure. Instead, the Blender server assumes that the channel server has failed and flag the appropriate channel.state in the ADU as failed. Issue 3.0 July

256 Blender Flows! CAUTION: CAUTION: Do not customize the Channel Server Failure flow. If this workflow cannot run, the Blender server issues a high priority alarm and the agent application cannot function correctly. The Channel Server Failure flow is shown in the following figure. The State flow performs the following steps after a channel state changes and the Blender server invokes the flow: 1. Retrieves input parameters from the ADU about the agent s state, including the agent task load and task ceiling. 2. Store the values for the task load and task ceiling values in a global cache named agentloadinfo@<agent_adu_id>. 3. Tests the values of each of the following fields in the ADU: 256 Media Workflow Reference

257 Blender system flows chat.forceserverfailed .forceserverfailed voice.forceserverfailed 4. If one of the fields includes a value which indicates that the server has failed, the workflow performs the following steps for that media channel: a. If the value of currentload is greater than zero, or is not an empty string, sets the value of currentload for the media channel to be the agent task load. b. Tests whether the value for the agent task load needs to be changed. If the load does not need changing, the workflow exits. c. Updates the cache for the channel state. d. Uses the value of the Channel State to set the channel load and current load for the agent. If none of the fields includes a value which indicates that the servers are running, the workflow exits. Issue 3.0 July

258 Blender Flows 258 Media Workflow Reference

259 Chapter 10:Business Advocate flows Business Advocate flows qualify contacts for Business Advocate systems that include multiple Logical Resource Managers. All Workflow servers can run the Business Advocate qualification workflows. You do not need to configure workflow criteria in the Workflow servers, because the Business Advocate servers start the workflows. For incoming voice contacts, the TSA server connects to a Workflow server and starts the voice qualification workflow. For contacts and chat contacts, the WAA server connects to a Workflow server and starts the appropriate qualification workflow. This configuration allows you to configure multiple Workflow servers to handle a high volume of contacts. For example, you can assign multiple Workflow servers to the same TSA server if the TSA server connects to a CTI link that handles a high volume of voice contacts. The TSA server uses a round robin approach to select a Workflow server to qualify each incoming contact. You can customize the sample Business Advocate flows to match the needs of your contact center. Some examples of customization are given in the sections that describe the sample workflows.! CAUTION: CAUTION: Blocks must eventually terminate, allowing another block in the workflow to run. If blocks do not terminate, the workflow can be caught in an infinite loop when the server shuts down or deassigns from a workflow that is still running. This section includes the following topics that describe the sample Business Advocate workflows: Qualification workflows in Business Advocate on page 260. Qualify Voice flow for Business Advocate on page 263. Qualify Chat flow for Business Advocate on page 271. Qualify flow for Business Advocate on page 281. Issue 3.0 July

260 Business Advocate flows Qualification workflows in Business Advocate This section includes the following topics that describe the general approach to qualification workflows in Business Advocate. Data used for qualification on page 260. Prequalification steps on page 260. Required qualifiers on page 261. Data used for qualification The qualification workflows for Business Advocate qualify a contact based on data from the following areas: EDU of a contact CCQ database Prequalification steps Some contacts also go through the prequalification steps shown in the following table. The prequalification steps are the same for Blender and Business Advocate environments. Type of contact Prequalification step Description Voice None required A voice contact does not typically go through a prequalification step. If the Avaya IC system includes integration with an IVR, the IVR functions as a prequalification step. Chat Routing hints assigned on Web Management Website When a customer browses Web pages before requesting a chat with an agent, the Website can associate routing hints with the chat contact. analysis workflow analysis flows function with or without Content Analyzer. For more information, see Analysis flows on page Media Workflow Reference

261 Qualification workflows in Business Advocate Required qualifiers Each sample qualification workflow for Business Advocate requires certain qualifiers. You can change the qualifiers used by the workflows to customize the way that the workflows qualify contacts. For more information about qualifiers, see IC Business Advocate Configuration and Administration. The following table describes the qualifiers required by the sample Business Advocate workflows. Qualifier category Qualifier Value Description channel voice Value cannot be changed. Identifies the channel for voice contacts. Installed automatically with Business Advocate. chat Value cannot be changed. Identifies the channel for chat contacts. Installed automatically with Business Advocate. Value cannot be changed. Identifies the channel for contacts. Installed automatically with Business Advocate. customertype Value is set according to the needs of the contact center. Identifies the type or worth of the customer to the contact center. Possible values can be gold, silver, or bronze. You can also use other values, such as high, medium, or low. Issue 3.0 July

262 Business Advocate flows Qualifier category Qualifier Value Description intent Value is set according to the needs of the contact center. Identifies the particular segment or division in which the customer is interested. The intent category normally reflects the following: For voice contacts, the telephone number (DNIS) dialed by a customer. For chat contacts, the Web page visited by a customer in a particular self-service Website. For contacts, the address where the customer sent the contact. Possible values can be: sales, service, or support. Other values can be more specific, such as laptops, desktops, peripherals, and servers. language Value is set according to the needs of the contact center. Identifies the language of the contact. The language is set in all channels with the two character ISO codes. The language category can reflect: For voice contacts, the value is typically the preferred language of a customer in the CCQ database. If you customize the sample workflow to integrate with an IVR, the value can be the language selected by the customer during IVR prompting. For chat contacts, the value is determined by the language that a customer selects on the Web Management Website. For contacts, the value can be set by Content Analyzer, if the Avaya IC system includes Content Analyzer. The value is not set by the preferred language of the customer. multimedia ivchat Value cannot be changed. Indicates that the customer wants to have a Chat & VOIP type of voice chat contact with the agent. pvchat Value cannot be changed. Indicates that the customer wants the agent to call back and have a Chat & Phone type of voice chat contact with the agent. 262 Media Workflow Reference

263 Qualify Voice flow for Business Advocate Qualify Voice flow for Business Advocate The Qualify Voice flow identifies a collection of Business Advocate qualifiers for an incoming voice contact. Business Advocate then uses these qualifiers to accurately match the incoming voice contact with a qualified, available agent. The Telephony Services Adaptor (TSA) server starts the Qualify Voice workflow. For more information about how Business Advocate routes voice contacts, see IC Business Advocate Configuration and Administration. The sample Qualify Voice flow is shown in the following figure. The beginning of this workflow is similar to the Incoming Call workflow that Avaya IC uses for systems without Business Advocate. Issue 3.0 July

264 Business Advocate flows Group the blocks of the sample Qualify Voice flow into several steps to see how the workflow qualifies an incoming voice contact. For example, this workflow contains the following groups of blocks: 1. Input parameters and EDU values on page Contact information on page Qualifiers on page Post qualification on page Stop flow on page 271. Input parameters and EDU values The first group of blocks gets EDU values for the contact, as shown in the following figure The Qualify Voice flow uses the following blocks to perform these functions: Step Block Name Description Start Flow 1 Get Input Parameters Starts the workflow. Incorporates the code for getting a unique database network session for database access through its DBNetwork property. Retrieves values for the input parameters listed on the Basic tab and enters the values in the specified symbols 264 Media Workflow Reference

265 Qualify Voice flow for Business Advocate Step Block Name Description 2 Fetch EDU Fetches the EDU for the incoming voice contact. 3 Get EDU Values Retrieves the value of the EDU attributes that are specified in the Field properties on the Basic tab. The EDU attributes include the following: primary_ani Assigns the value for the ANI of the contact to the $VoiceANI script variable. primary_dnis Assigns the value for the DNIS of the contact to the $VoiceDNIS script variable. For intent qualification, the workflow requires the original DNIS. language Assigns the value of the language of the contact to the $EDUlanguage script variable. The language is only available if determined by a prequalification workflow, such as an IVR script. customer_fetched Indicates whether the Customer record has already been fetched. type Assigns the value of the channel type of the contact to the $MediaType script variable. Contact information After the Qualify Voice flow gets input parameters and EDU values, the workflow sets additional values for the incoming voice contact. The values set by the second group of blocks, shown in the following figure, provide more information to assist the agent with the customer Issue 3.0 July

266 Business Advocate flows The flow uses the following blocks to perform these functions: Step Block Name Description 4 CustomerFetched? Tests whether the value of the customer_fetched field is NULL. A NULL value indicates that the attempt to find the Customer record has not yet been performed. If the answer is: Yes, value is NULL, proceeds to Step 5, Format ANI. No, value is not NULL, proceeds to Step 10, Create Agent Desktop Data. 5 Format ANI Formats the ANI of the contact for searches. Searches require that the ANI be in the form (000) to be used as a query parameter. 6 Fetch Customer Record (ANI) Attempts to fetch a record from the Customer table of the CCQ database with the primary_ani value in the $VoiceANI script variable. 1. Checks the database for a Customer record that matches the ANI of the contact. 2. Sets a NumRecords value for the number of records that match the ANI. 3. If only one Customer record is available, retrieves the specified values from the Customer record and writes the values to the customerinfo container of the EDU. To modify the values that the block retrieves from the Customer record, add or modify a pair of Field_N and Value_N parameters on the Basic tab. The field must correspond to a field in the Customer table. 7 RecordCount=1 Tests the NumRecords value set by the Fetch Customer Record block to see if the value is 1. If the answer is: Yes, the value is 1, proceeds to Step 8, Fetch EDU. No, the value is not 1, proceeds to Step 10, Create Agent Desktop Data. 8 Fetch EDU Fetches the EDU data again to ensure that the workflow uses the EDU data in the actual Customer data retrieved by the Fetch Customer Record block. 266 Media Workflow Reference

267 Qualify Voice flow for Business Advocate Step Block Name Description 9 Get Customer Values 10 Create Agent Desktop Data Gets the following values for the customer from the customerinfo container of the EDU that Business Advocate uses to help match the customer with an agent: customerinfo.preferredagent Login ID of the Avaya IC agent who is the preferred agent for the customer. customerinfo.language Preferred language of the customer. customerinfo.customertype Value that can identify the relative worth of this customer to the Enterprise. For example, this value is typically set to gold, silver, or bronze for Business Advocate demonstrations. Populates the EDU with the data that Avaya Agent and other agent desktop applications use for screen pops. Qualifiers This group of blocks, shown in the following figure, sets the qualifiers and other Business Advocate values for the contact Issue 3.0 July

268 Business Advocate flows The flow uses the following blocks to perform these functions: Step Block Name Description 11 Set Qualifier (Channel) 12 Preferred Agent NULL? 1. Takes the value of voice in the $MediaType script variable for channel and sets that as the qualifier of channel/voice for the contact. 2. Adds the channel qualifier to collection of qualifiers for the contact in the sequence couple $scqualifiers Business Advocate includes the Channel qualifiers. A qualifier of category Channel is always a valid Business Advocate qualifier. If no other qualifiers are set for a contact, Business Advocate uses the channel qualifier to match the contact with an agent. Tests whether the value retrieved from the EDU for customerinfo.preferredagent is NULL. If the answer is: Yes, value is NULL, proceeds to Step 14, EDU Language NULL? No, value is not NULL, proceeds to Step 13, Fetch LRMID. 13 Fetch LRMID Fetches the LRM ID for the Logical Resource Manager associated with the preferred agent. 14 EDU Language NULL? 15 Map to Qualifier (Language) 16 Map to Qualifier (Language) Tests whether the value of $EDUlanguage is NULL. If the answer is: Yes, value is NULL, proceeds to Step 15, Map to Qualifier (Language) No, value is not NULL, proceeds to Step 16, Map to Qualifier (Language). 1. Compares the value of $custlanguage to one of four possible values listed on the Basic tab. These qualifier values are the two character IS language codes. 2. If the value of $custlanguage matches a possible value, maps the ISO language code to the corresponding qualifier. For example, if the code is en, maps this code to english. 3. Assigns the qualifier value to the $language variable. 1. Compares the value of $EDUlanguage to one of four possible values listed on the Basic tab. These qualifier values are the two character IS language codes. 2. If the value of $EDUlanguage matches a possible value, maps the ISO language code to the corresponding qualifier. For example, if the code is en, maps this code to english. 3. Assigns the qualifier value to the $language variable. 268 Media Workflow Reference

269 Qualify Voice flow for Business Advocate Step Block Name Description 17 Set Qualifier (Language and Customer Type) 18 Map to Qualifier (DNIS) Sets qualifiers for the categories of language and customertype in the sequence couple $scqualifiers For the language category, the block: 1. Retrieves the value for language from the $language script variable. 2. If a valid qualifier exists with the values language/<$language>, adds that qualifier to the collection of qualifiers for the contact. 3. If no valid qualifier exists and the DefaultQualifier value on the Basic tab contains a mapped value for the language, adds the default qualifier value to the collection of qualifiers for the contact. For the customertype category, the block: 1. Retrieves the value of customerinfo.customertype from the script variable. 2. If a valid qualifier exists with the values customertype/<$customertype>, adds that qualifier to the collection of qualifiers for the contact. 3. If no valid qualifier exists and the DefaultQualifier value on the Basic tab contains a mapped value for the language, adds the default qualifier value to the collection of qualifiers for the contact. 1. Compares the $VoiceDNIS variable to one of four possible values listed on the Basic tab. These qualifier values are the telephone numbers that can be the primary DNIS for a contact. 2. If the value of the $VoiceDNIS variable matches a possible value, assigns corresponding qualifier for the value to the $intent variable. Note: By default, no telephone numbers are entered in this block. You must configure at least one telephone number for Value_1. 19 Set Qualifier (intent) 1. Uses the $intent value to set the value of the intent qualifier with the value of the $intent script variable. 2. Adds the intent qualifier to collection of qualifiers for the contact in the sequence couple $scqualifiers For example, if the value for $intent was set to sales by the Map to Qualifier (DNIS) block, this block sets the intent qualifier to intent/sales. Post qualification This group of blocks does the following: 1. Configures the wait treatment for the contact. Issue 3.0 July

270 Business Advocate flows 2. Translates the collection of qualifiers set by the Set Qualifier blocks into a numeric sequence. 3. Calls the postqualification method of the TSA server. Important:! Important: If you customize this workflow, you must preserve the order and position of this group of blocks in the flow The flow uses the following blocks to perform these functions: Step Block Name Description 20 Set Voice Wait Treatment 21 Translate Category/Qualifier Uses the $intent value to set the wait treatment style to a numeric value. When you configure the workflow, you select the numeric value from the drop-down list for each Wait_Treatment_N properties. The values that you can select are constants at the bottom of the list that start with $WT_. The default style is set to WT_TRANSFER which is defined as Transforms the sequence couple $scqualifiers from a collection of qualifiers in name value pairs to a string that contains the numeric transformation of these qualifiers. 2. Starts to build a new sequence couple for the variable $scroutinghint. This sequence couple contains the routinginfo container in the current advocate container of the EDU. 3. Adds the field qualifiers to the advocate.routinginfo container. 270 Media Workflow Reference

271 Qualify Chat flow for Business Advocate Step Block Name Description 22 Post Qualification 1. Uses the following script variables set in the workflow to call the postqualification method of the TSA server: - $waittreatmentstyle - $qualifier_set - $PreferedAgent -$LRMid 2. Sets the PostQualificationAction to route and sets ExcludeAgent to no. 3. Adds the following fields to the variable $scroutinghint, then writes those fields to the EDU: - agent_id - exclusion_flag - waittreatmentstyle -action - lrmid_key Stop flow The Stop block marks the exit point for the workflow. After the Stop block, the Workflow server executes the On Exit block. Qualify Chat flow for Business Advocate The Qualify Chat flow identifies a collection of Business Advocate qualifiers for a chat contact. Business Advocate then uses these qualifiers to accurately match the chat contact with a qualified, available agent. The Web Advocate Adaptor (WAA) server starts the Qualify Chat flow. For more information about how Business Advocate routes chat contacts, see IC Business Advocate Configuration and Administration. Issue 3.0 July

272 Business Advocate flows The sample Qualify Chat flow is shown in the following figure. Group the blocks of the sample Qualify Chat flow into several steps to see how the workflow qualifies a chat contact. For example, this workflow contains the following groups of blocks: 1. Input parameters and EDU values on page Contact information on page Qualifiers on page Post qualification on page Stop flow on page Media Workflow Reference

273 Qualify Chat flow for Business Advocate Input parameters and EDU values The first group of blocks gets EDU values for the contact, as shown in the following figure The Qualify Chat flow uses the following blocks to perform these functions: Step Block Name Description Start Flow 1 Get Input Parameters Starts the workflow. Incorporates the code for getting a unique database network session for database access through its DBNetwork property. Retrieves values for the input parameters listed on the Basic tab and enters the values in the specified symbols 2 Fetch EDU Fetches the EDU for the chat contact. 3 Get EDU Values Retrieves the value of the EDU attributes that are specified in the Field properties on the Basic tab. The EDU attributes include the following: customerinfo.role Assigns the login id value of the user who initiated the chat to the $ChatRole variable. If this value is guest, then no Customer record will be available for the contact. language Assigns the value of the language of the contact to the $EDUlanguage script variable. The language is only available if determined by a prequalification workflow, such as the workflows in the webcenter project. customer_fetched Indicates whether the Customer record has already been fetched. type Assigns the value of the channel type of the contact to the $MediaType script variable. ivchatenabled Indicates whether the customer wants to have a Chat & VOIP type of voice chat contact with the agent. Assigns this value to the $ivchatenabled variable. pvchatenabled Indicates whether the customer wants the agent to call back and have a Chat & Phone type of voice chat contact with the agent. Assigns this value to the $pvchatenabled variable. Issue 3.0 July

274 Business Advocate flows Contact information After the Qualify Chat flow gets input parameters and EDU values, the workflow sets additional values for the chat contact. The values set by the second group of blocks, shown in the following figure, provide more information to assist the agent with the customer The flow uses the following blocks to perform these functions: 9 Step Block Name Description 4 Chat Role = guest? Tests whether the value of customerinfo.role in the $ChatRole variable is guest. If this value is guest, then no Customer record will be available for the customer. If the answer is: No, value is not guest, proceeds to Step 5, Fetch Customer record by pkey. Yes, value is guest, proceeds to Step 10, Create Agent Desktop Data. 274 Media Workflow Reference

275 Qualify Chat flow for Business Advocate Step Block Name Description 5 Fetch Customer record by pkey Attempts to fetch a record from the Customer table of the CCQ database with the pkey value found in the customer_key script variable that was determined when the Website authenticated the customer login. 1. Checks the database for a Customer record that matches the customerinfo.role value. 2. Sets a NumRecords value for the number of records that match the customerinfo.role. 3. If only one Customer record is available, retrieves the specified values from the Customer record and writes the values to the customerinfo container of the EDU. To modify the values that the block retrieves from the Customer record, add or modify a pair of Field_N and Value_N parameters on the Basic tab. The field must correspond to a field in the Customer table. 6 RecordCount=1 Tests the NumRecords value set by the Fetch Customer Record block to see if the value is 1. If the answer is: Yes, the value is 1, proceeds to Step 7, Fetch EDU. No, the value is not 1, proceeds to Step 10, Preferred Agent NULL?. 7 Fetch EDU Fetches the EDU data again to ensure that the workflow uses the EDU data with the actual Customer data retrieved by the Fetch Customer Record block. 8 Get Customer Values Gets the following values for the customer from the customerinfo container of the EDU that Business Advocate uses to help match the customer with an agent: customerinfo.preferredagent Login ID of the Avaya IC agent who is the preferred agent for the customer. customerinfo.language Preferred language of the customer. customerinfo.customertype Value that can identify the relative worth of this customer to the Enterprise. For example, this value is typically set to gold, silver, or bronze for Business Advocate demonstrations. 9 Fetch Routing Hints 1. Fetches all routing hints for the chat contact that were assigned to the Web pages that the customer visited. 2. Adds the category and value information from the fetched hints to the $scroutinghint sequence couple. Issue 3.0 July

276 Business Advocate flows Step Block Name Description 10 Preferred Agent NULL? Tests whether the value retrieved from the EDU for customerinfo.preferredagent is NULL. If the answer is: No, value is not NULL, proceeds to Step 11, Fetch LRMID. Yes, value is NULL, proceeds to Step 12, Create Agent Desktop Data 11 Fetch LRMID Fetches the LRM ID for the Logical Resource Manager associated with the preferred agent. 12 Create Agent Desktop Data Populates the EDU with the data that Avaya Agent and other agent desktop applications use for screen pops. Qualifiers This group of blocks, shown in the following figure, sets the qualifiers and other Business Advocate values for the contact Media Workflow Reference

277 Qualify Chat flow for Business Advocate The flow uses the following blocks to perform these functions: Step Block Name Description 13 Set Qualifier (Channel) 14 EDU Language NULL? 15 Map to Qualifier (Language) 16 Map to Qualifier (Language) Takes the value of chat in the $MediaType script variable for channel and adds the channel qualifier to collection of qualifiers for the contact in the sequence couple $scqualifiers Business Advocate includes the Channel qualifiers. A qualifier of category Channel is required as a valid Business Advocate qualifier. If no other qualifiers are set for a contact, Business Advocate uses the channel qualifier to match the contact with an agent. Tests whether the value of $EDUlanguage is NULL. If the answer is: Yes, value is NULL, proceeds to Step 15, Map to Qualifier (Language) No, value is not NULL, proceeds to Step 16, Map to Qualifier (Language). 1. Compares the value of $custlanguage to one of four possible values listed on the Basic tab. These qualifier values are the two character IS language codes. 2. If the value of $custlanguage matches a possible value, maps the ISO language code to the corresponding qualifier. For example, if the code is en, maps this code to english. 3. Assigns the qualifier value to the $language variable. 1. Compares the value of $EDUlanguage to one of four possible values listed on the Basic tab. These qualifier values are the two character IS language codes. 2. If the value of $EDUlanguage matches a possible value, maps the ISO language code to the corresponding qualifier. For example, if the code is en, maps this code to english. 3. Assigns the qualifier value to the $language variable. Issue 3.0 July

278 Business Advocate flows Step Block Name Description 17 Set Qualifier (Lang and CustType) Sets qualifiers for the categories of language and customertype in the sequence couple $scqualifiers For the language category, the block: 1. Retrieves the value for language from the $language script variable. 2. If a valid qualifier exists with the values language/<$language>, adds that qualifier to the collection of qualifiers for the contact. 3. If no valid qualifier exists and the DefaultQualifier value on the Basic tab contains a mapped value for the language, adds the default qualifier value to the collection of qualifiers for the contact. For the customertype category, the block: 1. Retrieves the value of customerinfo.customertype from the script variable. 2. If a valid qualifier exists with the values customertype/<$customertype>, adds that qualifier to the collection of qualifiers for the contact. 3. If no valid qualifier exists and the DefaultQualifier value on the Basic tab contains a mapped value for the language, adds the default qualifier value to the collection of qualifiers for the contact. 18 IVChat Enabled? Tests whether the value of $ivchatenabled is True. If the answer is: Yes, value is True, proceeds to Step 19, media=ivchat No, value is False, proceeds to Step 20, PVChat Enabled?. 19 media=ivchat Tests whether Business Advocate has a valid qualifier of media/ivchat. If the answer is: Yes, qualifier exists, proceeds to Step 22, Set Qualifier (Multimedia) No, qualifier does not exist, proceeds to Step 23, Find Value in SeqCouple 20 PVChat Enabled? Tests whether the value of $pvchatenabled is True. If the answer is: Yes, value is True, proceeds to Step 21, media=pvchat No, value is False, proceeds to Step 23, Find Value in SeqCouple 21 media=pvchat Tests whether Business Advocate has a valid qualifier of media/pvchat. If the answer is: Yes, qualifier exists, proceeds to Step 22, Set Qualifier (Multimedia) No, qualifier does not exist, proceeds to Step 23, Find Value in SeqCouple 278 Media Workflow Reference

279 Qualify Chat flow for Business Advocate Step Block Name Description 22 Set Qualifier (Multimedia) 23 Find Value in SeqCouple Sets the multimedia qualifier for the contact. If the qualifier is: media/ivchat Specifies that the chat customer intends or is able to make a Chat & VOIP contact with the agent. media/pvchat Specifies that the chat customer would like the agent to callback through a Chat & Phone connection. 1. Searches the $scroutinghint sequence couple created by the Fetch Routing Hints block for a couple with the name of intent. 2. If the intent couple exists, extracts the value of that couple and assigns it to the script variable $CoupleValue. 24 Set Qualifier (intent) 1. Uses the value in $CoupleValue to set the value of the intent qualifier. 2. Adds the intent qualifier to the collection of qualifiers for the contact in the sequence couple $scqualifiers For example, if the value for $CoupleValue was set to sales by the Find Value in SeqCouple block, this block sets the intent qualifier to intent/sales. Post qualification This group of blocks does the following: 1. Configures the wait treatment sequence for the contact. 2. Translates the collection of qualifiers set by the Set Qualifier blocks into a numeric sequence. 3. Calls the postqualification method of the WAA server. Important:! Important: If you customize this workflow, you must preserve the order and position of this group of blocks in the flow Issue 3.0 July

280 Business Advocate flows The flow uses the following blocks to perform these functions: Step Block Name Description 25 Set Chat Wait Treatment 26 Translate Category/Qualifier Lets you build a scripted sequence of wait treatment responses to the chat contact. Use the following three properties on the Basic tab to create the step in the sequence that the current block represents: PushURL The URL of a web page to push to the Web browser of the customer waiting to chat with an agent. SayText A text string, typically in the form of a sentence to push to the chat application window of a customer waiting to chat with an agent. WaitTime The time in seconds that you want Web Management to display this sequence. For example, enter a value of -1 if you want Web Management to show the sequence indefinitely. This block collects these values into the sequence couple property ChatWaitSequence. Use this block several times in the workflow to create a complex chat wait treatment script. Warning: Do not use this block after the Post Qualification block. 1. Transforms the sequence couple $scqualifiers from a collection of qualifiers in name value pairs to a string that contains the numeric transformation of these qualifiers. 2. Starts to build a new sequence couple for the script variable $scroutinghints. This sequence couple contains the routinginfo container in the current advocate container of the EDU. 3. Adds the field qualifiers to the advocate.routinginfo container. 27 Post Qualification 1. Uses the following script variables set in the workflow to call the postqualification method of the TSA server: - $waittreatmentstyle - $qualifier_set - $PreferedAgent -$LRMid 2. Sets the PostQualificationAction to route and sets ExcludeAgent to no. 3. Adds the following fields to the variable $scroutinghints, then writes those fields to the EDU: - agent_id - exclusion_flag - waittreatmentstyle -action - lrmid_key 280 Media Workflow Reference

281 Qualify flow for Business Advocate Stop flow The Stop block marks the exit point for the workflow. After the Stop block, the Workflow server executes the On Exit block. Qualify flow for Business Advocate The Qualify flow identifies a collection of Business Advocate qualifiers for an contact. Business Advocate then uses these qualifiers to accurately match the contact with: A qualified agent who can handle the request. A qualified supervisor who can review the response from the agent. The Web Advocate Adaptor (WAA) server starts the Qualify flow. The Qualify flow for Business Advocate can use the values from the customerinfo container of the EDU as part of the collection of hints used to qualify an . With this configuration, you can configure the qualification logic to not use an Analysis flow to pre-qualify the contact. Instead, you can use only the customer data to determine the routing hints. The customer data includes customertype and language. If you customize the Qualify flow for Business Advocate to use data from the customerinfo container, you must ensure this data is available for outbound contacts that require supervisor approval. To make the data available for outbound, before the workflow identifies the complete qualifier set for the SUP type, insert an Add Routing Hint block that adds these values to the list of routing hints. For more information about how Business Advocate routes contacts, see IC Business Advocate Configuration and Administration. Issue 3.0 July

282 Business Advocate flows The sample Qualify flow is shown in the following figure. Group the blocks of the sample Qualify flow into several steps to see how the workflow qualifies an contact. For example, this workflow contains the following groups of blocks: 1. Input parameters and EDU values on page Contact information on page Channel qualifier on page Media Workflow Reference

283 Qualify flow for Business Advocate 4. Preferred agent on page Routing hints on page Qualifiers for approval on page Qualifiers for contact on page Post qualification on page Stop flow on page 298. Input parameters and EDU values The first group of blocks gets EDU values for the contact, as shown in the following figure The Qualify flow uses the following blocks to perform these functions: Step Block Name Description Start Flow 1 Get Input Parameters Starts the workflow. Incorporates the code for getting a unique database network session for database access through its DBNetwork property. Retrieves values for the input parameters listed on the Basic tab and enters the values in the specified symbols 2 Fetch EDU Fetches the EDU for the contact. Issue 3.0 July

284 Business Advocate flows Step Block Name Description 3 Get EDU Values Retrieves the value of the EDU attributes that are specified in the Field properties on the Basic tab. The EDU attributes include the following: current .fromaddress Assigns the address in the From field to the script variable $fromaddress. current .toaddress Assigns the address in the To field to the script variable $toaddress. current . type Assigns the type of the contact to the script variable $ type. For example, the type can be one of the following: NOR, SME, SUP. customer_fetched Indicates whether the Customer record has already been fetched. type Assigns the value of the channel type of the contact to the $MediaType script variable. preferredagentname Assigns the login ID of the preferred agent to receive this contact to the script variable $EDUPreferedAgent. For example, the EDU for an contact includes preferred agent information if the is a response to a request for additional information. current .msgid Assigns the message ID of the current contact to the script variable $msgid. The Fetch Routing Hints block uses this variable to fetch the hints from the qw_qualifier table in the CCQ database. rootmsgid Assigns the message ID of the original incoming contact to the script variable $rootmsgid. The Fetch Routing Hints block uses this variable to fetch the hints from the qw_qualifier table in the CCQ database. Contact information After the Qualify flow gets input parameters and EDU values, the workflow sets additional values for the contact. The values set by the second group of blocks, 284 Media Workflow Reference

285 Qualify flow for Business Advocate shown in the following figure, provide more information to assist the agent with the customer The flow uses the following blocks to perform these functions: Step Block Name Description 4 CustomerFetched? Tests whether the value of the customer_fetched field is NULL. A NULL value indicates that the attempt to find the Customer record has not yet been performed. If the answer is: Yes, value is NULL, proceeds to Step 5, Type = NOR?. No, value is not NULL, proceeds to Step 9, Get Customer Values. 5 Type = NOR? Tests whether the type of the contact is NOR. A NOR type indicates that this contact is an inbound from a customer. If the answer is: Yes, type is NOR, proceeds to Step 6, Fetch Customer record (fromaddr). No, type is not NOR, proceeds to Step 9, Get Customer Values. Issue 3.0 July

286 Business Advocate flows Step Block Name Description 6 Fetch Customer record (fromaddr) Attempts to fetch a record from the Customer table of the CCQ database with the current .fromaddress value in the $fromaddress variable. 1. Checks the database for a Customer record that matches the current .fromaddress value. 2. Sets a NumRecords value for the number of records that match the customerinfo.role. 3. If only one Customer record is available, retrieves the specified values from the Customer record and writes the values to the customerinfo container of the EDU. To modify the values that the block retrieves from the Customer record, add or modify a pair of Field_N and Value_N parameters on the Basic tab. The field must correspond to a field in the Customer table. 7 RecordCount=1 Tests the NumRecords value set by the Fetch Customer Record block to see if the value is 1. If the answer is: Yes, the value is 1, proceeds to Step 8, Fetch EDU. No, the value is not 1, proceeds to Step 10, Create Agent Desktop Data. 8 Fetch EDU Fetches the EDU data again to ensure that the workflow uses the EDU data with the actual Customer data retrieved by the Fetch Customer Record block. 9 Get Customer Values 10 Create Agent Desktop Data Gets the following values for the customer from the customerinfo container of the EDU that Business Advocate uses to help match the customer with an agent: customerinfo.preferredagent Login ID of the Avaya IC agent who is the preferred agent for the customer. customerinfo.language Preferred language of the customer. customerinfo.customertype Value that can identify the relative worth of this customer to the Enterprise. For example, this value is typically set to gold, silver, or bronze for Business Advocate demonstrations. Populates the EDU with the data that Avaya Agent and other agent desktop applications use for screen pops. 286 Media Workflow Reference

287 Qualify flow for Business Advocate Channel qualifier The next block in the Qualify flow, shown in the following figure, sets the channel qualifier for the contact. 11 The flow uses the following blocks to perform these functions: Step Block Name Description 11 Set Qualifier (Channel) Takes the value of in the $MediaType script variable for channel and adds the channel qualifier to collection of qualifiers for the contact in the sequence couple $scqualifiers Business Advocate includes the Channel qualifiers. A qualifier of category Channel is a required Business Advocate qualifier. If no other qualifiers are set for a contact, Business Advocate uses the channel qualifier to match the contact with an agent. Preferred agent The next group of blocks in the Qualify flow, shown in the following figure, determines whether the contact has a preferred agent and, if so, fetches the LRM ID associated with that agent Issue 3.0 July

288 Business Advocate flows The flow uses the following blocks to perform these functions: Step Block Name Description 12 EDU PreferedAgent = NULL Tests whether the value retrieved from the EDU for preferredagentname is NULL. If the answer is: Yes, value is NULL, proceeds to Step 14, PreferedAgent NULL? No, value is not NULL, proceeds to Step 13, Fetch LRMID. 13 Fetch LRMID Fetches the LRM ID for the Logical Resource Manager associated with the preferred agent. After this step is complete, proceeds to Step 38, Translate Category/Qualifier. Routing hints The next group of blocks in the Qualify flow, shown in the following figure, checks whether the contact has associated routing hints Media Workflow Reference

289 Qualify flow for Business Advocate The flow uses the following blocks to perform these functions: Step Block Name Description 14 PreferedAgent NULL? Tests whether the value for preferred agent in the customer record is NULL. If the answer is: No, value is not NULL, proceeds to Step 15, Fetch LRMID. Yes, value is NULL, proceeds to Step 16, Fetch Routing Hints (msgid) 15 Fetch LRMID Fetches the LRM ID for the Logical Resource Manager associated with the preferred agent. 16 Fetch Routing Hints (msgid) 1. Fetches all routing hints that were assigned to the msgid of the contact. This block fetches the hints from the qw_qualifier table in the CCQ database. 2. Adds the category and value information from the qualifiers to the $scroutinghint sequence couple. 17 Type = SUP? Tests whether the value for the type in the $ type variable is SUP. If the answer is: Yes, value is SUP, proceeds to Step 16, Fetch Routing Hints (msgid) No, value is not SUP, proceeds to Step 15, Fetch LRMID. Issue 3.0 July

290 Business Advocate flows Qualifiers for approval If the type is SUP, the Qualify flow uses this group of blocks, shown in the following figure, to set the qualifiers and other Business Advocate values for an contact which requires supervisor approval The flow uses the following blocks to perform these functions: Step Block Name Description 18 Fetch Routing Hints (rootmsgid) 1. Fetches all routing hints that were assigned to the rootmsgid of the contact. This block fetches the hints from the qw_qualifier table in the CCQ database. 2. Adds the category and value information from the qualifiers to the $scroutinghint sequence couple. 19 Add Routing Hints 1. Checks the EDU for the values of the following routing hints: - language -customertype 2. Adds these values to the $scroutinghints variable that is used by Set Qualifier blocks later in the workflow. Note: To use routing hints, you must add them to the RoutingHint table in IC Manager. For more information, see IC Installation and Configuration and IC Administration Volume 1: Servers & Domains. 290 Media Workflow Reference

291 Qualify flow for Business Advocate Step Block Name Description 20 Find Value in SeqCouple 1. Searches the $scroutinghint sequence couple created by the Fetch Routing Hints block for a couple with the name of QA. 2. If the QA couple exists, extracts the value of that couple and assigns it to the script variable $CoupleValue. If the value is: Found, proceeds to Step 21, Set Qualifier (QA). Not found, proceeds to Step 22, Find Value in SeqCouple. 21 Set Qualifier (QA) Sets qualifier for the category of QA in the sequence couple $scqualifiers: 1. Retrieves the value for QA from the $CoupleValue script variable. 2. If a valid qualifier exists with the values QA/approvalrequired or QA/suspectcontent, adds that qualifier to the collection of qualifiers for the contact. 3. If no valid qualifier exists and the DefaultQualifier value on the Basic tab contains a mapped value for the intent, adds the default qualifier value to the collection of qualifiers for the contact. 22 Find Value in SeqCouple 1. Searches the $scroutinghint sequence couple created by the Fetch Routing Hints block for a couple with the name of intent. 2. If the intent couple exists, extracts the value of that couple and assigns it to the script variable $CoupleValue. If the value is: Found, proceeds to Step 23, Set Qualifier (intent). Not found, proceeds to Step 24, Find Value in SeqCouple. 23 Set Qualifier (intent) Sets qualifier for the category of intent in the sequence couple $scqualifiers: 1. Retrieves the value for intent from the $CoupleValue script variable. 2. If a valid qualifier exists with the values intent/<intent>, adds that qualifier to the collection of qualifiers for the contact. 3. If no valid qualifier exists and the DefaultQualifier value on the Basic tab contains a mapped value for the intent, adds the default qualifier value to the collection of qualifiers for the contact. For example, if the value for $CoupleValue was set to sales by the Fetch Routing Hints block, this block sets the intent qualifier to intent/sales. Issue 3.0 July

292 Business Advocate flows Step Block Name Description 24 Find Value in SeqCouple 25 Set Qualifier (Language) 1. Searches the $scroutinghint sequence couple created by the Fetch Routing Hints block for a couple with the name of language. 2. If the language couple exists, extracts the value of that couple and assigns it to the script variable $CoupleValue. Sets qualifier for the category of language in the sequence couple $scqualifiers: 1. Retrieves the value for language from the $CoupleValue script variable. 2. If a valid qualifier exists with the values language/<$language>, adds that qualifier to the collection of qualifiers for the contact. 3. If no valid qualifier exists and the DefaultQualifier value on the Basic tab contains a mapped value for the language, adds the default qualifier value to the collection of qualifiers for the contact. After this step is complete, proceeds to Step 38, Translate Category/Qualifier. 292 Media Workflow Reference

293 Qualify flow for Business Advocate Qualifiers for contact If the type of the contact is not SUP, the Qualify flow uses this group of blocks, shown in the following figure, to set the qualifiers and other Business Advocate values for an contact The flow uses the following blocks to perform these functions: Step Block Name Description 26 RecordCount > 0 Tests the NumRecords value set by the Fetch Customer Record block to see if the value is greater than 0. If the answer is: No, the value is not greater than 0, proceeds to Step 27, Map to Qualifier (toaddress). Yes, the value is greater than 0, proceeds to Step 31, Find Value in SeqCouple. Issue 3.0 July

294 Business Advocate flows Step Block Name Description 27 Map to Qualifier (toaddress) 1. Compares the value of $toaddress to one of four possible values listed on the Basic tab. These values are the addresses to which customers can send contacts. 2. If the value of $toaddress matches a possible value, maps the address to the corresponding qualifier. For example, if the address is sales@xyzcorp.com, maps this code to sales. 3. Assigns the qualifier value to the $intent variable. Note: By default, two addresses are entered in this block. These addresses are not valid for a customer system. You must configure at least one address in Value_1 that matches a valid address to which customers can send contacts. 28 Set Qualifier (intent) Sets qualifier for the category of intent in the sequence couple $scqualifiers: 1. Retrieves the value for intent from the $intent script variable. 2. If a valid qualifier exists with the values intent/<intent>, adds that qualifier to the collection of qualifiers for the contact. 3. If no valid qualifier exists and the DefaultQualifier value on the Basic tab contains a mapped value for the intent, adds the default qualifier value to the collection of qualifiers for the contact. For example, if the value for $CoupleValue was set to sales by the Fetch Routing Hints block, this block sets the intent qualifier to intent/sales. 29 Map to Qualifier (custlanguage) 1. Compares the value of $custlanguage to one of four possible values listed on the Basic tab. These qualifier values are the two character IS language codes. 2. If the value of $custlanguage matches a possible value, maps the ISO language code to the corresponding qualifier. For example, if the code is en, maps this code to english. 3. Assigns the qualifier value to the $language variable. 294 Media Workflow Reference

295 Qualify flow for Business Advocate Step Block Name Description 30 Set Qualifier (Language) 31 Find Value in SeqCouple Sets qualifier for the category of language in the sequence couple $scqualifiers: 1. Retrieves the value for language from the $language script variable. 2. If a valid qualifier exists with the values language/<$language>, adds that qualifier to the collection of qualifiers for the contact. 3. If no valid qualifier exists and the DefaultQualifier value on the Basic tab contains a mapped value for the language, adds the default qualifier value to the collection of qualifiers for the contact. After this step is complete, proceeds to Step 37, Set Qualifier (customertype). 1. Searches the $scroutinghint sequence couple created by the Fetch Routing Hints block for a couple with the name of intent. 2. If the intent couple exists, extracts the value of that couple and assigns it to the script variable $CoupleValue. If the value is: Found, proceeds to Step 32, Set Qualifier (intent). Not found, proceeds to Step 33, Find Value in SeqCouple. 32 Set Qualifier (intent) Sets qualifier for the category of intent in the sequence couple $scqualifiers: 1. Retrieves the value for intent from the $CoupleValue script variable. 2. If a valid qualifier exists with the values intent/<intent>, adds that qualifier to the collection of qualifiers for the contact. 3. If no valid qualifier exists and the DefaultQualifier value on the Basic tab contains a mapped value for the intent, adds the default qualifier value to the collection of qualifiers for the contact. For example, if the value for $CoupleValue was set to sales by the Fetch Routing Hints block, this block sets the intent qualifier to intent/sales. Issue 3.0 July

296 Business Advocate flows Step Block Name Description 33 Find Value in SeqCouple 34 Map to Qualifier (language) 35 Map to Qualifier (custlanguage) 36 Set Qualifier (Language) 1. Searches the $scroutinghint sequence couple created by the Fetch Routing Hints block for a couple with the name of language. 2. If the language couple exists, extracts the value of that couple and assigns it to the script variable $CoupleValue. If the value is: Found, proceeds to Step 34, Map to Qualifier (language). Not found, proceeds to Step 35, Map to Qualifier (custlanguage). 1. Compares the value of $CoupleValue to one of four possible values listed on the Basic tab. These qualifier values are the two character IS language codes. 2. If the value of $CoupleValue matches a possible value, maps the ISO language code to the corresponding qualifier. For example, if the code is en, maps this code to english. 3. Assigns the qualifier value to the $language variable. 1. Compares the value of $custlanguage to one of four possible values listed on the Basic tab. These qualifier values are the two character IS language codes. 2. If the value of $custlanguage matches a possible value, maps the ISO language code to the corresponding qualifier. For example, if the code is en, maps this code to english. 3. Assigns the qualifier value to the $language variable. Sets qualifier for the category of language in the sequence couple $scqualifiers: 1. Retrieves the value for language from the $language script variable. 2. If a valid qualifier exists with the values language/<$language>, adds that qualifier to the collection of qualifiers for the contact. 3. If no valid qualifier exists and the DefaultQualifier value on the Basic tab contains a mapped value for the language, adds the default qualifier value to the collection of qualifiers for the contact. 296 Media Workflow Reference

297 Qualify flow for Business Advocate Step Block Name Description 37 Set Qualifier (customertype) Sets the qualifier for the category of customertype in the sequence couple $scqualifiers: 1. Retrieves the value of customerinfo.customertype from the script variable. 2. If a valid qualifier exists with the values customertype/<$customertype>, adds that qualifier to the collection of qualifiers for the contact. 3. If no valid qualifier exists and the DefaultQualifier value on the Basic tab contains a mapped value for the customer type, adds the default qualifier value to the collection of qualifiers for the contact. Post qualification This group of blocks does the following: 1. Translates the collection of qualifiers set by the Set Qualifier blocks into a numeric sequence. 2. Calls the postqualification method of the WAA server. Important:! Important: If you customize this workflow, you must preserve the order and position of this group of blocks in the flow Issue 3.0 July

298 Business Advocate flows The flow uses the following blocks to perform these functions: Step Block Name Description 38 Translate Category/Qualifier 1. Transforms the sequence couple $scqualifiers from a collection of qualifiers in name value pairs to a string that contains the numeric transformation of these qualifiers. 2. Starts to build a new sequence couple for the variable $scroutinghints. This sequence couple contains the routinginfo container in the current advocate container of the EDU. 3. Adds the field qualifiers to the advocate>routinginfo container. 39 Post Qualification 1. Uses the following script variables set in the workflow to call the postqualification method of the WAA server: - $qualifier_set - $PreferedAgent -$LRMid 2. Sets the PostQualificationAction to route and sets ExcludeAgent to no. 3. Adds the following fields to the variable $scroutinghints, then writes those fields to the EDU: - agent_id - exclusion_flag -action - lrmid_key Stop flow The Stop block marks the exit point for the workflow. After the Stop block, the Workflow server executes the On Exit block. 298 Media Workflow Reference

299 Creating an EDU Dictionary Chapter 11: Advanced concepts This section describes some advanced concepts and functions that you can implement in media workflows. This section includes the following topics. Creating an EDU Dictionary on page 299. Using properties and symbols on page 300. Using library files on page 309. Working with semaphores on page 313. Examples of semaphores on page 318. For information about other advanced concepts for all types of workflows and for Workflow Designer, see Avaya Workflow Designer User Guide. Creating an EDU Dictionary The EDU Dictionary is a list of EDU field names. Most workflows use EDU field names. For example, contact routing flows fetch and set EDU values when determining how to route a contact. To ensure that flows use EDU field names consistently, maintain an EDU Dictionary in Workflow Designer. To create an EDU Dictionary: 1. Select Project > Symbols > EDU Fields. 2. In the edu Fields dialog box, select New. 3. In the Create New edu Field dialog box: a. Enter the field name in the edu Field. b. If desired, enter a description of the field in the Description field. c. If desired, select the Use Alternate Display Name option and enter the name you want the users to see a different name than the EDU field name, in capital letters. 4. Select OK to add the EDU symbol to the EDU dictionary. Your new EDU symbol is also added to the general Symbol Dictionary. For more information, see Using properties and symbols on page 300. Issue 3.0 July

300 Advanced concepts Importing an EDU Dictionary You can import a comma-separated text file to use as an EDU Dictionary. To import an EDU Dictionary: 1. Select Project > Symbols > edu Fields. 2. Select Import. 3. Enter the name of the file you want to import into Workflow Designer. Note: Note: All file names must be unique. If a symbol name already exists, Workflow Designer overwrites the existing symbol with the imported symbol. Exporting an EDU Dictionary You can export an EDU Dictionary to a text file. The text file contains the symbols from the EDU Dictionary in a comma-separated list. To import an EDU Dictionary: 1. Select Project > Symbols > edu Fields. 2. Select Export. 3. Enter a name for the file you want to export from Workflow Designer. Using properties and symbols Workflow Designer manages data for workflows with: Project symbols defined in the Symbol Dictionary for each project Properties for configuring blocks Global couples for communicating between flows at runtime Workflow Designer supports variable symbols and constant symbols. Data types for symbols include string, integer, couple, and sequence. For more information about properties and symbols, see: Project Symbol Dictionary on page 301 Variable symbols on page Media Workflow Reference

301 Using properties and symbols Constant symbols on page 306 Global variables on page 307 Auto-defined symbols on page 308 Project Symbol Dictionary Every project has its own Symbol Dictionary (also known as a symbol table). The project Symbol Dictionary contains all the symbols that you create for a project. Note: Note: A project can have only one Symbol Dictionary. Use the Symbol Viewer, shown in the following figure, to manage symbols in a project Symbol Dictionary. You can do the following with a project Symbol Dictionary: Creating symbols on page 302 Editing symbols on page 303 Deleting symbols on page 303 Importing a Symbol Dictionary from another project on page 304 Exporting a Symbol Dictionary on page 304 Issue 3.0 July

302 Advanced concepts Creating symbols You can create new symbols, including constants and variables, at any time. If a symbol has already been created in the Symbol Dictionary for another project, you can import the Symbol Dictionary from that project For more information, see Importing a Symbol Dictionary from another project on page 304. If you are unsure which type of symbol you need, see: Variable symbols on page 305 Constant symbols on page 306 Global variables on page 307 Auto-defined symbols on page 308 To create a new symbol: 1. Select Project > Symbols > All Symbols. You must open a project before you can make changes to a project s Symbol Dictionary. 2. Select New to open the Create New Symbol dialog box, shown in the following figure. 3. In the Create New Symbol dialog box: a. Enter a name for the symbol in the Name field. The name displays in the Symbol column of the Symbol Viewer. b. Enter a description of the variable in the Description field. The description is displayed in the Comment column of the Symbol Viewer. c. Select the type of symbol from the drop-down Type list. 302 Media Workflow Reference

303 Using properties and symbols Editing symbols d. For a constant symbol, check the Constant box and enter the pre-defined value in the Value field. If the Constant box is not available, you cannot create a Constant symbol for the selected symbol type. e. Select OK. 4. Select OK to close the Symbol Viewer. You can change the definition for any symbol in your project s Symbol Dictionary. To edit the definition for an existing symbol: 1. Select Project > Symbols > All Symbols. 2. Select a symbol name in the Symbol Viewer. 3. Select Edit to open the Edit Symbol Definition dialog box, shown in the following figure. 4. Make the desired changes to any field in the definition. 5. Select OK. 6. Select OK to close the Symbol Viewer. Deleting symbols You cannot run or compile a workflow if you delete a symbol used by in the workflow. To delete a symbol: 1. Select Project > Symbols > All Symbols. 2. Select a symbol name in the Symbol Viewer. 3. Select Delete to delete the symbol. 4. Select OK to close the Symbol Viewer. Issue 3.0 July