This article presents a sample use case for how to work with Journey Management . The use case shows a journey from which analysts can understand how many customers can perform self-service within a specific flow.

Assume that you are a contact center analyst who assesses the effectiveness of bots that are designed for social media applications. Your goal is to compare the number of customers who achieve resolution through bots versus human agents (ACD). To accomplish this task, use Journey Analyzer functionalities.

1. Log in to your Genesys Cloud account and click the Journey Management menu. The Journey Management screen opens.
2. Create a new journey.
3. To enter Edit mode and modify a journey, click Edit.
4. Journey events align to the types of actions that are triggered throughout an interaction. The Customer Start event is triggered when a customer engages with a channel. Drag a Customer Start event and filter it for the social channel you want to measure.
5. Open the event, click the filter icon and select the following:
   1. MediaType - Message
   2. MessageType - The social channels you want to measure
   3. Add a descriptive name on the canvas to this event such as, Started a social engagement on Twitter.
      
6. Next, because you want to know how many customers went to Bot Start after they started their social engagement, drag and drop Bot Start to the canvas and then let it connect to Customer Start.
   Tip: Use the Tab key on the keyboard to move navigate through the event list and use the menu.
   
   
   1. To narrow down the event to the bot name, include the bot name as an event attribute filter.
      
      Tip: You can find the bot name in Architect. Journey Management supports native or third-party bot events, but native bots provide more detailed data for the journey.
7. Now, to examine completed bot sessions, drag Bot End to the canvas and then let it connect to Bot Start.
   1. Because you are interested in the same bot that you examined in Step 6, include the bot's identifier as an event attribute filter at this event.
      
      Tip: If you use a native Genesys bot, then to narrow your analysis to an intent and other interaction attributes that may be relevant, add Bot Turn between start and end.
   2. To see completed bot sessions, include the botsessionOutcome filter and then select the complete attribute.
      
   3. Click Apply filter.
   4. As in this event, you examine completed bot sessions and not the sessions that went to ACD (automatic call distribution), add a BotResult filter in the Exclude section with TransfertoACD as the value.
      
      
   5. Click Apply filter.
8. Next, examine sessions that went to ACD. Drag the ACD Start event to the canvas. Let it connect to Bot Start, so that it is parallel to Bot End.
   
9. In this event, select queueID as Attribute, and then add a filter for the Payment Queue. 
    
   
10. Click Save.

Calculate and edit the sample journey

1. Click Calculate to generate journeys. A notification about the calculation count appears.
2. To continue, click Proceed. The calculation takes a few minutes to run. The loading time depends on the volume of data to process, so larger datasets take more time to calculate. To see the results, refresh the page.
3. After the calculation finishes, you want to know the number of resolved calls by agents. To edit the journey, click Edit.
4. Drag the Agent Start event, and let it connect to the ACD Start event.
   1. Add a filter for the Payment Queue. The payment queue has two wrap-up codes: Success and Failure.
      • Track agent resolution with a Success wrap-up code. From the Voice event group, drag a Wrap Up event to the canvas and let it connect with the Agent Start event. Select the wrapupCode attribute and include the identifier of the Success wrap-up code as a filter.
        
        Note: You can get the list of wrap-up code IDs used in your environment with the Wrap-up API endpoint through the API Explorer, which is available on the Genesys Cloud Developer site.
      • To indicate that it stands for the Success wrap-up code, add a descriptive title to your After Call Event such as 'Successful Resolution'.
5. Click Save.
6. To update the journey, click Calculate. To see the updated counts refresh the page.

See funnel analysis in the sample journey

With the help of funnel analysis, you can understand how your customers move through the journey to achieve their goals and then determine the success rates of their individual journey paths.

A journey must have calculations for funnel analysis.

1. Open the existing journey that you want to analyze. 
2. In Edit mode, click Show conversion. Journey Analyzer calculates the conversion metrics.
3. To examine the attributed metrics, click the + icon again in the upper right corner of the event. To hide the conversion metrics of an event, click the - icon in the upper right corner.
4. To determine the journey that your customers followed, examine the Customers, Conversion rate, Dropped out and Moved forward metrics at the respective events.
   
   Example: The funnel analysis in the Bot Start event shows that 650 customers dropped out from the journey at this point, and 1052 customers Moved forward to Bot end, so Bot end has a conversion rate of 61.7%. This means that 61.7% of your customers proceeded to reach the Bot end session.