Genesys Cloud - Developer Community!

Hi Community!
Sorry for maybe adding this in the wrong forum - imho it would have fit into multiple categories at once... 

We have the following scenario: 

• Release-Link-Transfers do not work with our (BYOC) carrier - so every call transfered to an external target is still routed via our GC platform/trunk. 
  (We luckily already solved rlated recording issues...)
• We just found out, that in case a "post-flow" is assigned to calls in our flow logic, the assigned flow will also be executed after the call has been transfered to an external target and the execution condition is met - in this case the destination leaving the call, while the caller stays on it. Technically there's naturally nothing wrong with it, because it does what it is supposed to do. 
• Still, that is quite problemativ for us, as we are a service provider and the calls are (consult) transfered (e.g.) to the second level of our customer, if our agents can't handle them. The after call survey that is happening in the post-flow is meant as a quality evaluation for our agents - not the customers own employees, so this should not be happening - as well as it might actually be a workers council/GDPR problem here, to do something like that for our customers employees.

This much about the circumstances - now to the actual technical problem: 

• Agent scripts do not contain any kind of script action to change the post-flow setting. 
• Neither could I find any API endpoint that seems to be related/allow that. 
• Both of the above mentioned approaches would anyway be far from ideal, as a consult transfer (even if initiated via script elements/button, which is the case) could only trigger such an operation/data action call when the transfer is initiated, not when it is finished (as there is unfortunately no such thing as event handling or script actions that could be performed with the agent session ending). Which means: With this approach it would anyway only be possible to "drop" the post-flow in case of any ATTEMPT to transfer a call. If the transfer is not finished, the post-flow would still be removed - and the only way I would see to avoid that, would be offering the agent another button to reactivate the post-flow (if that would be possible anyway...)
• So the best approach would generally be a trigger - and as far as I researched, a trigger for the "user end" of a conversation by consult transfer could be created. 
  But still this wouldn't help, without a data action to change the post-flow setting of the interaction, as there is no related action in workflows - and it would anyway need to do this for a different interaction. 

Any smart ideas for this problem? Without a solution to this we might be forced to stop doing post-flow surveys, which would be a great GC feature completely lost due to it not being  adaptable to all customer needs... I guess I will create an idea for post-flow control operations in agent-scripts now anyway - if not already existing...

Try to create a button to blind transfer to a flow and there clear the post call flow and then transfer to where you need.

Hi Community!
Sorry for maybe adding this in the wrong forum - imho it would have fit into multiple categories at once... 

We have the following scenario: 

• Release-Link-Transfers do not work with our (BYOC) carrier - so every call transfered to an external target is still routed via our GC platform/trunk. 
  (We luckily already solved rlated recording issues...)
• We just found out, that in case a "post-flow" is assigned to calls in our flow logic, the assigned flow will also be executed after the call has been transfered to an external target and the execution condition is met - in this case the destination leaving the call, while the caller stays on it. Technically there's naturally nothing wrong with it, because it does what it is supposed to do. 
• Still, that is quite problemativ for us, as we are a service provider and the calls are (consult) transfered (e.g.) to the second level of our customer, if our agents can't handle them. The after call survey that is happening in the post-flow is meant as a quality evaluation for our agents - not the customers own employees, so this should not be happening - as well as it might actually be a workers council/GDPR problem here, to do something like that for our customers employees.

This much about the circumstances - now to the actual technical problem: 

• Agent scripts do not contain any kind of script action to change the post-flow setting. 
• Neither could I find any API endpoint that seems to be related/allow that. 
• Both of the above mentioned approaches would anyway be far from ideal, as a consult transfer (even if initiated via script elements/button, which is the case) could only trigger such an operation/data action call when the transfer is initiated, not when it is finished (as there is unfortunately no such thing as event handling or script actions that could be performed with the agent session ending). Which means: With this approach it would anyway only be possible to "drop" the post-flow in case of any ATTEMPT to transfer a call. If the transfer is not finished, the post-flow would still be removed - and the only way I would see to avoid that, would be offering the agent another button to reactivate the post-flow (if that would be possible anyway...)
• So the best approach would generally be a trigger - and as far as I researched, a trigger for the "user end" of a conversation by consult transfer could be created. 
  But still this wouldn't help, without a data action to change the post-flow setting of the interaction, as there is no related action in workflows - and it would anyway need to do this for a different interaction. 

Any smart ideas for this problem? Without a solution to this we might be forced to stop doing post-flow surveys, which would be a great GC feature completely lost due to it not being  adaptable to all customer needs... I guess I will create an idea for post-flow control operations in agent-scripts now anyway - if not already existing...