Hi Yvgeni,
Thank you for sharing the Ideas portal link as well.
Hopefully with more votes and customer interest it gets additional attention, as it definitely seems like something multiple organisations are looking for when implementing CGA reporting and visibility.
------------------------------
Phaneendra
Technical Solutions Consultant
------------------------------
Original Message:
Sent: 05-24-2026 03:28
From: Yvgeni Liberman
Subject: Queue - CGA Reporting and RT Monitoring
Hello Phaneendra,
Many thanks for your response.
As I can see from the two links you sent, I am not the only one with this question. I also found this related idea on the Ideas portal:
https://genesyscloud.ideas.aha.io/ideas/CERTNG-I-2139
However, it is still "Under PM Review."
Regards,
------------------------------
Yvgeni Liberman
Solutions Architect
Mobile +972 52-6344414
Voice +972 3-9281514
e-mail yvgeni_new@itnavpro.com
------------------------------
Original Message:
Sent: 05-24-2026 03:07
From: Phaneendra Avatapalli
Subject: Queue - CGA Reporting and RT Monitoring
Hi Yvgeni,
From my understanding and from a few similar CGA/Conditional Routing discussions I came across in the community, one of the current challenges is that the interaction itself remains within the original queue while the eligible agent pool dynamically expands in the background.
Because of that, the reporting visibility seems to focus more on:
rather than exposing very explicit CGA activation/group routing reporting directly in standard views.
I also noticed discussions where even the Conversation Details Analytics API was not always exposing enough information to reliably identify which conditional group handled the interaction historically.
Some related discussions I found useful:
Hope this helps and someone with more hands-on CGA reporting experience may be able to add further detail/corrections as well.
------------------------------
Phaneendra
Technical Solutions Consultant