No, there’s no concept of “push/pop” or more generally “gosub vs. goto” when transferring control from one handler to another. All hand offs are “goto” and there’s no way to jump back to whatever object (or conversation) you happened to be at before arriving at a handler.
We had looked into this – I’m familiar with products like the old AVT model where you can do a “push” of the object you’re on before traveling to the next object (their handlers were a bit different but the model was roughly equivalent) and then as an exit action you could issue “pop” to jump back. This has some power and appeal however it’s very unwieldy given the various paths you can go down to reach a handler (it may be from a routing rule, a direct extension dial by the caller or mapped to a one key rule etc…) – there may or may not be something to “pop” to in that case – in the old AVT model this would essentially dump you back to the opening greeting or “home state” of sorts which sounds very, very odd to the caller.
Anyway – a “breadcrumb” feature of some sort would be handy stuff but implementing it in a safe and usable way is a difficult problem to solve so you’ll have to assume all trips are one way and you’ll have to do separate handlers with separate “return” logic if you want to get back to where you started.
