Intelligent Management

Transcription

1 Intelligent Management White Paper May, 2003 IP Telephony Contact Centers Unified Communication Services

2 T able of Contents: Section 1: Section 2: Section 3: Section 4: Section 5: Executive Summary The Challenge The Solution: Avaya Management Overview of Avaya Management Components Improving Agent Productivity and Quality Assurance Section 5.1: Quality Analysis Process Section 6: Management Effectiveness: Intelligent Workflow Driven Processing Section 6.1: Section 6.2: Section 6.3: Analyze Workflow Qualify Workflow Outbound Workflow Section 7: Improving Customer Satisfaction Section 7.1: Section 7.2: Section 7.3: Section 7.4: Section 7.5: Section 7.6: Auto Acknowledge Auto or Agent Directed Response Avaya Routing and Resource Matching Avaya Business Advocate for Avaya Interaction Center Routing Multiple Interactions / Document Matching Send Request to Subject Matter Expert Section 8: Intelligent Analysis Section 8.1: Section 8.2: Section 8.3: Section 8.4: Section 8.5: Sender Identification / Information Customer Segmentation Keyword Matching Content Analysis Determining Languages Section 9: Management Reporting and Analysis Section 9.1: Section 9.2: Specific Reports Specific Drill-Through Reports Section 10: Appendix A: Conclusion System Requirements

3 Section 1: Executive Summary Many companies struggle with processing their increasingly high volumes of efficiently and effectively. This can result in poor customer service and lost revenue opportunities. Fortunately, Avaya has developed a robust set of tools to better manage customer-initiated . The Avaya Management system provides intelligent tools to both reduce response times and improve the accuracy and quality of responses. Section 2: The Challenge In today s economy, companies are increasingly looking for ways to cut costs while staying competitive. With the increase of multiple communication channels like and web, customers are demanding immediate service to their inquiries. Specifically, with , expectations for a response to written inquiries are getting shorter. Are companies responding in a fast and accurate manner to their high valued customers? The reality is that companies are doing a poor job in managing customer s. A recent survey by Jupiter Research showed that while 88% of customers expect a response to their within 24 hours, only 54% of companies surveyed meet this expectation 1. The slow and impersonal attention to a customer s s can drastically damage the company s reputation and may cause customers to defect to the competition. Further, companies are struggling with high volumes and paying the high price for not incorporating better cost effective means to handle customer s interactions. With the figure below, Gartner measures that the cost of contact per contact type for poorly implemented can be as high as $28! $40.00 $30.00 $20.00 $10.00 $- Web Self- Service Web chat Phone selfservice Phone high low average $5.00 $0.25 $0.65 $28.00 $1.50 $2.50 $34.00 $3.00 $7.50 $12.00 $0.85 $1.85 $30.00 $2.50 $4.50 Gartner Copyright 2003 Figure 1: Cost of Interaction by Channel Type Source: Kolsky, Esteban, Customer Self-Service: Reducing Customer Maintenance, presentation, Gartner Group, 2003, slide Jupiter Research, JUPITER RESEARCH REPORTS THAT COMPANIES ARE FAILING AT ONLINE CUSTOMER SERVICE DESPITE GROWTH IN ONLINE CRM SPENDING, press release, 1

4 This means that it can be more expensive to implement if companies don t incorporate capabilities like automation and content analysis routing strategies into their business. The good news is that companies can achieve the low cost target if they have the right technology along with efficient and cost effective strategies. Therefore, incorporating the right management into customer service is a critical need. By establishing contact queues to respond to s from customers, companies can improve their efficiency, boost productivity and reduce costs. When evaluating solutions, companies are not simply looking for a point solution, but the option to have an integrated suite approach that will allow them to incorporate other channels like voice and web. Companies also need to decide to effectively segment, prioritize and intelligently route s to ensure that responses are appropriate and consistent with their corporate brand. If valued customers are ing, is the level of service and treatment matching their value? Are they also handled in an intelligent and effective manner? For example, is there a screening mechanism that allows supervisors to scan s from new agents? Quality and consistency of s is another major concern since it puts the company s answers in writing. The purpose of this paper is to cover: The Avaya Management technology and benefits Improved agent productivity and quality assurance effectiveness with intelligent workflow driven processing Customer satisfaction Self-service automation capabilities like Content Analysis Management reporting and analysis System requirements Section 3: The Solution: Avaya Management Avaya Management, an application within the Avaya Interaction Center software suite, provides intelligent automated and agent-assisted response capabilities to manage high volumes of efficiently. The Avaya solution can drive down costs by automating responses without the need for large numbers of live agents. Automatic responses, suggested responses, and auto-acknowledge can be triggered based on key words or natural language content analysis to determine the intent of the . In addition, content analysis can be utilized for routing, filtering and providing suggested responses. Avaya Management provides personalized treatment and routing. Incoming can be classified based upon the sender, the subject, or other criteria to create entitlements and route to appropriately skilled agents. These messages are queued based on the skills needed to answer them and the availability of those skills. They are routed to agents in a predetermined order based on the contact center's current load and agent skills available. The management system uses business rules to ensure service level. Avaya Management can also improve agent productivity and increase speed of service, through a set of templates, agent resources and suggested responses. 2

5 Below are a few examples of how to obtain some of the Avaya Management benefits. Improved customer service by providing rapid auto-acknowledgement messages for s that arrive during off hours to set customer expectations. Avaya offers built-in date/time functions to indicate in the acknowledgement message how many hours until the contact center agents will be available. Content analysis or keyword searching can also be used to provide a more customized response (for example, distinguish between new messages and replies to a prior from the contact center). Consistency in treatment regardless of language. In a multi-lingual contact center environment, automatic language recognition capability can route to a language-specific workflow that references the appropriate language. is delivered with the auto-suggest responses and template to the appropriate skilled agent. Matching the right agent to the right customer . A customer request may involve several agents (for example, due to multiple specialized requests in a single or a complex fulfillment process with multiple steps). A special workflow tracks the status of the transaction. Improve quality assurance of outbound . Content analysis is performed on outgoing responses to determine if a non-standard delivery commitment is being made to the customer. If this is detected, the message can be automatically routed to a Quality Assurance (QA) or review agent for further action. A standard, structured response with a web site link is provided for common requests (for example, status request for a current open order). requests are quickly identified and the appropriate information fields in the message are retrieved and acted on automatically. Tailored responses during times of corporate changes. For example, in the event of a major product recall, companies can use the content analysis capability to pre-sort the s according to whether the incoming requests information on the recall program. Automatic response capability retrieves Frequently Asked Questions (FAQ) and program information to be included in the response to the customer. Section 4: Overview of Avaya Management Components Avaya Management delivers intelligent and personalized service. The process entails: Incoming s from customers or web forms are delivered to a standard POP3 server. The is then polled and parsed by the Avaya Management system. Based on keywords, subject or content, s can be auto-acknowledged or auto-responded for routing to the most appropriate agent. When the agent receives the , they can use auto suggest templates or type the response. Outgoing s can then be routed to supervisors to review and then sent back to the customer. 31

6 Figure 2: Overview of Avaya Management Section 5: Improving Agent Productivity and Quality Assurance On the agent desktop, Avaya Management gives agents the necessary tools to effectively and efficiently handle s ( resources, canned libraries, templates and suggested responses). The system automatically presents agents with a screen pop of a caller's data from the desktop application being used with the customer s contact history (across multiple media) to save time and ensure personalized handling. The Agent interface presents controls and suggested templates to allow easy response to s that can dramatically increase the speed of response to common questions and ensure quality answers. The agent interface also includes spell check to ensure correct spelling and grammar. 4

7 A screen shot of the Avaya Web Agent interface for is shown in Figure 3. Figure 3: Agent Interface Section 5.1: Quality Analysis Process To ensure high quality responses, the Quality Assurance (QA) routing process can be configured within the Avaya workflow. This process has the following features: The Outbound flow automatically runs when the agent "sends the " to allow for business rules to be run on before it is sent to the customer. Business logic encoded in the workflows determines which responses will be sent through a quality assurance process. Options can be configured for including all from a specific agent, a random (%) sample, and/or specific content analysis topics (e.g. legal, confidential, bad language etc). Items that are selected for review are routed to an "approver" who can reject the causing it to be returned to the agent with comments on how to fix it. The approver can alternatively make edits and send the . This mechanism can be used as a mechanism of observing a new agent and providing training feedback. 5

8 The QA Review Agent has the ability to approve a response and send it out, edit the response and send it out, or reject the response (with or without comment) and return it to the originating agent. Avaya Management also comes with alerts, which provides the capability to set a timer to monitor for the timely receipt of an information request from an agent or customer. When configured, the appropriate time interval is set automatically by the Outgoing workflows. This capability allows the agent to meet any special service-level requirements set for the customer such as follow-up work, or when the requires and answers from and outside subject matter expert. When the timer expires, the agent is alerted automatically and can decide whether to follow-up on the current status of the request or to pursue another contingency. Section 6: Management Effectiveness: Intelligent W orkflow Driven processing An important component of Avaya Management is its ability to enable customized and intelligent workflow to suit the needs of the contact center s unique business requirements. Steps in the management process are managed through the use of the Interaction Center Workflow Designer engine. A Workflow Designer tool provides a mechanism to specify powerful retrieval, delivery, and information retrieval capabilities for -related transactions. Three standard types of sample workflows are provided as a starter set with Avaya Management. Analyze workflow - for initial processing Qualify workflow - for routing to a contact center agent Outbound workflow - for handling subsequent routing from an agent Section 6.1: Analyze Workflow The processing sequence provided by Analyze Workflow begins after the is retrieved from an external POP3 Server and ends with the transaction provided to the Qualify Workflow for delivery to the appropriate contact center agent. The Analyze Workflow analyzes the by examining To and From address fields (for example, to determine the routing destination and customer). Content analysis is applied to the Subject and/or Body of the message. Intent of the is identified to a level of detail that can be used for determining auto-acknowledgement and either an automated response and/or input to subsequence routing to a contact center agent. Important characteristics of the (for example, size of the message, whether attachments are included) are determined automatically by identifying and parsing various fields within the . These fields are stored in a customer history folder or Electronic Data Unit (edu), which is used to pass important information about the from one Interaction Center component to another. Any combination of these fields may be used for subsequent analysis and use in response and routing. The To Address might reference a special contact center group (for example, support@yourcompany.com) to which certain s will 6

9 always be routed. The combination of the From Address and Mail Priority might be used to provide expedited routing for selected high-value customers. If additional information about the customer is maintained in a database, then the From Address is used for a database lookup (for example, to retrieve a customer number or credit history). Figure 4: Example of Analyze Workflow 7

10 Section 6.2: Qualify Workflow The Qualify Workflow provides the routing logic needed to deliver an to the appropriate agent, after the Analyze Workflow has determined the intent, customer information, and disposition. As the Analyze Workflow accomplishes its processing, routing hints are created and used to match work to an agent or agent queue depending on agent availability and skill level. Figure 5: Example of Qualify Workflow Section 6.3: Outbound Workflow The Outbound Workflow for outgoing s is triggered after the contact center agent has completed their current work on the current transaction and "sends" the . Depending on the activity intended by the agent, the outbound could be a direct response destined for the customer or a request to an external subject matter expert (SME). The Outbound Workflow routes the request, possibly invoking a subsequent review by a quality assurance supervisor or setting the time for an automatic alert for later action by the agent. 8

11 A functional view of the Outbound Workflow steps is provided in Figure 6. The remaining subsections provide more details on the specific activities that take place during each step of the Analyze and Outbound Workflows. Figure 6: Example of Outbound Workflow 9

12 Section 7: Improving Customer Satisfaction Avaya Management comes with a number of capabilities that increase prompt responses and thereby increase customer satisfaction. Section 7.1: Auto Acknowledge An auto-acknowledgement informs the customer that the mail was successfully received and will be processed soon. The message to the sender is informational only and additional processing of the continues after the acknowledgement is sent out. This is in contrast to an auto-response where the answer/response is sent back to the customer with the expectation that the contact is finished. The content of an auto-acknowledgement can be different, depending upon the desire of the contact center. The first option is to send out a standard auto-acknowledgement upon receipt of the , with no or little analysis of the itself. This allows for a timely automated response, but at the expense of some specificity such as reference to intent or to what area the has been forwarded. A second, more intelligent auto-acknowledgment can be provided. A combination of content analysis, keyword search or segmentation is used to determine which specific type of acknowledgment should be sent (e.g. "Thank you for your recent sales inquiry about our new software."). For example, different acknowledgments could be used for "Sales" versus "Services" . These auto responses serve to let customers know that correspondence was received, and set the expectation as to when to expect a response. Section 7.2: Auto or Agent Directed Response With auto response, companies are able to respond to a customer inquiry or request automatically without human intervention. Fully automated responses work best when there is a high confidence level that the intent of the has been correctly identified and the business cost of providing an incorrect or inappropriate response is relatively low. An example is when a request is for information (for example, product features or requirements) rather than a business commitment. If the confidence level is medium to low or the business cost associated with providing the wrong response is high, an agent response is the better option. This decision can be tuned as part of the business rules for this type of . An agent should not be expected to develop a response for every . Each agent has his/her own writing style and responses will vary in content and quality. Once the intent of an is determined, a suggested response(s) will be presented to the agent. The agent always has the option of tailoring it. Results from determining the intent of an are used to create search parameters into the Self-Service Knowledge Base to retrieve suggested responses and response templates. The matched responses are returned along with a confidence score indicating the closeness of the response to the selected topics. Templates are "form letter" responses that automatically answer customer requests. 10

13 Section 7.3: Avaya Routing and Resource Matching Avaya Management provides the capability to use the routing information gathered during analysis to make basic routing decisions. The routing capabilities are implemented within the Qualify workflow. Examples of some of these basic operations might include: Routing/decisions based on a pre-specified mailbox (To). Routing/decisions based on keywords in header or body (From, To, Subject, Body). Blocking of the delivery of junk mail to agents based on patterns in body (This is not the main mechanism for junk mail screening, but is a mechanism to customize for specific business rules). Routing/decisions based on pre-specified senders (To customer lookup). Routing/decisions based on identified topics in the subject and body based on content analysis. Routing/decisions based on identified language of the . Section 7.4: Avaya Business Advocate for Avaya Interaction Center Routing (Available in Release 6.1) Avaya Management capabilities will utilize Avaya Business Advocate algorithms for predictive and skills-based routing capabilities. Advocate is a set of capabilities that provides new methods and added flexibility for selecting an agent for an or an for an agent. Advocate is an optional add-on component to the base Interaction Center system. Using Business Advocate for Interaction Center, the contact center manager defines business goals that specify what kind of service to provide for various customer segments and/or for various types of work ( , voice calls, web chat). It is these business goals that drive the routing and work distribution decisions while providing contact center managers with a way to measure the value that the center brings to the business. As work comes into the system, its characteristics (qualifiers) that will be used as input to Business Advocate for routing are identified. Each connector (channel) has its unique way of identifying work type and storing the relevant information about the contact. For example, the connector may store the From Address, To Address and Subject of the . In addition, the output of content analysis, key word search or other identifying information can be used to further qualify the piece of . Examples of further CA qualification might include language, product and customer type. Section 7.5: Multiple Interactions / Document Matching The processing cycle for an transaction often involves multiple items. s can be exchanged with the sender to get additional information or confirm data. A subject matter expert (SME) can be requested to provide additional information or provide approval to proceed with a transaction. A copy of the actual can be sent to a supervisor for quality assurance purposes. These different s must be tracked and kept together for later processing and historical purposes. The Avaya Management system provides the capability of matching incoming s with previously received s for a particular transaction. The various s are available for review by the agent to assist in processing the customer request. 11

14 Section 7.6: Send Request to Subject Matter Expert To ensure that the customer receives the right answer to their inquiry, agents can engage a Subject Matter Expert (SME), an individual who is capable of assisting the agent in responding to a service request. Several capabilities are provided to support convenient collaboration between the agent and an external SME: Agents are able to send to SMEs for help during the processing of the work item. The SME can be within or outside of the company domain. As part of this capability, an agent has the option to include the original received (text and/or file attachments) plus any annotations. When sending to a SME, information is embedded in the outbound message to support matching a received response from the SME to the original . An agent has access to a SME address book when originating outbound mail, or (at the agent s option) can manually input a TO, CC or BCC address. Avaya Management is able to identify a received as a response to an existing item from either a customer or a SME. The response received back is automatically tracked and tied to the original and routed back to the agent or group of agents that was specified when the SME mail was sent outbound. 2 The agent is able to include one or more responses from the SME when composing an outgoing mail message to the customer. The response to the customer may include text and/or file attachments. Section 8: Intelligent Analysis Avaya Management has the ability to sort and route incoming s as well as analyze incoming s based on the sender information, service levels and message content (through keyword matching and intent). Avaya Management with Content Analyzer can also determine the language of the incoming . Section 8.1: Sender Identification / Information The From (sender s) address can be used to identify the customer from a customer database and to retrieve a customer record with basic information. The retrieved information is displayed on the agent s desktop. Having customer summary information enables an agent to handle a customer s more effectively and efficiently. Avaya Management can search customer information databases that are located on other systems. 2 alerts provide the capability to set a timer to monitor for the timely receipt of an information request from an SME or customer. When configured, the appropriate time interval is set automatically by the Outgoing workflows. This capability allows the agent to meet any special service-level requirements set for the customer or request class. When the timer expires, the agent is alerted automatically and can decide whether to follow-up on the current status of the request or to pursue another contingency. 12

15 Section 8.2: Customer Segmentation The customer record can be used to provide the value of the customer to a company for use in customer segmentation. This allows a company to assign different service levels based on the value of that customer. High value customers can be routed immediately to a particular customer service representative for personalized services. Other customers are routed through normal process steps. Section 8.3: Keyword Matching The customer s intent of an can be determined by searching the subject line and/or body of the for key words that are associated with different topics. Key words can consist of a single word or a phrase. It is important to note that the different tenses of a word are treated as different words. A word of a different tense can often change the meaning and intent of an . When using keyword matching, all variations of a word(s) should be considered. While subject intent can often be determined, the sender does not always imbed the right key words within the subject line. If subject intent cannot be determined, the body of the must be analyzed to determine intent. Therefore, another limitation with keyword searching in a subject line is that it is difficult to determine a sub-topic within a subject. As an example, the subject identified is computer service, but is that service for hardware or software? If hardware, is the hardware a processor, keyboard or monitor? Ultimately, Avaya Management provides both options, keyword matching and Content Analysis, depending on the company s business needs and processing model and preference. Keyword matching is used also to retrieve specific information from a portion of an . is checked against pre-designated customer account numbers (for example, in order to differentiate service levels based on customer value). This information can be used also by the Analyze Workflows to provide additional routing hints to downstream routing workflows. Regular expressions to specify the search text are supported. This allows a pattern with known format (for example, a Social Security Number or Customer Identification Number) to be easily located and used as a key for subsequent routing or database lookups. Keyword matching is most useful in situations where the keywords can be unambiguously identified within the message. This is because the keyword returned may represent one of several possible addresses: the sender s address, an address to be used as a destination for the response, or an unrelated address from an embedded message (for example, within a forwarded piece of ). If the body is well structured (for example, some type of form which has only one field designated for an address), then keyword matching may be appropriate. Section 8.4: Content Analysis Since s often have informal and ambiguous language, content analysis and natural language processing is needed to enable enterprises to effectively and intelligently process and discern value from the information in the . Avaya Management imbeds the Content Analyzer 3 (CA) feature module. CA is an optional component that allows the system to automatically perform content analysis 3 The underlying content analysis engine is based on the Relationship Modeling Engine (RME) licensed from Banter, Inc. 13

16 on incoming . It extends analysis beyond simple keyword matching. Complex natural language processing and statistical analysis algorithms are applied to text of the and derive a likelihood match between that text and a list of possible topics. While keyword searching can determine if a given keyword is contained in a message, the presence of the keyword alone is often insufficient to determine the actual meaning or intent of the message. An example of this is provided in Figure 7 where keywords such as "Lincoln" or "Ford" could have multiple meanings depending on the actual context of the message. Presidents Automobiles Nixon Ford Corvette Lincoln Madison Tacoma Dublin Cities Figure 7: Limitations of Keyword Matching Content Analyzer can analyze text written in languages other than English. This information can be useful when qualifying and routing a piece of in a multi-lingual contact center environment. It can also be used to recognize and react (via specialized routing) to unsupported languages. Supported languages for text classification are English (both U.S. and U.K.), French (both Parisian and Canadian), German, Spanish (both Castilian and Latin American) and Japanese. Section 8.5: Determining Languages A contact center may be servicing an area where multiple languages are prevalent. If the routing of a call to particular agent skill group is dependent upon language, the company may want to route inbound s based on language. Many companies have difficulty in accomplishing this. 4 With the Avaya solution, the body of the is passed to the Content Analyzer server to determine the dominant language of the . The accuracy of the identification depends on the size of the message as well as the number of different languages that it contains. 4 The underlying content analysis engine is based on the Relationship Modeling Engine (RME) licensed from Banter, Inc. 14

17 Avaya Management with Content Analyzer can identify the dominant language of the for any of the following languages: English (U.S. and U.K.), German, French (Parisian and Canadian), Spanish (Castilian and Latin American), Portuguese, Italian, Japanese, Dutch, Danish, Norwegian, Swedish, Korean, and Chinese (Simplified). Section 9: Management Reporting and Analysis Avaya provides operational reporting support for management of contact center activity to drive revenue and improve operational costs, improve productivity, and more importantly, increase customer intimacy, retention and satisfaction. The integrated customer interaction repository and suite of standard predefined reports provide detail and summary views across multiple sites, multiple ACD vendors and multiple communication channels (Voice, VoIP, , Web Chat and Web Self-Service). The Avaya reporting package provides a rich and consistent set of real-time metrics across all channels thereby substantially reducing the effort to manage multi-media contact centers. Ten -specific reports are included with Avaya Management. Section 9.1: Specific Reports Detailed Agent Response Time Range Report Detailed Agent Group Statistics Report Detailed Agent Interactions by Channel Detailed Reports by Channel and Trends Monthly Traffic Trends Report Traffic by Hour Report Account Summary Report Section 9.2: Specific Drill-Through Reports Detailed Agent Response Time Range Report Detailed Agent by Queues Report Detailed Agent Response by Date Range Report Mail Account Summary Report The 3-D graphical, web-based monitoring of real time and historical contact center performance allows for efficient management of agent activities and verification that the system is achieving service level goals. The ability to create and maintain customized reports aids in the assessment of customer service and marketing activities unique to each business. The predefined data collectors and standard reports are automatically combined with full multi-channel data for complete cradle-to-grave contact analyses. 15

18 Section 10: Conclusion By using the Avaya advanced automation technology, companies can successfully cut costs and improve efficiency with measurable agent productivity gains and intelligently route s throughout the contact center. Companies can also experience enhanced customer satisfaction by the timeliness, quality and accuracy of responses. As a result, companies can deliver excellent customer service and increase revenue opportunities! Appendix A: System Requirements Agent Desktop OS Windows NT/2000/ XP Servers OS Windows 2000 Solaris 8 Databases Microsoft SQLServer 2000 Oracle

19 About Avaya Avaya enables businesses to achieve superior results by designing, building and managing their communications networks. More than one million businesses worldwide, including 90 percent of the FORTUNE 500, rely on Avaya solutions and services to enhance value, improve productivity and gain competitive advantage. Focused on enterprises large to small, Avaya is a world leader in secure and reliable IP telephony systems, communications software applications and full life-cycle services. Driving the convergence of voice and data communications with business applications and distinguished by comprehensive worldwide services Avaya helps customers leverage existing and new networks to unlock value and enhance business performance. reach IP Telephony Contact Centers Unified Communication Services 2003 Avaya Inc. All Rights Reserved. Avaya and the Avaya Logo are trademarks of Avaya Inc. and may be registered in certain jurisdictions. All trademarks identified by the, SM or TM are registered trademarks, service marks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners. Printed in the U.S.A. 04/03 EF-LB2082 avaya.com