Optimize customer journeys proactively

Get a clear view of how customers progress through your flow directly within Architect.

With a heat map representation, you can quickly identify areas with high customer engagement, as darker colors indicate denser interactions.

Hover over the highlighted Architect actions or flow components to display the exact number of times customers interacted with each of these actions or components.

Analyze the heat map and note where the darkest interaction colors appear to pinpoint the most frequently used Architect actions and other flow components within the flow. If certain actions or components are heavily interacted with, simplify or refine these components to ensure a smoother experience, and reduce any potential friction at key points of customer interaction. High interaction counts can also indicate that customers need extra guidance or support. Add clearer instructions to address customer needs proactively.

Use the heat map to spot areas with unexpectedly high interaction counts, which could indicate bottlenecks where customers struggle or require multiple attempts. For instance, if an Architect action or menu has significantly higher interaction counts than surrounding actions, it could suggest confusion or difficulty completing that step. Investigate ways to simplify or clarify this Architect action to improve flow efficiency.

Identify flow components with low interaction counts to assess whether customers overlook these components or the components are ineffective in guiding customers. Make these components more prominent or evaluate whether they are necessary to refine the journey and ensure that each step contributes value and supports customer progression.

With the ability to see exact interaction counts on hover, you can prioritize optimizations on specific flow components that receive the highest customer engagement. For example, if an initial step shows a high interaction count but subsequent steps drop off, you can refine this first step to ensure it better prepares customers for the next stages. You also help customers to maintain engagement throughout the flow.

The heat map data allows you to discern trends in customer movement. If customers repeatedly engage with specific Architect flow components in certain ways (for example, they repeatedly return to a particular step), redesign this part of the flow and add more guidance to support a smoother journey.

Track how interaction frequencies change over time to measure the impact of optimizations. If a particular action’s interaction count drops significantly after refinement, it can indicate that the improvement successfully removed a barrier, guiding customers more effectively through the flow.

1. From the Architect home page, click or hover over the Flows menu and select the desired flow type.
2. Click the flow that you want to analyze.
3. Use the Flow Insights toggle to display the interaction heat map for the flow.
   Note: There must be interaction data from the past seven days for the heat map to appear.
4.  Look for flow components with high frequency (interaction count) levels and check if customers are dropping off in subsequent steps. In the following example, customers make it to the Digital Menu action in a digital bot flow, but fail to progress further:
5. Now, examine the Digital Menu action to review and determine why progress is stalling and identify any necessary actions to remove the fricton points.

Get a dynamic visual representation of how users navigate through and engage with various flow segments in their customer journey.

Explore granular and high-level insights into customer behavior by drilling down into steps that customers take throughout their journey or zooming out to view broader patterns. Reveal key pathways within an Architect flow that represents a segment of the customer’s experience.

Select from various flow outcomes to generate distinct visualizations to reveal the paths customers took to reach each outcome. Outcomes include scenarios such as path abandonment, escalation to an agent, disconnection, or intent recognition failure. These paths illustrate both successful or happy routes and failure routes within the customer journey, and provide insights into a range of customer experiences.

View all flow milestones that customers reach on each journey path. Hover over specific milestones or outcomes to see the frequency counts of customer interactions. Get quick access to data on how often customers interact with particular steps to help you assess flow performance and customer engagement along the journey.

Analyze visualizations of customer paths that lead to the abandonment outcome to identify specific milestones where a high percentage of customers drop off. If, for example, there is a high frequency of abandonments after a specific milestone, you can investigate potential friction points, such as unclear instructions, lengthy processes, or technical issues, and make adjustments to improve customer retention through this segment of the journey.

Analyze paths that end in an escalation to an agent to determine at what stages and why customers felt the need for live assistance. With these insights, you can identify opportunities to enhance self-service options, for example, by adding more guidance at specific milestones, improving automated responses, or refining knowledge articles. Such adjustments can reduce escalations and ensure that more customers achieve successful outcomes without additional support.

Focus on the happy paths where customers reach successful outcomes without any issue to identify efficient pathways. Understand the milestones that are common to these paths to simplify the customer journeys by removing or consolidating some steps to make it easier for more customers to reach successful outcomes quickly and with less effort.

Review paths that end in a disconnect or recognition failure including each step that leads up to these outcomes to detect and resolve root causes, such as limitations in recognizing customer intent or confusing interface elements. Proactively address these issues to reduce the failure rate to improve customer satisfaction and completion rates.

Use the frequency metrics at each milestone to identify high-traffic areas within the flow and prioritize optimizations for these points. Focus on these key milestones to ensure that changes impact the greatest number of customers, which can contribute to smoother, faster journeys and higher satisfaction scores across the board.

Zoom out to view broader patterns of customer movement through the Architect flow to detect common journey patterns, such as sequences of milestones reached by specific customer segments. You can use such patterns to inform personalized experiences, such as tailored prompts, shortcut options, or predictive guidance that aligns with likely next steps, and create a more intuitive and engaging customer journey.

With the frequency metrics that Architect shows on hovering over milestones or outcomes, you can make informed, data-driven decisions about where to invest optimization efforts. For instance, if a particular milestone sees heavy interaction before a drop-off, you could allocate resources to improve that specific point, and drive a targeted approach to customer journey optimization.

Assume that you are a contact center admin or analyst who wants to assess the effectiveness of a bot. Your goal is to compare the number of customers who achieve resolution through the bot versus a human agent (ACD). To accomplish this task, use Journey Flows functionalities.

1. From the Architect home page, click or hover over the Flows menu and select the desired flow type.
2. Click the flow that you want to analyze.
3. Click Journey Flows in the Insights and Optimizations menu. The Journey Flows visualization opens. The visualization shows the distribution of customers along the various flow milestones and outcomes as well as the various flow exit reasons. The visualization also demonstrates how the customer journey progressed at each flow stage:

   Montre moi

   
4. Next, because you want to know how many customers went to the Payment Initialized milestone, hover over the milestone to display the frequency count:
   
5. Now, to examine why 11 per cent of customers who completed the Payment Initialized milestone asked to speak to a human agent and seven per cent of customers disconnected the call, use Flow Insights to generate a heatmap of the Digital Menu options in your Initial Settings menu or use Replay Mode to check execution instances of your flow.
6. Next, examine sessions that were Abandoned.
   

 

Replay past executions of your Architect flows to pinpoint low engagement and conversion issues based on insights from Flow Insights and Journey Flows.

Test flow logic adjustments to boost engagement with key components of your Architect flow, reduce drop-offs for key flow milestones, and increase the number of customers who reach desired flow outcomes.

After you identify a specific flow component with low customer engagement in Flow Insights, use Replay Mode to examine how customers interact with that flow component. Replay the steps that customers take to identify potential issues, such as confusing wording, slow response times, or missing information, that could be causing customers to disengage. Make targeted adjustments to boost engagement rates with the flow component.

If Journey Flows shows a high drop-off rate at a specific flow milestone, replay interactions that lead to that flow milestone to see where customers are dropping off and why. For example, if customers are exiting after a specific menu choice or step, Replay Mode can reveal issues like unclear options or unmet expectations. Adjust the milestone to minimize drop-offs and retain customers in the journey.

After you change the Architect flow’s logic, for example, you simplify steps or clarify messaging, use Replay Mode to observe if these modifications positively impact customer behavior. Compare new execution instances with previous execution instances and then confirm whether engagement rates have also improved in Flow Insights and if Journey Flows shows fewer drop-offs and more customers reaching key outcomes.

For flow components that lead to successful outcomes, replay the customer interactions to understand better why these flow components work well. This insight can guide optimizations for other parts of the flow, and create more success paths that drive customers to desired outcomes more reliably.

After you make improvements to the Architect flow’s logic to reduce drop-offs or increase milestone completion, replay both pre- and post-adjustment interactions. Such comparison allows you to verify if the adjustments led to a more intuitive flow. Verify the increased engagement in Flow Insights and the improved milestone progression in Journey Flows.

For flows with multiple pathways (such as different menu options or self-service routes), use Replay Mode to track how customers navigate these choices. If certain paths show significantly lower engagement or higher drop-offs, pinpoint where customers encounter issues and make modifications to balance path effectiveness across the flow.

If execution instances reveal frequent escalations to agents at a particular point of an Architect flow, analyze these moments to identify gaps in the self-service flow that could be causing customer frustration. Add prompts, clarify options, or improve flow responses to create a smoother self-service experience that reduces the need for agent intervention and improves journey health.

1. From the Architect home page, click or hover over the Flows menu and select a flow type for which historical execution data is available.
2. Open the flow that you previously executed to debug and troubleshoot.
3. Cliquez sur Historique des exécutions. La boîte de dialogue Historique de l'exécution du flux s'ouvre.
4. Sous Results, Architect répertorie les instances d'exécution précédentes du flux que vous avez ouvert et fournit le nom, la version, le type de flux ainsi que les dates de début et de fin des instances de flux.
5. Cliquez sur une instance de flux pour ouvrir l'instance en mode lecture. Pour plus d'informations, voir Utiliser le mode de relecture pour dépanner un flux d'architecture.

6. Use the replay controls to step through the flow to replay the sequence of actions that lead to the specific flow component that you want to analyze. 
7. If the required level of execution data is available, review communication exchanges and inspect variable values as well to pinpoint the issue with the flow component.

In the following digital bot flow example, customers enter their order number to check the status of their order, but the bot fails to recognize the number.

1. The flow designer used an Ask for Slot action to verify the order number and used a slot of the type builtin:any to store the customer’s input.
2. After the bot receives the input, the flow moves on to a Decision action that uses the expression If(FindFirst(Flow.OrderNumbersDatabase, ToJSON(Task.CheckNumber))==-1, false, true) to determine whether the array of existing order numbers stored in the Flow.OrderNumbersDatabase variable contains the order number the customer entered (Task.CheckThisNumber).

Flow Insight’s heat map analysis shows that the Decision action always takes the unhappy path:

Architect’s Replay mode provides the key to understanding why this happens. The bot uses a pattern in the format ###-### to display the order number for customers, where each # represents a digit (0–9) and - is a dash separator. The grouped format is a familiar pattern for customers that reduces the likelihood of errors compared to a long string of digits, and makes it easier to read and remember the number.

The recognition issue occurs because the bot provides the order number in the###-### format, but the bot expects a string of digits without dashes as user input (see the order numbers in the Flow.OrderNumbersDatabase variable). This mismatch in the flow design leads to recognition failure.

                                         

Replay mode revealed that the bot must handle dashes in customer input. To address the recognition issue, use a regex slot type with the pattern ^\d{6}$|^\d{3}-\d{3}$ to validate the input format and remove any dashes before you check the order number against the order database.

Get a customizable view of the entire end-to-end customer journey across all Genesys Cloud channels to help you understand customer interactions from initial contact to resolution.

Extend your analysis of customer journeys beyond single-channel Architect flows, with up to 365 days of data available to track customer interactions across multiple channels and visualize long-term engagement patterns.

View and assess specific journeys, such as customer transitions from bot interactions to agent support, across multiple channels, to understand customer needs and improve journey outcomes.

Filter for key events, such as repeat calls within the past 24 hours, or add channels like SMS to the journey canvas, enabling a tailored view of the customer experience to drive better engagement.

Visualize journey performance trends over time with charts and perform quick comparisons across time periods to identify shifts in metrics, such as self-service rates or escalations, for proactive issue resolution.

Analyze customer progression across journey stages to pinpoint high-attrition points to identify and reduce friction between channels for a smoother, more effective customer experience.

Visualize journeys across multiple channels to track customer interactions that span different touchpoints. For example, interactions that start with web messaging and move to a call. If customers frequently switch channels mid-journey, it could indicate that certain channels are failing to meet their needs. You can then focus on enhancing the initial channel’s functionality to reduce unnecessary channel-switching, which reduces customer effort and improves satisfaction.

Examine customer journeys that start with a bot in a web messaging window and transition to an agent to identify points where customers experience gaps or delays in service. For example, if customers frequently contact an agent after struggling with the bot, you could refine the bot’s capabilities or adjust the transfer process to ensure a smoother transition.

Explore how often customers move from a self-servicing interaction to an agent across different channels, such as from a web messaging interaction to a voice call. Visualize these transfers to identify if certain interactions commonly lead to escalations, suggesting areas where the customer experience might need improvements to enable more effective self-service. You can also use this analysis to make sure you transfer customers more smoothly and with the relevant context already captured to reduce the need for customers to repeat information or agents to repeat customer calls.

You can evaluate the success rates of self-service interactions across various channels, such as digital bots across various messaging channels. By comparing the journey paths of customers who self-serviced successfully against those who required agent intervention, you can identify which self-service flows are most effective on each channel. For example, if SMS has a lower self-service completion rate than web messaging, you might suggest enhancements to the SMS flow, provide clearer prompts, or offer more resources for common issues.

Examine which channels customers use at different points in their journey to identify trends that suggest customer preferences. For example, if customers tend to start with IVR but switch to messaging for follow-up, consider proactive messaging options after IVR interactions to better align with customer behavior and preferences to improve the journey experience.

Visualize trends in journey performance over time with bar, line, or column charts. Compare metrics across time periods to identify changes in journey effectiveness, such as a drop in self-service rates or an increase in agent escalations. Monitor these trends to detect and address emerging issues proactively and ensure that the journey remains efficient and effective.

Use funnel analysis to assess customer progression through various stages of their journey across channels to identify high-attrition points. For example, if many customers engage with an IVR system but fail to progress to a messaging channel for self-service, investigate potential friction points in the transition. Improve the transition between channels to maintain engagement and support successful journey progression.

Adding multiple channels like SMS or email to the journey canvas to evaluate how these channels fit within the larger customer journey. If certain channels show low usage or effectiveness, consider ways to integrate or promote these options better to create a more comprehensive and responsive multichannel experience for customers.

Supposez que vous êtes un analyste de centre de contact qui évalue l'efficacité des bots conçus pour les applications de médias sociaux. Votre objectif est de comparer le nombre de clients qui parviennent à une résolution grâce à des bots par rapport à des agents humains (ACD). Pour accomplir cette tâche, utilisez les fonctionnalités du Journey Analyzer.

1. Connectez-vous à votre compte Genesys Cloud et cliquez sur le menu Journey Management . L'écran Journey Management s'ouvre.
2. Créer un nouveau voyage.
3. Pour entrer dans le mode Edit et modifier un trajet, cliquez sur Edit.
4. Pour créer votre premier événement dans le parcours, développez le groupe d'événements Social & App Messaging, puis sélectionnez et faites glisser Web Message Start sur le canevas.
5. Ensuite, parce que vous voulez savoir combien de clients sont allés sur Bot Start après Web Message, glissez et déposez Bot Start sur le canevas et laissez-le se connecter à Web Message Start.
   1. Pour limiter l'événement au nom du robot, incluez le nom du robot dans le filtre de l'attribut de l'événement .
      
      Conseil: Vous pouvez trouver le nom du bot dans Architect. La gestion des parcours prend en charge les événements des robots natifs ou tiers, mais les robots natifs fournissent des données plus détaillées sur le parcours.
6. Maintenant, pour examiner les sessions de bot terminées, faites glisser Bot End sur le canevas et laissez-le se connecter à Bot Start.
   1. Because you are interested in the same bot that you examined in Step 5, include the bot's identifier as an event attribute filter at this event.
      
      Conseil: Si vous utilisez un robot Genesys natif, pour limiter votre analyse à une intention et à d'autres attributs d'interaction susceptibles d'être pertinents, ajoutez Bot Turn entre le début et la fin.
   2. Pour voir les sessions de robots terminées, incluez le filtre botsessionOutcome et sélectionnez ensuite l'attribut complete.
      
   3. Cliquez sur Appliquer le filtre.
   4. Comme dans cet événement, vous examinez les sessions de robots terminées et non les sessions qui sont allées à l'ACD (distribution automatique des appels), ajoutez un filtre BotResult dans la section Exclude avec TransfertoACD comme valeur.
      
      
   5. Cliquez sur Appliquer le filtre.
7. Examinez ensuite les sessions qui ont été envoyées à l'ACD. Ouvrez le groupe d'événements Voice et faites glisser l'événementhe ACD Start sur le canevas. Laissez-le se connecter à Bot Start, de manière à ce qu'il soit parallèle à Bot End.
   
   
8. Dans cet événement, sélectionnez queueID comme Attribut, puis ajoutez un filtre pour Payment Queue. 
    
   
9. Cliquez sur Sauvegarder. 

Calculer et modifier le trajet de l'échantillon

1. Cliquez sur Calculer pour générer des trajets. Une notification concernant le nombre de calculs s'affiche.
2. Pour continuer, cliquez sur Procédez. Le calcul prend quelques minutes. Le temps de chargement dépend du volume de données à traiter, de sorte que les ensembles de données plus importants prennent plus de temps à calculer. Pour voir les résultats, rafraîchissez la page.
3. Une fois le calcul terminé, vous souhaitez connaître le nombre d'appels résolus par les agents. Pour modifier le trajet, cliquez sur Edit.
4. Faites glisser l'événement Agent Start et laissez-le se connecter à l'événement ACD Start.
   1. Ajouter un filtre pour la file d'attente de paiement . La file d'attente des paiements comporte deux codes de récapitulation : Succès et Échec.
      • Suivre la résolution de l'agent avec un code de synthèse de la réussite. Dans le groupe d'événements Voice, faites glisser un événement Wrap Up sur le canevas et laissez-le se connecter à l'événement Agent Start . Sélectionnez l'attribut wrapupCode et incluez l'identifiant du code wrap-up Success comme filtre.
        
        Note: Yous pouvez obtenir la liste des ID de code wrap-up utilisés dans votre environnement avec le point de terminaison Wrap-up API via API Explorer, qui est disponible sur le site Genesys Cloud Developer.
      • Pour indiquer qu'il s'agit du code de synthèse Success, rnomme l'événement Wrap Up.
5. Cliquez sur Sauvegarder. 
6. Pour mettre à jour le trajet, cliquez sur Calculer. Pour voir les comptes mis à jour, rafraîchissez la page.

Voir l'analyse de l'entonnoir dans l'exemple de parcours

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.

Un parcours doit comporter calculs pour l'analyse de l'entonnoir.

1. Ouvrez le trajet existant que vous souhaitez analyser. 
2. En mode édition , cliquez sur Show conversion. Journey Analyzer calcule les indicateurs de conversion.
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. Pour déterminer le parcours de vos clients, examinez les indicateurs Clients, Taux de conversion, Abandonné out et Avancé lors des événements respectifs.
   
   Exemple: L'analyse de l'entonnoir dans l'événement Bot Start montre que 650 clients ont abandonné le parcours à ce stade, et que 1052 clients ont avancé de à Bot end, de sorte que Bot end a un taux de conversion de 61,7 %. Cela signifie que 61,7 % de vos clients ont atteint la session Bot end.