---
title: 4.2 Use case: Call center deflection insights
slug: bootcamp-anzbank-2024/42-use-case-call-center-deflection-insights
docTags: 
createdAt: 2023-12-15T15:34:53.463Z
---

# Exercise: 

**Use case**: Call center deflection - I need to understand which digital experiences can be improved to reduce the calls to our call center. e.g. Understand what pages drove the calls to the call center. 

For this exercise, we'll analyse the top call reasons to the call center and use the flow visualtion to understand what were they doing on other channels before calling the call center. 

## 4.2.1 Understand the top call reasons to the call center

1. Add a **new blank panel** to our dashboard by clicking the **+ icon** at the bottom of our dashboard.

![](https://api.archbee.com/api/optimize/1Jp0iolWv35Z_mkI7oUiT/Gp4dUEOepuvL9lRvmjRro_image.png)

2\. Ensure that the **`CID Release 5 (Nov15 - Jan 15, 2024)`** is selected in the Data View selector and the reporting date range is **Nov 15 2023 - Jan 15, 2024. **Then select the **Flow **visualisation from the options presented. 

![](https://api.archbee.com/api/optimize/1Jp0iolWv35Z_mkI7oUiT/Hpc9pKp3PVKhkxmHRrUXM_image.png)

**Notes on Dimension configuration:**

- Dropping a dimension as the Entry point will show the top first values seen in that dimension either at a Session or Person level
- Dropping a dimension as the Exit point will show the top last values seen for a dimension at a Session or Person level
- Dropping a dimension or a dimensional element in the middle will show you how often that element is the entry or exit, as well as the top elements a person saw prior or after from a pathing perspective. This can also be configured at the Session or Person level.

3\. Drag the **`FSI_RetailBank_CallReason`** dimension and drop it in the Exit drop zone. Then click **Build.**

![](https://api.archbee.com/api/optimize/1Jp0iolWv35Z_mkI7oUiT/1aG3byFH1Gi-LJ4ADQN5b_image.png)

This shows us the top Call Reasons for customer calls into the call center.

![](https://api.archbee.com/api/optimize/1Jp0iolWv35Z_mkI7oUiT/CVotTvi8vwjznZl_5-q1m_image.png)

## 4.2.2 Understand which pages drove the calls 

One very powerful capability the Flow visualization supports is the ability to mix and match the dimensions being used.  

1. Drag the **`FSI_Retail_Bank_Pages`**dimension and drop it to replace the left most column of the flow visualisation. The result is a view into the top pages customers interact with prior to a call, broken out by call type:

![](https://api.archbee.com/api/optimize/1Jp0iolWv35Z_mkI7oUiT/c14l9fmI17M63Bbov35V8_image.png)

2\. Drill into any of the pages to see what customers interact with prior to that on their path to a call. We can see many customers are visiting the self help forums and still not finding an answer before calling in to the call center with an Application Issue. There could be value in running some optimisation tests on those pages.   

![](https://api.archbee.com/api/optimize/1Jp0iolWv35Z_mkI7oUiT/p4OzwbtMinAsf6cwKH9Yq_image.png)

6\. Finally hit **Ctrl/Command S** to save your project.

![](https://api.archbee.com/api/optimize/1Jp0iolWv35Z_mkI7oUiT/vHIB9YyLfx_tXp26Zg8tZ_image.png)

This can be very powerful in understanding customer journeys across channels. Other use cases could be to analyse how are customers moving across different channels or post a campaign click. 

# Exercise complete checklist 

- [ ] Able to view the top call reasons to the call center
- [ ] Able to find the top pages leading to the calls. (This insight can then be fed back to the digital team for any optimisation)