Bob, yes, this is the "create callback" feature.
So, it does seem that the collective thinking here is that once the caller enters callback after waiting for a period of time in-queue, the time waited is inherited -- although visually the timer resets to reflect how long the "callback leg" of that interaction has waited.
I appreciate those who took a few minutes to reply and help convince me (once again) that we do "retain the position in queue".
Now, I've gotta convince the business. :-)
Cheers,
Dan
------------------------------
Dan DeSive
Acendas Travel
------------------------------
Original Message:
Sent: 03-21-2022 09:19
From: Bob Shappell
Subject: Callback functionality -- holding position in queue. Not so sure....
This is correct. Callbacks maintain (inherit?) all properties of the original call. ACD Voicemail, although "wrapped" in a callback object, resets all properties and enters the queue as a new object.
Dan, please ensure the object you are referring to is indeed a simple Callback (with no voice recording embedded) and not ACD Voicemail (appears like a Callback but with the ability to listen to a recording).
------------------------------
Thanks!
Bob Shappell
Avtex Solutions, LLC
Original Message:
Sent: 03-19-2022 20:59
From: Robert Wakefield-Carl
Subject: Callback functionality -- holding position in queue. Not so sure....
From what I have found, when using the Create Callback took in Architect, all priority, skills, and time in queue are all maintained. ACD Voicemail I found something different - it stripped the time in queue and reset the timer. You might try writing out some participant data so you can compare the data between the call and the callback.
------------------------------
Robert Wakefield-Carl
Avtex Solutions, LLC
Contact Center Innovation Architect
robertwc@avtex.com
https://www.Avtex.com
https://RobertWC.Blogspot.com
Original Message:
Sent: 03-18-2022 10:45
From: Dan DeSive
Subject: Callback functionality -- holding position in queue. Not so sure....
Genesys Documentation states: The callback object placed in the queue takes the position in the queue of the original call and automatically acquires the same skill requirements and priority settings as the original call.
My interpretation of this is that if the caller waited in-queue for 10 minutes, then entered callback, then the callback would be presented to an agent prior to a voice call that has waited 5 minutes, for instance. Hence, "kept its place in queue". However....
In my experience, this is not the case -- the "timer" restarts completely as that callback interaction waits in queue. I do not see how the caller that selected callback while in queue (recurring prompt to do so) gains the benefit of the wait time they invested in the queue once they select callback (and the timer restarts).
What are experiences of others with callback and "keeping it's position in queue"?
We're considering workarounds for this and before we do this, I'd like to validate experiences of other shops using this valuable tool/feature.
Thank you,
Dan
#Routing(ACD/IVR)
------------------------------
Dan DeSive
Acendas Travel
------------------------------