What is the high level attribute you are looking to bill on? From the agent status view, you could use the total for "interacting" time. Interacting will capture linearly the amount of time an agent spent interacting on an ACD assigned conversation. If there's overlap of conversations, it's still counted as a singular bucket. The drawback is that you can't correlate "interacting" time directly to a single queue especially considering the circumstance where an agent could be interacting with multiple conversations that are assigned to different queues.
The actual active activity for a callback happens under the voice channel. You could consider using only the voice talk time metric as your billing point. The block you highlighted in #3 would be counted towards the voice media channel's talk time.
------------------------------
Ryan Legner
Staff Product Manager, Genesys Cloud CX
------------------------------
Original Message:
Sent: 11-15-2023 09:15
From: Judy Heckbert
Subject: Double Talk time
Thanks Ryan but that isn't helping with our current billing situation. Any temporary recommendations?
------------------------------
Judy Heckbert
NTT America, Inc
------------------------------
Original Message:
Sent: 11-15-2023 09:09
From: Ryan Legner
Subject: Double Talk time
Hello Judy! We do have a feature in the works to address this issue. https://genesyscloud.ideas.aha.io/ideas/ANLS-I-4 More details around exactly what this feature changes is explained within that idea. We expect to release this feature early 2024.
------------------------------
Ryan Legner
Staff Product Manager, Genesys Cloud CX