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