I know that this thread is over a year old, but in case anyone runs across it moving forward...
If I wanted to accomplish something like this in 2022, I would look at leveraging a Common Module flow for the ANI check scenario that you presented.
1. A Common Module naturally will run and then come back to where it left off.
2. A function that determines down-stream routing, caller experience, etc. seems like something that could/would be used in multiple flows for your organization.
Cheers!
------------------------------
Patrick Rohlf
Summit Broadband
------------------------------
Original Message:
Sent: 11-16-2020 11:21
From: Gordon Bell
Subject: Moving between tasks
Can anyone tell me if is possible to exit a task to another reusable task then come back to the original task flow and pick up where I exited?
I have a scenario that I need to transfer to a reusable task that checks the ANI for VIP status, sets the value of a variable, then returns to the main task which then tests for this 'flag' and amends the routing acordingly.
I've attempted this but the when i re-enter the flow I enter at the start block instead of half way down the flow just after the transfer task.
Thanks
G
#Routing(ACD/IVR)
------------------------------
Gordon Bell
Sabio Ltd
------------------------------