Hello Vittorio,
Great question, this is actually a really solid use case, and yes, there's a supported way to do exactly what you're describing. The typical approach is to handle the initial intent detection and any disambiguation in Architect first using things like Ask for Slot, Yes/No, or menus, store that info in variables, and then pass it into your Virtual Agent using the "Call Guide" action.
When you configure that action, you can map your Architect variables directly to input variables in your AI Guide, so the Guide starts with all the context you already collected and doesn't need to ask the same questions again. This works well for scenarios like narrowing down "password" issues into something more specific before handing off to the Guide.
From there, the Guide can use that context to give more tailored responses and even pass data back to Architect if needed. It's essentially a hybrid model-Architect handles the routing and data collection, and the AI Guide takes over for the more dynamic, conversational part.
If you're using Agentic Virtual Agents, there's also a similar option with the Call Agentic Virtual Agent action that supports passing input/output variables the same way. Overall, the key idea is that context is passed explicitly between components, which gives you a lot of control and keeps the experience smooth without repeating questions.
Hope this helps!
------------------------------
Cameron
Online Community Manager/Moderator
------------------------------