Two things worth your time in the June 1, 2026 release: Journey Management can finally import Architect flows, and WFM got a smarter way to chew through time-off requests. Both cut busywork rather than adding new surface area to learn.
TL;DR
- Journey Management now imports published Architect flows directly and renders them as Sankey diagrams. No more rebuilding flows by hand on the journey canvas.
- WFM supervisors can filter and sort time-off requests by criteria like hire date and performance, and run a sequential auto-approval pass that pauses when a request needs a human decision.
- Adoption cost is low for both. If you already use Journey Management or WFM time-off plans, these slot right in.
Journey Analytics
Import Architect flows into Journey Management
Until now, analyzing a single IVR or bot flow in Journey Management meant recreating its structure on the journey canvas by hand. Tedious, error-prone, and enough of a chore that most people skipped flow-level analysis entirely. This release fixes that: you can pull a published Architect flow into Journey Management directly.
The workflow: from the journey canvas, choose Import Flow, pick a published flow, and review it in the Journey Flows Sankey view. Select the nodes you want to analyze, pick the outcomes and milestones you care about, and add them to the journey. Save and calculate, and the flow's real traffic patterns become part of your journey analysis.
This is the feature I'd try first. If you've ever wanted to know where callers bail out of a specific menu, or which branch of a bot flow correlates with escalations, you can get there in minutes now instead of burning an afternoon on canvas work. One catch: the import only works against published flows. Drafts don't count.
Workforce Engagement
Time-off request filtering, sorting, and sequential approval
The second update goes after one of the least glamorous supervisor chores there is: the pending time-off queue. Two things changed.
Filtering and sorting got deeper. On top of the existing agent, date-range, status, and activity-code filters, supervisors can now order requests by criteria such as hire date and performance, and stack up to three sort categories at once. If your time-off policy awards priority by seniority or scorecard results, the request list can finally match the policy instead of arrival order. Overdue.
There's also a sequential evaluation run for requests flagged for manual review. Kick it off and Genesys Cloud walks the list in your chosen sort order, auto-approving each request against the time-off plan rules and showing progress as it goes, until it hits a request it can't approve on its own (a coverage limit, say, or a plan rule violation). Then it pauses with an action-required prompt. You resolve or skip that request and the run continues. You can also mark items to be skipped automatically in future runs, and export the results to CSV when it finishes.
What this means for your contact center
The Journey Management import is the bigger deal. Genesys has been positioning Journey Management as the analytical layer over everything customers touch, and flow import removes the main reason people weren't using it on self-service. If your org licenses Journey Management but usage stalled because setup felt heavy, revisit it now. It's the right tool for the IVR containment and bot-abandonment questions Architect reporting can't answer on its own.
Watch your scope, though. An imported flow gives you that flow's structure, and you still have to choose outcomes and milestones that mean something. Import everything and select every node and you'll produce a Sankey diagram nobody can read.
On the WFM side, sequential approval turns the supervisor's job from processing requests one by one into handling exceptions. That's a real workload cut. But the automation is only as good as the limits and policies it evaluates against, and if your time-off plans have loose or outdated rules, the run will either rubber-stamp requests it shouldn't or pause constantly. Tighten the rules first, then turn on the automation.
What to check
- Import one high-traffic, published Architect flow into Journey Management and validate the Sankey view against what Architect's own metrics tell you.
- Confirm the flows you want analyzed are published. Unpublished work isn't importable.
- Review your time-off plan rules and coverage limits before relying on sequential auto-approval. The run enforces exactly what's configured, nothing more.
- Decide your sort policy (seniority, performance, submission date) up front, since the evaluation run processes requests in that order.
- Check role permissions. Journey creation requires Creator/Editor roles, and time-off evaluation is gated by WFM admin permissions.
Full details are in the official notes: Genesys Cloud Release Notes — June 1, 2026.
Questions about how these changes affect your environment? Email me.