The new consult transfer behavior observed arrived with the Multi Contextual Panels release on Aug 11. We were not using MCP after testing it back in Feb revealed it was not an ideal screen layout for our users so postponed until it became mandatory on Aug 11. The MCP documentation/videos mentioned the call controls were also changing as part of the MCP update but it didn't mention the change in consult transfer behaviour so we are currently doing manual direct transfers as a work around until Genesys advises if they are restoring the previous behaviour or not. If they are not restoring the behaviour we will need to go and modify all our agent scripts to avoid using consult transfer option :(
Original Message:
Sent: 08-21-2025 08:38
From: Nettie B Roe
Subject: Issue with Consult Transfer
Travers, thank you for sharing your case. Did your problem also start around the 10th of this month? And did your tech ask about your firewall? In our situation, the issue does not occur every time. We have yet to find a pattern. Our organization is only partially on Genesys, so sometimes it is necessary to transfer customers to toll free numbers which are always answered by an IVR. In many of those cases, the agent will initiate the consult transfer, the customer will immediately go on hold like they are supposed to, and the agent will hear the IVR message but they do not have the controls to bring the customer back into the call once they have reached a live party. This is especially problematic because we use the consult option for translation services for our Spanish speaking customers. We could use the conference option if it automatically put the customer on hold like the consult option, or at least gave us an option to manually put the customer on hold, but that is not the case. Which, to me seems a rather stupid design, but that is a battle for another day.
------------------------------
Nettie B Roe
Telecommunications Tech
Original Message:
Sent: 08-21-2025 02:29
From: Travers Dunne
Subject: Issue with Consult Transfer
Hi Nettie,
We have raised a ticket also and supplied logs and video of this new behaviour. What we have observed is when consult transferring to a queue the system will show the transfer buttons ONLY if there is no agent being offered the call in the destination queue. If an agent is being offered the call the system will show the agents name that is being offered the call and only show the disconnect button until the agent answers the call or they decline/miss the call offer.
We urgently need this changed back so that transferring agents can immediately complete the transfer once they've confirmed its been answered by the in-queue flow. All our agent scripts have shortcut buttons using consult transfer which are now not usable for any that go direct to a queue.
This new behaviour of "cannot transfer until answered" also affects transfers to external numbers where it waits for the call to be answered before displaying the transfer buttons.
------------------------------
Travers Dunne
Original Message:
Sent: 08-20-2025 09:31
From: Nettie B Roe
Subject: Issue with Consult Transfer
We recently started having an issue with the consult transfer option. We use this feature a lot but recently agents have reported that when they click on this option and then dial a number or select a queue to transfer the call, they do not get the two party controls that they normally do. They do not have any control for the customer line, who is apparently on hold judging by the call recordings. This is random as sometimes it works and sometimes it does not. We did notice in trying to reproduce the issue that if an agent has a successful consult, disconnects and tries a second consult with a different number, that second attempt failed. Has anyone else had a similar issue with consult and if so, what was the cause and what did you do to fix it?
#Unsure/Other
------------------------------
Nettie B Roe
Telecommunications Tech
------------------------------