Genesys Cloud - Main

 View Only

Sign Up

Expand all | Collapse all

Callback Reporting & Analytics Updates

  • 1.  Callback Reporting & Analytics Updates

    Posted 16 days ago
    Edited by Sherlaine Lau 3 days ago

    Upcoming Feature: Dedicated Callback Reporting & Analytics Updates

    We are introducing dedicated lifecycle-based callback reporting in Genesys Cloud. This update provides true customer wait-time tracking, discrete attempt and outcome reporting, dedicated queue views, and separates Customer First Callback (CFC) metrics from standard voice reporting.


    What's new

    • True Virtual Wait Time: Tracks customer wait from initial request to connection with an agent across all attempts.

    • Attempt & Outcome Visibility: Report directly on callback attempts, schedules, and outcomes (Connected, Abandoned Reach, Not Reached).

    • Virtual Wait SLA Option: An opt-in setting in Analytics Settings that measures callback service level against actual customer wait time.

    • Callbacks Performance Tab: A dedicated view in Queue Performance to monitor callback metrics directly.

    • Separated CFC Voice Metrics: Second-pass CFC legs are separated from standard voice counts, giving you clean, uninflected inbound metrics and dedicated callback reporting.

    Transition guide

    This guide explains what is changing in callback reporting, who is affected, and what to do about it. 

    Who this affects 

    This applies to you if you use Customer First Callback (CFC), the callback type where the system calls the customer first and then connects the call to an agent. 

    If you only use Agent First Callback (AFC), where an agent places the outbound call to the customer, these changes do not affect you. 

    What to do 

    • Expect your CFC queues to show lower Offered, ACD, Answered, Abandon, and Flow Out values. The activity did not disappear, it moved to its own callback-specific counts. 

    • If you need the old combined totals, set up a custom calculation to add the two values back together. 

    • Consider opting in to the new service level calculation for callbacks. It takes effect immediately and can be turned off again if needed. 

    What's changing: reporting values 

    Today, a CFC callback involves a “second pass” call leg: after the system reaches the customer, that call is routed back through the queue a second time to find an agent. Historically, that second pass activity has been counted together with your regular, first-time call activity. 

    With this release, that second pass activity is being broken out into its own separate counts, instead of being folded into your standard numbers. 

    What you'll see 

    • Your CFC queues' Offered, ACD, Answered, Abandon, and Flow Out values may drop after this change goes live. 

    • This drop is expected. It reflects the second pass activity being removed from those numbers, not a loss of data. 

    • That same activity is now viewable on its own, as dedicated callback counts, so you can still see it, just separately from your regular call metrics. 

    Why we made this change 

    Blending the second pass activity into standard call metrics could make a queue's call performance look better or worse than what customers actually experienced on their first-time calls. Separating the two gives you a cleaner, more accurate view of both your regular call activity and your callback activity on their own terms. 

    If you need the combined total 

    If a dashboard, report, or business metric depends on the old combined number, you can recreate it by adding the standard value and the new callback-specific value back together using a custom calculation. 

    What's changing: service level (SLA) 

    We recommend opting in to the new service level calculation option for callbacks, called Use Callback Virtual Wait SLA. 

    • Today, callback service level is calculated the same way as a regular answered call: the clock runs from when the callback is offered to the queue until an agent answers the callback object.  This method doesn’t account for time it takes for the agent to reach out to the customer. 

    • This release introduces Virtual Wait: the time from when the callback is created and enters the queue until the customer is actually connected with an agent, regardless of how many attempts or steps it took to get there. It's meant to be an honest measure of how long the customer actually waited for their callback. 

    • The new SLA option lets you calculate callback service level against this Virtual Wait time instead of the standard wait-to-answer time. In effect, you're choosing what the SLA clock is measuring: a specific answer event, or the customer's full wait for their callback. 

    • Turning this on will immediately change your reported service level values for the callback media type. This is expected: it's measuring something different, and for callbacks a more accurate reflection of customer wait, not a data issue. 

    • You can switch back to the previous calculation at any time if the new values don't work for you yet. 


    Sign up for a chance to be selected for our Beta.

    Learn more

    We will share another update as we get closer to General Availability. Stay tuned!


    #Outbound
    #Roadmap/NewFeatures

    ------------------------------
    Sherlaine Lau
    Staff Product Manager - Callbacks



  • 2.  RE: Callback Reporting & Analytics Updates

    Posted 16 days ago

    Great enhancement thank you for sharing Sherlaine.



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



  • 3.  RE: Callback Reporting & Analytics Updates

    Posted 8 days ago

    Great progress, this will be really useful and prevent a lot of work out in the countries :-)



    ------------------------------
    Magnus Andersson
    other IKEA IT AB
    ------------------------------



  • 4.  RE: Callback Reporting & Analytics Updates

    Posted 8 days ago

    Very good.... Great enhancement



    ------------------------------
    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.
    ------------------------------



  • 5.  RE: Callback Reporting & Analytics Updates

    Posted 8 days ago

    I see Callback reporting documentation About callback reporting - Genesys Cloud Resource Center provides metric names where most, but not all of those metrics map to values in Conversation Data Model. Is there a mapping available? Thanks!



    ------------------------------
    Benjamin Wyatt
    ------------------------------



  • 6.  RE: Callback Reporting & Analytics Updates
    Best Answer

    Posted 7 days ago

    Hi Benjamin,

    The details are on this page under metrics:

    https://developer.genesys.cloud/analyticsdatamanagement/analytics/detail/conversation-data-model#metrics-on-conversation-details

    Metrics

    GC Metric

    Applies to

    Description

    Callback Attempts

    nCallbackAttempts

    AFC, CFC

    The number of times the system or agent attempts to reach the customer for a callback. A callback can have multiple attempts before it resolves to an outcome, including Callback Reached, Callback Not Reached, or Callback Abandon.

    Callback Scheduled

    nCallbackScheduled

    AFC, CFC

    Indicates that the callback was created as a scheduled callback rather than routed immediately.

    Active Callback

    tActiveCallback

    AFC only

    Reported on the callback media type, the time an agent spends on a callback while a call is active.  Ensures agent does not accrue handle time on the callback media type while they accrue voice Handle Time.

    Time to First Dial

    tFirstDial

    AFC only

    The time from when the agent answers the callback until the agent first places an outbound call to the customer.

    Time to First Connect

    tFirstConnect

    AFC only

    The time from when the agent answers the callback until the customer first answers the call.

    Callback Reached

    tCallbackConnect

    AFC, CFC

    Indicates that the callback successfully reached an agent. For AFC, this occurs when the agent's outbound call is answered. For CFC, it occurs when the system's reconnect is routed to a selected agent.

    Callback Not Reached

    tCallbackNotReached

    AFC, CFC

    Indicates that the system or agent did not reach a live customer. Reasons can include no answer, busy, invalid number, voicemail, or maximum attempts reached.

    Callback Abandon

    tCallbackAbandon

    CFC only

    Indicates that the customer was live on the line but the interaction ended before an agent was selected.

    Callback Virtual Wait

    tCallbackVirtualWait

    AFC, CFC

    The amount of time the customer actually waits for a callback outcome. For scheduled callbacks, this metric does not include the time spent waiting for the scheduled callback time to arrive. Dwell time is not counted as a virtual wait.

    Callback Over SLA

    nCallbackOverSla

    AFC, CFC

    Increments when a callback exceeds the configured target time to reach Callback Reached, as an alternative to timing SLA off a standard Answer event.



    ------------------------------
    Shazia
    ------------------------------



  • 7.  RE: Callback Reporting & Analytics Updates

    Posted 7 days ago

    Shazia Shafique Thank you for sharing.



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



  • 8.  RE: Callback Reporting & Analytics Updates

    Posted 7 days ago

    Thanks for the list. Those UI names don't show up in the link you provided. I provided feedback on the page  



    ------------------------------
    Benjamin Wyatt
    ------------------------------



  • 9.  RE: Callback Reporting & Analytics Updates

    Posted 7 days ago

    Thanks for sharing 



    ------------------------------
    Akhil
    ------------------------------



  • 10.  RE: Callback Reporting & Analytics Updates

    Posted 8 days ago

    Hi Sherlaine Lau!

    Great explanation. Thank you very much for sharing.



    ------------------------------
    Juliano Fernandes Mendes Pimentel De Paiva
    Genesys Analyst
    ------------------------------



  • 11.  RE: Callback Reporting & Analytics Updates

    Posted 7 days ago

    Thanks for sharing 



    ------------------------------
    Narasimha
    ------------------------------



  • 12.  RE: Callback Reporting & Analytics Updates

    Posted 7 days ago

    Hi Sherlaine, 

    could you please share the tentative GA timeline for this feature? Also, is there an Idea associated with this feature that we can follow?

    Thanks!



    ------------------------------
    Rainbow
    Software Engineer
    ------------------------------