Genesys Cloud - Main

 View Only

Sign Up

  • 1.  optimize specific feature/capability

    Posted 21 days ago

    Good Day Community,

    As a Sr. Technical Account Manager, I'm constantly working with customers who have successfully implemented Genesys Cloud but want to optimize their [specific feature/capability]. I'd love to hear from the community:

    1. What metrics do you monitor to identify optimization opportunities?
    2. How do you balance performance improvements with change management?
    3. What tools or dashboards have been most effective for ongoing optimization?

    Any real-world examples or lessons learned would be greatly appreciated!


    #Other

    ------------------------------
    Minhaj Mubashir
    Technical Account Manager
    ------------------------------


  • 2.  RE: optimize specific feature/capability

    Posted 21 days ago

    Hi Minhaj,

    In environments running Genesys Cloud at scale, optimization usually comes from combining operational metrics, governance, and continuous monitoring rather than focusing on a single feature.

    Here's the approach I typically see working well with customers:

    1. Metrics to Identify Optimization Opportunities

    I usually start by monitoring metrics that highlight capacity, agent efficiency, and customer experience, such as:

    • Service Level and ASAto identify routing or staffing inefficiencies

    • Abandon Rateoften indicates queue design or wait-time issues

    • Average Handle Time (AHT)useful for spotting process or knowledge gaps

    • Agent Occupancyhelps detect over/under-utilization

    • Transfer Ratehigh values may indicate poor routing logic or skill configuration

    • First Contact Resolution (FCR)strong indicator of journey efficiency

    For digital channels (email, messaging), I also monitor response SLA compliance and conversation reopen rates.

    Many optimization initiatives actually start when one of these metrics moves unexpectedly after a configuration change or volume shift.


    2. Balancing Performance Improvements with Change Management

    In most mature environments, the key is controlled iteration rather than large changes.

    A few practices that work well:

    • Test routing or flow improvements in a pilot queue or limited group of agents

    • Document baseline metrics before any change

    • Implement changes during low-volume periods

    • Align with operations and workforce management before modifying routing logic

    In several deployments, we treat optimization changes almost like mini releases, with validation windows and rollback plans.


    3. Tools and Dashboards for Continuous Optimization

    The most effective setups usually combine:

    • Native performance views in Genesys Cloud (Queue, Agent, and Flow Performance views, flow outcomes...etc)

    • Custom dashboards for operational leaders

    • Historical exports or API-driven reporting for deeper analysis

    • Journey or flow analytics to identify IVR containment or drop-off points

    Some teams also build long-term trend dashboards using the Analytics APIs to correlate metrics like volume, staffing, and service level over time.


    Real-World Example

    In one environment I worked with, a customer had rising abandon rates despite stable call volume. After reviewing queue analytics and flow paths, we identified that:

    • calls were entering a generic queue instead of skill-based routing,

    • and agents with the correct skill were underutilized.

    After adjusting the ACD routing and skill priorities, abandon rate dropped by ~18% within a few weeks without increasing staffing.


    Lesson Learned

    Optimization in Genesys Cloud rarely comes from a single change. The biggest gains usually happen when you combine:

    • analytics-driven decisions

    • small iterative improvements

    • close alignment with operations and WFMthe community approach continuousoptimization as well.



    ------------------------------
    Kaio Oliveira
    GCP - GCQM - GCS - GCA - GCD - GCO - GPE & GPR - GCWM

    PS.: I apologize if there are any mistakes in my English; my primary language is Portuguese-Br.
    ------------------------------



  • 3.  RE: optimize specific feature/capability

    Posted 20 days ago

    Hi @Kaio Oliveira

    Thank you for such a thorough and practical response! The real-world example you shared about the routing/skill priority adjustment leading to an 18% reduction in abandon rate is exactly the type of insight I was hoping to surface.Your mention of monitoring conversation reopen rates for digital channels is particularly interesting. Do you have a typical benchmark or threshold that triggers investigation in your environments? 



    ------------------------------
    Minhaj Mubashir
    Technical Account Manager
    ------------------------------



  • 4.  RE: optimize specific feature/capability

    Posted 21 days ago
    Edited by Phaneendra Avatapalli 21 days ago

    Hi Minhaj,

    In many cases we approach optimization on a use-case basis rather than focusing only on individual metrics. When reviewing opportunities, we usually ask whether a change will improve the customer experience or increase operational efficiency.

    1) Metrics: We typically monitor service level, ASA, abandon rate, and queue wait time to identify areas that may require improvement. These metrics usually highlight pressure points in routing or IVR design.

    2) Change management: Before implementing changes, we normally validate them in a lower environment and then roll them out gradually. This helps balance performance improvements with operational stability.

    3) Tools and dashboards: Performance Views and Interaction Details are commonly used to monitor trends and identify optimization opportunities. Analytics data also helps uncover patterns in customer behaviour and agent handling.



    ------------------------------
    Phaneendra
    Technical Solutions Consultant
    ------------------------------



  • 5.  RE: optimize specific feature/capability

    Posted 21 days ago

    Hi Minhaj,

    Some of our businesses have different priorities to others, so when it comes to measuring performance, that can vary.  For those who typically work on Inbound calls, we'd look at ASA, Calls Answered/Abandonment%, Service Level.  For Outbound we look at the volume of Outbound calls and if we're looking at how successful these have been, we'd look at the percentage of wrap outcomes.  Externally, in the CRM's we also keep track of outcomes that way.  We have looked into Outbound Campaigns, but due to staffing numbers and volumes of calls to be made, it's not viable to setup at this stage.

    In terms of change management, we like to make recommendations to the business and gauge their interest regarding the change.  We want to make sure that changes to processes don't negatively impact callers or staff themselves.  Culture is also a big consideration too.  Whilst some people have done things one way for a long time, getting their buy in to a process change can be a challenge.  So we always make sure that they see the benefits to change we'd like to implement.

    In terms of reporting/dashboards, we extract a lot of our call metrics out of the Analytic Workspace to provide to stakeholders who use Genesys.  We're in the process of finalising setting up reporting in PowerBi for better visibility.  Previously reporting was delivered through Emails using Excel spreadsheets.  Dashboards for Supervisors have been great.  It allows them to monitor volume of calls and be able to make better informed decisions on the fly in terms of making sure they have coverage through the day.  



    ------------------------------
    Robert Niblock
    Contact Centre Technology Analyst
    ------------------------------



  • 6.  RE: optimize specific feature/capability

    Posted 20 days ago

    Hi @Robert Niblock

    Thanks for sharing this perspective - you've introduced some important dimensions that weren't covered yet in the thread.

    Quick question: When tracking wrap outcome percentages for outbound success, have you found certain outcomes that serve as leading indicators for other performance issues? (e.g., high "callback requested" rates indicating timing problems?) 



    ------------------------------
    Minhaj Mubashir
    Technical Account Manager
    ------------------------------



  • 7.  RE: optimize specific feature/capability

    Posted 20 days ago

    hi @Phaneendra Avatapalli ,

    Your use-case based approach is a great complement to the metrics-driven perspective Kaio shared earlier.

    I particularly appreciate your emphasis on asking "will this improve customer experience or operational efficiency?" before making changes. It's a simple but powerful filter that prevents optimization for optimization's sake.

    A few observations from your response:

    Environment validation + gradual rollout - This aligns perfectly with Kaio's "mini release" approach. I'm curious: do you typically use specific time-based rollout phases (e.g., 25% → 50% → 100%) or base it more on observing stabilized metrics?
    Your mention of using Interaction Details alongside Performance Views is interesting. I find many customers underutilize Interaction Details for root cause analysis. Are there specific interaction attributes you've found most useful when troubleshooting routing or IVR issues?



    ------------------------------
    Minhaj Mubashir
    Technical Account Manager
    ------------------------------



  • 8.  RE: optimize specific feature/capability

    Posted 20 days ago
    Edited by Phaneendra Avatapalli 20 days ago

    Hi Minhaj,

    For rollout strategy we typically deploy changes during a low-volume period and monitor key operational metrics afterwards. Rather than using fixed rollout percentages (e.g., 25% → 50% → 100%), we usually rely on observing stabilized metrics such as service level, queue wait time, and abandon rate to confirm that the change is behaving as expected.

    Regarding Interaction Details, we’ve found it extremely useful for root cause analysis when troubleshooting routing or IVR behaviour. In particular we review attributes such as the interaction timeline, IVR duration, routing paths, queue transfers, and any participant data captured in the IVR to understand where callers may be spending unnecessary time or encountering friction.

    For example, in one case we noticed through Interaction Details that our IVR was quite long and contained several sub-menus. It took roughly 2–3 minutes for callers to reach the end of the IVR, and if they were unsure which option to select they had to wait through the full prompt sequence.

    After reviewing the routing paths we discovered that regardless of which sub-option was selected, the calls were ultimately routed to the same queue. Based on that insight we simplified the IVR by removing unnecessary sub-menus and routing directly after the primary selection. This significantly reduced IVR navigation time and improved the overall caller experience.


    ------------------------------
    Phaneendra
    Technical Solutions Consultant
    ------------------------------



  • 9.  RE: optimize specific feature/capability

    Posted 20 days ago

    Great topic, Minhaj!

    From my experience working with Agent Copilot implementations, one of the most effective ways to identify optimization opportunities is by closely monitoring adoption and usage through custom reports.

    Metrics like Copilot suggestion usage, acceptance rates, and correlation with AHT/Talk Time trends give a clear view of how well the tool is being utilized and where improvements are needed.

    On the change management side, staying close to agents is key. Gathering continuous feedback directly from them helps refine prompts, improve suggestion quality, and adjust the experience to better fit real interactions.

    This approach naturally increases adoption, and as agents start trusting the tool more, improvements in metrics like AHT tend to follow in a more sustainable way.

    In terms of tools, combining Genesys native dashboards with custom BI (e.g., Power BI) has been very effective to track usage at a granular level and support ongoing optimization.

    One key lesson learned: optimization is much more about iteration and feedback loops than just initial configuration.



    ------------------------------
    Mateus Nunes
    Tech Leader Of CX at Solve4ME
    Brazil
    ------------------------------



  • 10.  RE: optimize specific feature/capability

    Posted 19 days ago

    hi @Mateus Nunes 

    Thank you so much for sharing your experience with Agent Copilot optimization.

    I really appreciate how you've connected adoption metrics directly to business outcomes like AHT. The point about acceptance rates being a leading indicator is particularly valuable.

    Your emphasis on continuous agent feedback resonates strongly with me. It's a great reminder that the technical optimization and the human side need to work together for sustainable improvements.

    The combination of native dashboards with Power BI for granular tracking is something I'd like to explore further with my customers.

    Thanks again for contributing to the discussion!



    ------------------------------
    Minhaj Mubashir
    Technical Account Manager
    ------------------------------