Please give a quick overview of your product feature request or feedback and note who in your organization is affected by this issue [ex. agents, admins, customers, etc.]
I am requesting the ability to "pause" a procedure in the Advanced AI Chat Bot to link to another Use Case (Procedure or Dialogue) at any point, and then return to the original procedure once complete. For example, the bot could pause the current procedure, run another use case to display a dynamic carousel and collect a user parameter, and then pass that context back to "unpause" the first procedure and continue the flow. This primarily affects admins and bot builders in our organization.
What problem do you see this solving?
Currently, bot builders have to design procedures that "jump" to different actions based on parameters collected in future steps, and then awkwardly link back to the original procedure. This feature would eliminate these convoluted jump loops, solving major design and maintenance headaches when building or updating bot capabilities.
When was the last time you were affected by this lack of functionality, or specific tool? What happened? How often does this problem occur and how does this impact your business?
I am affected by this every time I need to build even a semi-complex procedure. Because we cannot simply pause and return, I end up spending hours caught in a tedious cycle of building, testing, rebuilding, and testing again. This is a massive drain on productivity and significantly slows down our ability to deploy new bot functionalities.
Are you currently using a workaround to solve this problem? (If yes, please explain)
Yes, the current workaround is to update the procedure with a "check step." I have it check if a specific parameter exists; if it does, it skips the first part of the procedure that calls the use case. If it doesn't, it continues to the step that collects the parameter. This is incredibly inefficient—if you need to collect 2-3 parameters and build different flows for each, it quickly devolves into a highly complex, unmanageable spiderweb of routing.
What would be your ideal solution to this problem? How would it work or function?
The ideal solution is to allow procedures to naturally "Pause" when linking to another use case and automatically "Unpause" (return to the exact point it left off) when that use case is complete. The procedure could then continue normally using simple branching steps, entirely removing the need for a procedure to be called over and over again from the beginning.