As is noted in a number of other discussions in the general community (as opposed to the developer community), if you use a Set Whisper Audio during the inbound flow, that whisper overrides the queue-configured whisper not only for the initial transfer to the queue whereby the first agent answers, but also for subsequent transfers of that same call that the agent(s) may make. So if the inbound flow does a Set Whisper Audio to PromptA, when that call routes initially to Queue1, Agent1 hears PromptA. If Agent1 then transfers that call to Queue2 (and Queue2 has PromptB configured to play for all agents, not just auto-answer), Agent2 who answers that transfer still hears PromptA.

The above is "known behavior."

What I'd like to know is whether or not there is some way to "clear" that Set Whisper Audio or issue a new Set Whisper Audio (using the queue default as the 'value' of that Set Whisper Audio function) with an agent Script and/or a Data Action. 

Alternatively, I'd like to know if anyone has figured out a way to force the in-queue flow to run so the whisper can be set/reset there. Obviously when there are no agents available, NONE of this is an issue because the in-queue flow will run when there are no agents waiting (call surplus).

Third possible approach: let's assume the call has been answered by Agent1. Is there some way via the agent Script actions, etc. or a data action to ADD a required skill (let's pretend the required ACDSkill to add is called 'TRANSFER_SKILL') to the interaction such that when Agent1 transfers the call to another queue, this new skill is now required in addition to the skill that was required to start with. My thinking here is that NO agent would have the 'TRANSFER_SKILL' ACD Skill which would thus force the call to sit in the in-queue flow (where the 'TRANSFER_SKILL' can then be removed once whatever required processing is completed). I have found an API that allows you to adjust the skills but it states that it only works on calls that are presently in-queue.

I'm aware of the idea to transfer to a flow, but the customer I'm asking on behalf of is allergic to this approach due to the fact that their ~12,000 agents have the queue names memorized. I also came up with an idea to create a "second" queue to go along with the "real" queue but with _XFER appended to the end of the name. The idea here is that the agent would pick that _XFER version of the queue, but the _XFER version would have no members, thus forcing the in-queue flow. Once it hits the in-queue flow, whatever required processing could be completed and then that in-queue flow transfers the call to the "real" queue.

With respect to the transfer to a flow idea, that MAY work if I created a distinct flow for each queue and gave the flow the exact same name, but to try to eliminate transfer errors, would there be a way that if the agent searches by name, I could block searching the queues such that the only search results would be the flows with the same name. If the search shows results both under the Queues icon and the Flows icon, my fear is that even with training, agents would still pick the queue instead of the flow.

I'm trying to be very, very creative here ;).