Three changes in this week's release are worth your time. Bot flows can finally call other bot flows. In-queue flows get an error-recovery option that should have existed from day one. And Quality Management forms are now division-aware, which will quietly change who sees which forms in multi-division orgs.
TL;DR
- Bot flows can now call other bot flows (voice-to-voice, digital-to-digital). Modular bot design and parallel development across teams are finally on the table.
- In-Queue Message and Email flows can transfer to another queue on error, instead of being limited to ending the state or the whole flow.
- Evaluation and survey forms are now division-aware. Users only see and edit forms in their assigned divisions, and some workflows now prompt for a division.
Self-Service and Automation
Bot flows calling bot flows
Architect now lets a bot flow invoke another bot flow, and a digital bot flow invoke another digital bot flow, via new Call Bot Flow and Call Digital Bot Flow actions. The pairing is strict: voice calls voice, digital calls digital. Within that constraint, you can finally split a monolithic bot into smaller flows that different teams own and publish on their own schedule.
Know the boundaries before you refactor everything:
- NLU is scoped per flow. A called bot doesn't inherit the caller's intents, slots, or knowledge configuration, so shared understanding has to be designed on purpose.
- The whole chain runs inside one session, and the usual session ceilings still apply (200 turns per session, per-turn action limits). Recursive task invocation is capped at five iterations.
- Subflows can inherit the core flow's language when configured for it, and the core flow's voice processing settings apply across the session.
The action configuration covers naming, target flow selection, and variable passing. So you can hand context into a subflow and get results back, which is everything you need for a hub-and-spoke bot architecture. Licensing spans CX 1 through CX 4 and the AI Experience tiers.
Transfer to queue from the In-Queue Flow Error event
In-Queue Message and In-Queue Email flows used to give you two options when the Flow Error event fired: end the state or end the flow. Now there's a third: transfer the interaction to another queue. An error in your in-queue logic no longer strands a digital interaction. You can shunt it to a fallback queue where a human picks it up.
One catch. If the target queue is invalid at runtime (deleted, misconfigured), the transfer doesn't happen and the system falls back to End State handling. A broken queue reference fails silently into the old behavior. Nobody gets alerted. Requires Communicate or CX 1–3 licensing.
Workforce Engagement
Evaluation and survey forms become division-aware
Quality Management evaluation and survey forms can now be managed by division. Users see and modify only the forms in divisions they're assigned to, and workflows that reference forms (voice survey flows, for example) now surface a division badge and may require selecting a division when you pick a form.
On the flow side: selecting a form auto-populates its division into the flow's division list, and Architect warns you when the flow's division doesn't match the form's, or when a form has no division assigned but the flow does. Access to published survey forms in flows requires the Quality > Survey Form > View permission. Licensing: CX 2/3 or the CX 1/CX 2 WEM add-ons.
What This Means for Your Contact Center
The bot-to-bot calling change is the strategic one, and it's overdue. Until now, a large bot estate meant picking your poison: one sprawling flow that everyone edits, with the merge pain and risky publishes that come with it, or duplicated logic across many bots that drift apart over time. Composable flows let you build a router bot that hands off to specialist bots, say a billing bot and an orders bot, each owned by its own team and released on its own cadence. Respect the per-flow NLU scoping when you design this. Your entry bot needs enough understanding to route correctly, because the specialist bot's intents won't help it.
The in-queue error transfer is smaller, but I like it. Digital interactions sitting in queue belong to customers who have already waited, and losing one to a flow error is the worst failure mode there is. A fallback queue staffed by generalists turns a silent drop into a handoff someone can recover. But watch that invalid-queue fallback. Delete the target queue six months from now and error handling quietly reverts to End State. Put those queue references on your change-management checklist.
Division awareness for forms is the one most likely to surprise people. If your org runs a flat division model, nothing changes. But in a multi-division org, quality analysts may suddenly lose sight of forms they used yesterday, because those forms live in a division they aren't assigned to. Audit before your evaluators notice.
What to Check
- Inventory your largest bot flows and find the natural seams for splitting into called subflows. Plan NLU coverage for the router flow explicitly.
- Confirm variable handoff needs between prospective caller/callee bots before committing to a decomposition.
- Add a Transfer to Queue action to the Flow Error event in your In-Queue Message and Email flows, pointed at a monitored fallback queue.
- Document that fallback queue as a protected dependency, because deleting it silently reverts error handling to End State.
- Review division assignments on all evaluation and survey forms, and verify evaluators and survey flow authors hold membership in the right divisions.
- Check that flow authors have Quality > Survey Form > View where voice survey flows reference published forms.
Full details are in the official Genesys Cloud release notes for July 6, 2026. Questions about how any of this lands in your deployment? Email me.