That's odd. Voting looks to be available for me and I have seen at least one other vote submitted. Have you got any votes left? If you do, I recommend reaching out to the Aha support folks.
Even if you are unable to vote at the current time, please comment - it all helps to push engagement with the Idea and hopefully increase it's visibility!
Views expressed are my own and do not necessarily reflect those of my employer.
Original Message:
Sent: 07-22-2024 20:37
From: Tatjana Knezevic
Subject: Stripping ACW heritage when interaction is transferred from ACD queue to another Agent
@Paul Simpson
I wanted to support this idea, however, it is closed for the vote :-(
------------------------------
Tatjana Knezevic
www.startelecom.cloud
https://www.linkedin.com/company/star-telecom-www-startelecom-ca-/
Original Message:
Sent: 07-22-2024 16:10
From: Paul Simpson
Subject: Stripping ACW heritage when interaction is transferred from ACD queue to another Agent
OK, so it looks like no ideas exist already, so I have created one. Please give this Idea some love!
------------------------------
Paul Simpson
Views expressed are my own and do not necessarily reflect those of my employer.
Original Message:
Sent: 06-28-2024 10:43
From: Paul Simpson
Subject: Stripping ACW heritage when interaction is transferred from ACD queue to another Agent
We are experiencing a similar issue with reporting of ACW.
So, call comes in, hits a Queue, agent transfers the call to another user. Other user ends interaction, but doesn't disposition the call for a long time (we have many cases of hours, but a few of days!) When you look at the Queue summary stats the ACW (both total and average) reflect that extended ACW, even though the user concerned is not a member of the queue. This means that any KPIs that the queue is being monitored against are screwed up by someone outside their control. (Hardly fair!)
Interestingly, if the Interaction is transferred from one Queue to another and then to a specific user, that user's behavior only affects the last ACD queue utilized.
So, before I create an Idea, is there already one open to have stats only relate to the parts of the call handled within the queue?
------------------------------
Paul Simpson
Views expressed are my own and do not necessarily reflect those of my employer.
Original Message:
Sent: 06-26-2024 01:42
From: Robert Wakefield-Carl
Subject: Stripping ACW heritage when interaction is transferred from ACD queue to another Agent
Currently, the ACW from the first follows the transfer. I know there is work to enhance ACW on transfers as well as allowing No ACW setting on Queues. Look for some improvements in the coming months
------------------------------
Robert Wakefield-Carl
ttec Digital
Sr. Director - Innovation Architects
Robert.WC@ttecdigital.com
https://www.ttecDigital.com
https://RobertWC.Blogspot.com
Original Message:
Sent: 06-24-2024 09:20
From: Gudmundur Sveinsson
Subject: Stripping ACW heritage when interaction is transferred from ACD queue to another Agent
Hi.
We want to skip ACW inheritance when an agent answering a call from a ACD queue and then forwards the call directly to another agent not in the same queue
So when agent A answer a call from a Queue that have ACW mandatory, transfer that call directly to another agent (agent B) that is not in the same queue as agent A and in not using ACW, then agent B won´t need to do any ACW.
Does anybody know If this is possible and if yes, how I can accomplish that ?
Regards,
Guðmundur.
------------------------------
Gudmundur Sveinsson
Advania Island ehf
------------------------------