The Contact Driver Gap Analysis aims to ensure comprehensive coverage and effectiveness of the configured contact drivers by addressing missing drivers, incorporating new ones as needed, and refining existing guidelines based on insights from contact center interactions. This involves several key aspects:

1. Identification of Missing Contact Drivers:

This entails identifying any contact drivers that are not currently configured but are necessary for analyzing customer cases effectively. These missing contact drivers may be crucial for understanding and categorizing incoming customer inquiries.

2. Relevance of Contact Drivers:

Additionally, the analysis includes identifying new contact drivers that were not initially considered relevant during the configuration of the contact driver model. However, with the emergence of new cases, these contact drivers have become important and must be integrated into the system for accurate case analysis.

3. Evaluation of Existing Contact Driver Guidelines:

The analysis also assesses any gaps in the guidelines of the existing contact drivers. This evaluation is based on insights gathered from contact center conversations. If these conversations reveal the need for updates to the guidelines to address overlaps or address any missing aspects, adjustments can be made accordingly.

Generating Contact Driver Insights

The generation of Contact Driver Insights involves a multi-step process aimed at identifying areas for the creation of new contact drivers or updates to existing ones based on customer cases. Below is a detailed explanation of each step:

Step 1: Perform Case Analysis

• Granular analysis is conducted for individual customer cases to understand the specific issues they encountered.

• The focus is on understanding the most granular contact driver of the conversation, irrespective of the existing list.

Step 2: Validate Existing Contact Drivers

• In this step, the identified contact driver is verified against the current list of configured contact drivers at the most granular level.

• If the contact driver exists:

  • The need for a guideline change is determined, and the guideline change is suggested if necessary.

• If the indentified contact driver is new:

  • Its parent contact driver is determined. For example, if L3 is missing, its parent L2 is identified.

• The presence of the parent L2 in the current list of contact drivers is checked.

  • If it is present, the suggestion is made to create the new contact driver within this L2, along with the guideline it should follow.

  • If it's not present, the process is repeated to determine its parent contact driver (L1).

• The presence of the new parent contact driver (L1) in the configured list of contact drivers is checked.

  • If it is present, the suggestion is made to create the new identified contact driver and L2 within this L1, along with the guidelines it should follow.

  • If it's not present, the suggestion is made to create L1 as well. This process continues until the top level is reached.

​

This comprehensive approach ensures that all customer cases are thoroughly analyzed to identify the need for new contact drivers or updates to existing ones, ultimately improving the effectiveness of the contact driver model.