Twenty-four items this week, three of them deprecations. One of those three has a real deadline you should put on a calendar today.
TL;DR
- Attribute-based access control (ABAC) lands, letting admins gate access by IP or time of day and consolidate the old Allowed IP Addresses rules into one policy engine.
- Canned response libraries can now be scoped by division, so agents only see what's relevant to their team.
- The current agentic virtual agent model loses support on October 1, 2026, with automatic migration for anyone who hasn't moved by then.
- New integrations can no longer embed the Genesys Cloud login web app in an iframe; existing ones have until February 4, 2027.
Identity & Access Management
ABAC is the headline item. Admins can now write access policies keyed on attributes like IP address or time of day, and migrate existing IP-based restrictions into the same system instead of running two separate mechanisms. This is the kind of feature that sounds administrative until you're the one explaining to security why contractor access isn't time-boxed. Worth a look even if your current IP allowlist works fine, because ABAC is clearly where Genesys is putting future access-control investment.
Canned response libraries get division scoping, so a supervisor can hand a division only the libraries that apply to it. Small feature, real payoff for any org running multiple brands or regions out of one instance where agents were wading through libraries meant for someone else's queue.
The login web app can no longer be loaded in an iframe for new integrations, and existing ones have until February 4, 2027 to switch to pop-out authentication. This is a clickjacking mitigation, not a Genesys whim, so don't bother asking for an exception. If you embed the Genesys login anywhere, a custom portal or an older CTI integration, start the inventory now. Five months sounds generous until nobody can say which internal tool does this.
Agentic Virtual Agents
The bigger deprecation: support for the current agentic virtual agent model (which Genesys calls the APT-1 model) ends October 1, 2026. Test and transition before then, or you get auto-migrated to the new model with a 30-day opt-in window you didn't choose the timing of. I'd rather pick my own testing window than have Genesys pick it for me. If you're running agentic VAs in production, this is this week's actual to-do item, not background reading.
Separately, agentic VA authors can now preview and transition to an updated model voluntarily, ahead of that October deadline, with expanded language support including German (Switzerland), Hebrew, and Thai. Do this early and you skip the forced migration entirely.
The VA Performance dashboard also picked up cost and latency trends for LAM-based agents, and the Bot Flow Reporting Turns API now returns turn-level metadata for tool calls, knowledge calls, and guardrail outcomes. Both are the kind of observability that should have shipped with agentic VAs on day one, but I'll take them now.
Customer Engagement and Automation
Architect gets three new native actions this week: retrieving customer intents, partially updating external contacts, and managing conversation attributes directly in a flow. All three replace custom data actions that people were building by hand, which means less flow logic to maintain and fewer places for a data action timeout to break something. If you've got custom data actions doing any of this today, there's no reason to keep them.
Outbound campaigns can now pick a content template at runtime based on a contact list column, so one campaign can serve multiple languages or notification types instead of forking into separate campaigns. And canned responses finally support file attachments (documents, PDFs, images, video), a basic capability that took longer than it should have to arrive.
Copilot can now create and update worktypes and schemas from natural language, and AI agents can create workitems at runtime. Useful if you're building work automation from scratch, less relevant if your schemas are already stable.
Data and Reporting
Sensitive data masking for messaging and voice transcripts now covers Danish, Finnish, Norwegian, and Swedish, closing a gap for Nordic-language contact centers. The Analytics Aggregates API now returns only groupings that match your filter instead of padding the response with everything else, which should shrink payloads and simplify client code that was filtering results after the fact. Dashboard ownership can now be transferred individually or in bulk, with email notification to both sides. Small, but it's the kind of thing that becomes a fire drill the day someone leaves without warning.
What this means for your contact center
October 1 is the date that matters this week. If you have anything running on the current agentic virtual agent model, get it into AI Studio Preview and validate the new model before Genesys does it for you on its own schedule.
The iframe deprecation is a slower burn but not one to file away. Security-driven deprecations don't get extensions, and the honest answer to "does anything embed the login page" is usually "nobody's sure," which is exactly why it's worth an afternoon now.
ABAC is worth adopting even without a forcing function. If your access model is a pile of IP allowlists nobody remembers the reasoning for, this is the cleanup opportunity.
What to check
- Preview your agentic virtual agents on the new model in AI Studio and plan the transition before October 1.
- Inventory any integration that embeds the Genesys Cloud login web app in an iframe.
- Evaluate ABAC as a replacement for existing IP-based access restrictions.
- Scope canned response libraries by division if agents are seeing libraries outside their team.
- Replace any custom data actions duplicating the new Architect actions for intents, contact updates, or conversation attributes.
- Check the VA Performance dashboard's new cost and latency trends if you run LAM-based agents.
Full details are in the official Genesys Cloud release notes for August 31, 2026. Questions about how any of this lands in your environment? Email me.
Tracking a deadline? Every announced Genesys Cloud deprecation is on the deprecation tracker.