Genesys doesn't currently support a formal AVA-to-AVA chaining feature. Instead, AVAs are used within bot flows, with Architect calling AI Guides during execution.
There are two options:
The recommended approach is one AVA managing the entire request, using reasoning and actions across systems.
Or
If separation is needed, Architect handles orchestration between flows, but this is flow-level routing-not AVA-to-AVA chaining.
Bottom line: Multi-step experiences are supported, but not as direct AVA chaining. Best practice is a single AVA per conversation goal, with Architect and data actions coordinating backend steps.
------------------------------
Qasim Chaudhry
Professional Services Director
------------------------------
Original Message:
Sent: 04-01-2026 13:08
From: Kashaf Chaudhry
Subject: Agentic Virtual Agents
Hi Everyone,
Is it possible to chain multiple AVA's such that one AVA can kick off another one if the customer asks for multiple actions to be taken. If not, is there way to do it or is this on the roadmap?
Thanks
#AIConfiguration
------------------------------
Kashaf Chaudhry
Customer Success Director
------------------------------