Avaya Callback Assist Considerations for Avaya Call Management System Release 4.6.2.0 December 2017
2015-2017 Avaya Inc. All Rights Reserved. Notice While reasonable efforts have been made to ensure that the information in this document is complete and accurate at the time of printing, Avaya assumes no liability for any errors. Avaya reserves the right to make changes and corrections to the information in this document without the obligation to notify any person or organization of such changes. Documentation disclaimer Documentation means information published by Avaya in varying mediums which may include product information, operating instructions and performance specifications that Avaya may generally make available to users of its products and Hosted Services. Documentation does not include marketing materials. Avaya shall not be responsible for any modifications, additions, or deletions to the original published version of documentation unless such modifications, additions, or deletions were performed by Avaya. End User agrees to indemnify and hold harmless Avaya, Avaya's agents, servants and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this documentation, to the extent made by End User. Link disclaimer Avaya is not responsible for the contents or reliability of any linked websites referenced within this site or documentation provided by Avaya. Avaya is not responsible for the accuracy of any information, statement or content provided on these sites and does not necessarily endorse the products, services, or information described or offered within them. Avaya does not guarantee that these links will work all the time and has no control over the availability of the linked pages. Warranty Avaya provides a limited warranty on Avaya hardware and software. 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 to Avaya customers and other parties through the Avaya Support website: http://support.avaya.com or such successor site as designated by Avaya. Please note that if You acquired the product(s) from an authorized Avaya Channel Partner outside of the United States and Canada, the warranty is provided to You by said Avaya Channel Partner and not by Avaya. Licenses THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA WEBSITE, HTTP://SUPPORT.AVAYA.COM/LICENSEINFO OR SUCH SUCCESSOR SITE AS DESIGNATED BY AVAYA, ARE APPLICABLE TO ANYONE WHO DOWNLOADS, USES AND/OR INSTALLS AVAYA SOFTWARE, PURCHASED FROM AVAYA INC., ANY AVAYA AFFILIATE, OR AN AVAYA CHANNEL PARTNER (AS APPLICABLE) UNDER A COMMERCIAL AGREEMENT WITH AVAYA OR AN AVAYA CHANNEL PARTNER. UNLESS OTHERWISE AGREED TO BY AVAYA IN WRITING, AVAYA DOES NOT EXTEND THIS LICENSE IF THE SOFTWARE WAS OBTAINED FROM ANYONE OTHER THAN AVAYA, AN AVAYA AFFILIATE OR AN AVAYA CHANNEL PARTNER; AVAYA RESERVES THE RIGHT TO TAKE LEGAL ACTION AGAINST YOU AND ANYONE ELSE USING OR SELLING THE SOFTWARE WITHOUT A LICENSE. BY INSTALLING, DOWNLOADING OR USING THE SOFTWARE, OR AUTHORIZING OTHERS TO DO SO, YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE INSTALLING, DOWNLOADING OR USING THE SOFTWARE (HEREINAFTER REFERRED TO INTERCHANGEABLY AS YOU AND END USER ), AGREE TO THESE TERMS AND CONDITIONS AND CREATE A BINDING CONTRACT BETWEEN YOU AND AVAYA INC. OR THE APPLICABLE AVAYA AFFILIATE ( AVAYA ). Avaya grants You a license within the scope of the license types described below, with the exception of Heritage Nortel Software, for which the scope of the license is detailed below. Where the order documentation does not expressly identify a license type, the applicable license will be a Designated System License. The applicable number of licenses and units of capacity for which the license is granted will be one (1), unless a different number of licenses or units of capacity is specified in the documentation or other materials available to You. Software means computer programs in object code, provided by Avaya or an Avaya Channel Partner, whether as stand-alone products, preinstalled on hardware products, and any upgrades, updates, patches, bug fixes, or modified versions thereto. Designated Processor means a single stand-alone computing device. Server means a Designated Processor that hosts a software application to be accessed by multiple users. Instance means a single copy of the Software executing at a particular time: (i) on one physical machine; or (ii) on one deployed software virtual machine ( VM ) or similar deployment. License type(s) Designated System(s) License (DS). End User may install and use each copy or an Instance of the Software only on a number of Designated Processors up to the number indicated in the order. Avaya may require the Designated Processor(s) to be identified in the order by type, serial number, feature key, Instance, location or other specific designation, or to be provided by End User to Avaya through electronic means established by Avaya specifically for this purpose. Copyright Except where expressly stated otherwise, no use should be made of materials on this site, the Documentation, Software, Hosted Service, or hardware provided by Avaya. All content on this site, the documentation, Hosted Service, and the product provided by Avaya including the selection, arrangement and design of the content is owned either by Avaya or its licensors and is protected by copyright and other intellectual property laws including the sui generis rights relating to the protection of databases. You may not modify, copy, reproduce, republish, upload, post, transmit or distribute in any way any content, in whole or in part, including any code and software unless expressly authorized by Avaya. Unauthorized reproduction, transmission, dissemination, storage, and or use without the express written consent of Avaya can be a criminal, as well as a civil offense under the applicable law. Third Party Components Third Party Components mean certain software programs or portions thereof included in the Software or Hosted Service may contain software (including open source software) distributed under third party agreements ( Third Party Components ), which contain terms regarding the rights to use certain portions of the Software ( Third Party Terms ). As required, information regarding distributed Callback Assist Considerations for Avaya Call Management System December 2017 2
Linux OS source code (for those products that have distributed Linux OS source code) and identifying the copyright holders of the Third Party Components and the Third Party Terms that apply is available in the products, Documentation or on Avaya s website at: http://support.avaya.com/copyright or such successor site as designated by Avaya. You agree to the Third Party Terms for any such Third Party Components. THIS PRODUCT IS LICENSED UNDER THE AVC PATENT PORTFOLIO LICENSE FOR THE PERSONAL USE OF A may own the Mark. Nothing contained in this site, the Documentation, Hosted Service(s) and product(s) should be construed as granting, by implication, estoppel, or otherwise, any license or right in and to the Marks without the express written permission of Avaya or the applicable third party. Avaya is a registered trademark of Avaya Inc. All non-avaya trademarks are the property of their respective owners. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. CONSUMER OR OTHER USES IN WHICH IT DOES NOT RECEIVE REMUNERATION TO (i) ENCODE VIDEO IN COMPLIANCE WITH THE AVC STANDARD ( AVC VIDEO ) AND/OR (ii) DECODE AVC VIDEO THAT WAS ENCODED BY A CONSUMER ENGAGED IN A PERSONAL ACTIVITY AND/OR WAS OBTAINED FROM A VIDEO PROVIDER LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS GRANTED OR SHALL BE IMPLIED FOR ANY OTHER USE. ADDITIONAL INFORMATION MAY BE OBTAINED FROM MPEG LA, L.L.C. SEE HTTP://WWW.MPEGLA.COM. Note to Service Provider The product or Hosted Service may use Third Party Components subject to Third Party Terms that do not allow hosting and require a Service Provider to be independently licensed for such purpose. It is your responsibility to obtain such licensing. Preventing Toll Fraud Toll Fraud is the unauthorized use of your telecommunications system by an unauthorized party (for example, a person who is not a corporate employee, agent, subcontractor, or is not working on your company's behalf). Be aware that there can 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 Toll 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 +1-800- 643-2353 for the United States and Canada. For additional support telephone numbers, see the Avaya Support website: http://support.avaya.com or such successor site as designated by Avaya. Suspected security vulnerabilities with Avaya products should be reported to Avaya by sending mail to: securityalerts@avaya.com. Downloading Documentation For the most current versions of Documentation, see the Avaya Support website: http://support.avaya.com, or such successor site as designated by Avaya. Contact Avaya Support See the Avaya Support website: http://support.avaya.com for product or Hosted Service notices and articles, or to report a problem with your Avaya product or Hosted Service. For a list of support telephone numbers and contact addresses, go to the Avaya Support website: http://support.avaya.com (or such successor site as designated by Avaya), scroll to the bottom of the page, and select Contact Avaya Support. Trademarks The trademarks, logos and service marks ( Marks ) displayed in this site, the Documentation, Hosted Service(s), and product(s) provided by Avaya are the registered or unregistered Marks of Avaya, its affiliates, or other third parties. Users are not permitted to use such Marks without prior written consent from Avaya or such third party which Callback Assist Considerations for Avaya Call Management System December 2017 3
Table of Contents Table of Contents About this document... 6 Intended audience... 6 Related documents... 6 Introduction... 7 Callback Assist CTI installation... 9 CMS view of terminated calls related to Callback registrations... 9 Minimizing the impact of artificial abandons on CMS reporting... 11 Performing registration response within Communication Manager instead of Callback Assist... 11 Offering Callback before putting the caller in queue... 13 Callback Assist SIP Installation... 15 Support for Communication Manager 6.2 feature ICR Pullback... 15 Support for Communication Manager 6.2 feature - No resources available... 15 Callback Assist Considerations for Avaya Call Management System December 2017 4
Table of Figures Table of Figures Figure 1 Standard Callback Assist vector... 9 Figure 2 Call reported as DISCONNECT... 10 Figure 3 Call reported as ABANDON... 10 Figure 4 Main vector with route-to... 12 Figure 5 Disconnected vector... 12 Figure 6 Disconnected vector with multiple language support... 13 Figure 7 Offering callback before putting the caller in queue... 14 Callback Assist Considerations for Avaya Call Management System December 2017 5
About this document About this document Avaya Callback Assist Considerations for Avaya Call Management System provides a description of scenarios in which Communication Manager reports a particular call to the Call Management System (CMS) as DISCONNECT or ABANDON, and offer guidance in minimizing any potential adverse effects to CMS reporting while maintaining the key improvements offered by Callback Assist. Intended audience The document is addressed to users who want to install Callback Assist. Related documents Avaya Callback Assist Considerations for Avaya Call Management System is part of the Callback Assist documentation set. The other documents in the documentation set are as follows: Avaya Callback Assist overview and planning guide Provides an overview and functional description of the CBA application. The document also lists the features of the CBA application and the environment configuration requirements to install the application. Installing and configuring Avaya Callback Assist Provides environment configuration requirements and procedural information to install and configure Callback Assist. Administering Avaya Callback Assist guide Provides information on administering and using CBA. Avaya Callback Assist reporting guide Provides information on the CBA Reporting feature. Avaya Callback Assist migration Guide Provides information on preparing the user for migrating to the latest version of Callback Assist and procedure to migrate. Avaya Callback Assist Web services API guide Provides information on Callback Assist Web services API. Avaya Callback Assist Release Notes Provides information on the latest version of Callback Assist. Callback Assist Considerations for Avaya Call Management System December 2017 6
Introduction Introduction Callback Assist provides a mechanism for callers and to the contact center to register for a callback when the expected wait times (EWT) exceed certain thresholds. The contact centers that employ this mechanism experience various operational improvements including the following: Improved customer satisfaction by empowering the caller to control how they interact with the contact center. Improved agent satisfaction as callers spend less time being frustrated by long queue times. Increased rates of achievement for Service Level Agreements (SLA's). Decreased overall abandoned call rates. Reduction in toll costs for both the contact center (less time spent waiting on hold via an 800 number) and the customer (fewer wireless minutes spent waiting on hold). Leveling of unpredictable call volume spikes and valleys. When the expected wait time for a caller is greater than the EWT threshold for the callback configuration associated with the queue, the system offers the caller an option to register for a callback by the contact center when agents are available or at a specific date and time in the future. Once the caller successfully registers for a callback, the system disconnects the call and removes the call from the queue. This disconnection can occur in one of following ways: Scenario 1: When the callback registration is complete, Callback Assist will out-pulse a Converse Data Return code to Communication Manager. Assuming that the caller is still on the call, the vector that originally sent the caller to Callback Assist will receive the converse data return value and initiate a vector disconnect step. Then the system immediately terminates further vector processing. Scenario 2: The caller may hang-up as soon as they hear the registration confirmation message played by Callback Assist. In such a case, the system returns the control to Communication Manager vector that sent the caller to Callback Assist and then terminates the vector processing immediately. There are subtle differences in the overall call flow for these scenarios, but the most important aspect to note is the outcome of the call, as reported by Communication Manager to the Call Management System (CMS). The report is different for both the scenarios. In Scenario 1, the call is reported by Communication Manager as a DISCONNECT. The call in Scenario 2 is reported as an ABANDON. This difference in reporting the call as a DISCONNECT or an ABANDON can have a significant impact on Key Performance Indicators (KPIs) for a contact center and lead to the mistaken belief that the service levels in the contact center have decreased. Callback Assist Considerations for Avaya Call Management System December 2017 7
Introduction The purpose of this document is to discuss the scenarios in which Communication Manager reports a particular call to the Call Management System (CMS) as DISCONNECT or ABANDON, and offer guidance in minimizing any potential adverse effects to CMS reporting while maintaining the key improvements offered by Callback Assist. Callback Assist Considerations for Avaya Call Management System December 2017 8
Callback Assist CTI installation Callback Assist CTI installation CMS view of terminated calls related to Callback registrations In the first scenario, the customer call is reported as a DISCONNECT while in the second scenario the call is reported as an ABANDON. The following sections show a typical Callback Assist enabled vector and the output of telephony traces conducted on a Communication Manager ACD for the two scenarios mentioned earlier. Callback Assist Enabled Vector Figure 1 Standard Callback Assist vector Callback Assist Considerations for Avaya Call Management System December 2017 9
Callback Assist CTI installation Scenario 1: Customer requests a call back and is disconnected by the vector Figure 2 Call reported as DISCONNECT Lines 10 through 14, as highlighted in the graphic shows the steps taken by the vector immediately following the successful receipt of the converse data return out-pulse from Callback Assist. In CMS, this call is shown as a DISCONNECT in the Vector, VDN, and Skill reports. Scenario 2: Customer hangs up immediately after requesting a call back (before being disconnected by the vector) Figure 3 Call reported as ABANDON Line 10 as highlighted in the graphic shows how Communication Manager processes the call without receiving a converse data return from Callback Assist. This is because the caller hung-up while still in Voice Portal. In CMS, this call is shown as an ABANDON in the Vector, VDN, and Skill. Callback Assist Considerations for Avaya Call Management System December 2017 10
Callback Assist CTI installation Minimizing the impact of artificial abandons on CMS reporting If abandon call rate is a KPI for your contact center, then you have two options related to the configuration of your vectors and Callback Assist that can alleviate any potential negative impact to your abandon call reporting for callback enabled skills. The options are as follows: Change the registration response to occur within Communication Manager instead of Callback Assist. Offer callback before putting the caller in queue. Performing registration response within Communication Manager instead of Callback Assist A summary of the procedure is as follows: 1. Create a silence WAV file, that is, a WAV file with only silence recorded in. The recommended length of the silence is one second. 2. Replace the OOTB confirmation WAV file, that is, the c0020.wav file on the Callback Assist server with the silence WAV file. The default confirmation WAV file is located in the folder: /opt/avaya/callbackassist/apache-tomcatddapps/webapps/cbaphrases/custom/customer/<language_name>/<loc ale>/c0020.wav where <language_name> and <locale> represent the specific language you are addressing. For example, if you were changing the prompt for US English the folder would be: /opt/avaya/callbackassist/apache-tomcatddapps/webapps/cbaphrases/custom/customer/englishus/enus/c0020.wav 3. On the Communication Manager vector that performs the converse-on step and the collection of the converse data return value, add a Route-To step to direct the caller to a disconnect vector. The purpose of the vector is to play the success message and then disconnect the caller. By routing the caller to a separate vector you are moving the caller out of the measured vector and ensuring that if they choose to hang-up before Communication Manager reaches the disconnect step, the artificial abandon is isolated. You can now be sure that calls reported as abandons in the measured vector are true abandons. Callback Assist Considerations for Avaya Call Management System December 2017 11
Callback Assist CTI installation Figure 4 Main vector with route-to Figure 5 Disconnected vector If you need to support multiple languages in your IVR messaging you can expand the disconnect vector to incorporate vector variables and select the appropriate, language-specific, message in the vector. Callback Assist Considerations for Avaya Call Management System December 2017 12
Callback Assist CTI installation Figure 6 Disconnected vector with multiple language support Offering Callback before putting the caller in queue This option involves determining if the caller should be offered CBA before actually queuing them. Making this determination first provides a way to keep callers who accept the callback offer from impacting the CMS measures for the skill. The following example depicts a vector where the expected wait time for the skill is checked first and then a decision is made whether to queue the caller immediately or offer them callback (step 02). If the caller is routed to callback they can still chose to remain in queue in which case the call is then queued to the skill by the vector (step 08). Callback Assist Considerations for Avaya Call Management System December 2017 13
Callback Assist CTI installation Figure 7 Offering callback before putting the caller in queue Callback Assist Considerations for Avaya Call Management System December 2017 14
Callback Assist SIP installation Callback Assist SIP Installation Support for Communication Manager 6.2 feature ICR Pullback Starting from Release 4.1, Callback Assist supports the ICR Pullback feature added to Communication Manager 6.2. This feature provides a mechanism for an adjunct application to mark specific calls as non-abandoned. From the perspective of Callback Assist, the general idea is that if a phantom call created by ICR or Callback Assist needs to be dropped, that is, pulled back, Callback Assist can indicate to Communication Manager that the phantom call should not be considered as an abandoned call thereby removing the potential for false abandon reporting in CMS. Callback Assist does not consider a dropped phantom call as abandoned when: A customer goes through all the Callback Assist offering menus and reaches confirmation that callback was left correctly. A phantom call is on queue and Callback Assist requests a new license port but there are no available ports. Callback Assist engine delivers a call and timeout for having phantom call on queue is met. Callback engine delivers a call on Customer First strategy, the customer is not available and there are no more callbacks to deliver. Dynamic Routing is configured and the dynamic VDN timeout is met, so the system goes to recovery. Callback Assist considers a dropped phantom call as abandoned when: A customer reaches Callback Assist and hangs up before reaching the confirmation message. A customer reaches Callback Assist, chooses to wait on the queue, and then hangs up. Callback Assist engine delivers a call on Customer First strategy and the customer hangs up before reaching an agent. Support for Communication Manager 6.2 feature - No resources available Starting from Release 4.1, when Callback Assist attempts to deliver a callback and requests a Callback Assist license port, but there are no more ports available or all the ports are in use, the system records this incident on CMS report as No resource available. Callback Assist Considerations for Avaya Call Management System December 2017 15