Difference between revisions of "Cost Improvement Programs"
| Line 25: | Line 25: | ||
All observations and studies to this point suggest that there are at least 8 major contributing factors driving an increased contact rate. A critical observation; higher contact rate within the markets served by the Miramar call center is being driven by multiple causes. Contact rate solutions will require multiple initiatives, some of which will require significant change and investment in the operational environment. The 8 major call driver factors identified in this report include: | All observations and studies to this point suggest that there are at least 8 major contributing factors driving an increased contact rate. A critical observation; higher contact rate within the markets served by the Miramar call center is being driven by multiple causes. Contact rate solutions will require multiple initiatives, some of which will require significant change and investment in the operational environment. The 8 major call driver factors identified in this report include: | ||
| − | [[ | + | [[file:improvement-areas.jpg]] |
| Line 31: | Line 31: | ||
Finding: Avaya Structure Suspect – Analysis of the Avaya call routing structure, vectors, VDNs and skill design indicate a significant opportunity to improve call routing, and potentially directly lower contact rate. 2000+ VDNs feed over 100 active skills which lack a uniform method for accounting for call volume. Currently, the call center business is managed by altering VDNs and Vectors in a live environment, which introduces the potential for creating errors in call routing. An example of such an error was logged on March 3rd, when a return path VDN & Vector from an outsourcer, designed to hand calls back into the call center, was built with a vector that was set as “high” priority. This caused calls to flow freely from the outsourced vendor, but because of the large inbound volume, it at the same time created a call blocking situation: | Finding: Avaya Structure Suspect – Analysis of the Avaya call routing structure, vectors, VDNs and skill design indicate a significant opportunity to improve call routing, and potentially directly lower contact rate. 2000+ VDNs feed over 100 active skills which lack a uniform method for accounting for call volume. Currently, the call center business is managed by altering VDNs and Vectors in a live environment, which introduces the potential for creating errors in call routing. An example of such an error was logged on March 3rd, when a return path VDN & Vector from an outsourcer, designed to hand calls back into the call center, was built with a vector that was set as “high” priority. This caused calls to flow freely from the outsourced vendor, but because of the large inbound volume, it at the same time created a call blocking situation: | ||
| + | [[file:improvement-avaya.jpg]] | ||
| + | |||
| + | By making changes within the routing structure, the opportunity for creating such situations is greatly increased. Additionally, opportunities exist for improving efficiencies by consolidating and standardizing call buckets and skills. Lack of standardized call types leads to changes made in routing, which can potentially bucket calls differently from one month to the next, providing challenges to WFM and forecasting. The largest portion of calls is currently classified as “General”, which requires mapping into a skill which more specifically defines the nature of the call type. While some transfer skills were recently built, transferred calls do not appear to be captured consistently by designating skills specifically for transfers, leading to exposure for increased contact rate from double counting calls. Steps should be taken to standardize and clean all existing routing within the Avaya; calculating an accurate contact rate will be the primary metric used to measure the impact made from other project recommendations. | ||
| + | Solution: Avaya Standardization – A standardization project has been initiated, with the first operational review workshop held in Miramar March 18th- 20th. This workshop established the foundation for the redesign and standardization of call routing and skills, which will be implemented within approximately 4-6 weeks. See the timeline (Appendix D) for additional details associated with the Avaya project. Phase I project. | ||
==SL% Challenge, Forecasting and Staffing Models== | ==SL% Challenge, Forecasting and Staffing Models== | ||
Revision as of 10:55, 16 July 2016
Contents
Cost Improvement Programs
Workforce Management organizations often are leveraged for establishing baseline metrics within a contact center and validating whether identified cost or metric improvement initiatives have yielded improvements in contact center operations. While 1:1 correlations are not always feasible, changes that are implemented and properly base-lined can be examined by a WFM organization to evaluate whether volumes, handle-time, shrinkage, or occupancy have changed as the result of that activity.
Below is a sample real-life contact rate reduction plan. In this plan, WFM would support validations of various segments.
Executive Summary
South Florida Region is currently experiencing a customer contact rate outside of normal operational goals and expectations. In order to determine the primary drivers contributing to the high contact rate, the Southern Division Customer Care and Technical Operations support team has launched a project to analyze all potential contributing factors. The project began with 3 weeks spent on-site in Florida, reviewing daily operations in both the call center and the field. This report outlines the initial observations, and recommends initiating a series of projects specifically designed to reduce contact rate within the call center.
Methodology
The methodology used to examine contact rate drivers approaches the business from multiple vantage points. Live and historical data collection, live customer care interactions and direct feedback from front-line representatives and management contributed to the core findings included in this report. The activities conducted to derive the initial findings included:
• Call Monitoring Sessions • Workforce Management Interviews • Supervisor Focus Group • CAE Focus Group • Resolve Ticket Analysis • Traffic Analysis (Live and Historical) • Analysis of Avaya VDN and Skill Structure • Outbound Repeat Caller Program (National Team)
No Single Cause
All observations and studies to this point suggest that there are at least 8 major contributing factors driving an increased contact rate. A critical observation; higher contact rate within the markets served by the Miramar call center is being driven by multiple causes. Contact rate solutions will require multiple initiatives, some of which will require significant change and investment in the operational environment. The 8 major call driver factors identified in this report include:
Avaya Call Routing & Skills
Finding: Avaya Structure Suspect – Analysis of the Avaya call routing structure, vectors, VDNs and skill design indicate a significant opportunity to improve call routing, and potentially directly lower contact rate. 2000+ VDNs feed over 100 active skills which lack a uniform method for accounting for call volume. Currently, the call center business is managed by altering VDNs and Vectors in a live environment, which introduces the potential for creating errors in call routing. An example of such an error was logged on March 3rd, when a return path VDN & Vector from an outsourcer, designed to hand calls back into the call center, was built with a vector that was set as “high” priority. This caused calls to flow freely from the outsourced vendor, but because of the large inbound volume, it at the same time created a call blocking situation:
By making changes within the routing structure, the opportunity for creating such situations is greatly increased. Additionally, opportunities exist for improving efficiencies by consolidating and standardizing call buckets and skills. Lack of standardized call types leads to changes made in routing, which can potentially bucket calls differently from one month to the next, providing challenges to WFM and forecasting. The largest portion of calls is currently classified as “General”, which requires mapping into a skill which more specifically defines the nature of the call type. While some transfer skills were recently built, transferred calls do not appear to be captured consistently by designating skills specifically for transfers, leading to exposure for increased contact rate from double counting calls. Steps should be taken to standardize and clean all existing routing within the Avaya; calculating an accurate contact rate will be the primary metric used to measure the impact made from other project recommendations. Solution: Avaya Standardization – A standardization project has been initiated, with the first operational review workshop held in Miramar March 18th- 20th. This workshop established the foundation for the redesign and standardization of call routing and skills, which will be implemented within approximately 4-6 weeks. See the timeline (Appendix D) for additional details associated with the Avaya project. Phase I project.
