Fourteen items and a deprecation deadline three days out. The deprecation is a restatement rather than news, but if you ignored it the first time, this is your last reminder with any runway left in it.
The best thing in these notes is a presence status, which is not a sentence I expected to write.
TL;DR
- Agents can now request an off-queue status and stay On Queue until their active interactions finish, so a long call no longer eats their break.
- Support for the current agentic virtual agent model ends October 1, 2026, with automatic migration after a 30-day opt-in window.
- Screen recording works on managed ChromeOS devices via the WebRTC Media Helper isolated web app.
- Architect bot and digital bot flows get native conversation attribute actions, plus a JSON data type and editor.
Agentic Virtual Agents
Genesys restates the end of support for the existing agentic virtual agent model: October 1, 2026. Test and transition to the latest model before then, or you get auto-migrated after a 30-day opt-in period you didn't schedule. This was first announced on August 31 and it's on the deprecation tracker with the rest.
Three days is not enough time to validate a virtual agent properly. If you're reading this and you haven't started, the realistic plan is to accept the migration and then test hard immediately afterward, with someone watching containment and escalation rates daily for the first week. Pretending you'll finish a proper transition by Thursday is how you find out about a behavior change from a customer complaint.
Routing and Agent Experience
Requesting Off Queue is the week's standout. An agent with active interactions can request Break or Meal, and instead of flipping status immediately, they stay On Queue for presence, reporting, and adherence while receiving no new ACD interactions. Once active interactions and after-call work finish, Genesys moves them to the status they asked for.
This fixes two problems at once. Agents stop losing break time to the call that ran long, and adherence stops penalising them for it. The old workaround was for agents to go off queue and then sit in after-call work in the wrong status, which made every adherence report slightly fictional. Enable this.
External contacts also get personal favorites, up to 100 per user, with no extra permission needed and a filter in the contact list. Useful for anyone who deals with the same named accounts repeatedly.
Voice and Telephony
Admins can now see real-time concurrent call-session usage for cloud media against configured capacity at the org level. Capacity here is based on a configurable outer threshold, so read what yours is set to before you interpret the number.
If you've ever had a vague "calls were failing around 2pm" report with nothing in the logs to explain it, this is the view that tells you whether you were near the ceiling. Worth pinning somewhere a telephony admin will see it during peak.
Architect and Data
Bot flows and digital bot flows get native create, retrieve, and update actions for custom conversation attributes, along with JSON data type support and a JSON editor. Architect flows got the equivalent on August 31, so this closes the gap.
The real benefit is rate limits. Every custom data action doing attribute reads and writes was consuming API quota and adding a failure point to the flow. Replacing those with native actions removes both. If you have data actions that exist only to manage conversation attributes in a bot flow, rip them out.
Admins can also view external event schemas and configurations created through the External Event Ingestion API in the admin UI. Read-only and a first iteration, but previously the only way to know what you'd ingested was to ask whoever wrote the integration.
Recording and Quality
Screen recording now supports managed ChromeOS devices through the WebRTC Media Helper isolated web app, with existing policies and permissions carrying over. ChromeOS fleets have been a hole in quality management programs for a while. If you run Chromebooks and had to exempt those agents from screen recording, that exemption can go.
CRM Integrations
CX Cloud auto-answer gets much finer control, configurable by queue, campaign, user or agent group, and interaction type, and it can trigger earlier in the lifecycle for eligible outbound campaign voice to cut connection latency. Agents get an on-screen notification with caller information when a call is auto-answered.
That notification is the important half. Auto-answer without it is how agents end up mid-conversation with someone they didn't know had connected, and the customer hears three seconds of confusion on every call.
On the ServiceNow side, agents can handle agent-first callbacks inside Unified Experience and start wrap-up while a voice call is still active, where the queue allows it. Salesforce users get group voicemails in the CX Cloud inbox, with forwarding and notes. Same pattern throughout: fewer reasons to leave the CRM.
Work Automation and Workforce Engagement
Workitem Details gets an inline preview where supervisors can change assignee, priority, and due date without going back to the list, and it surfaces skills, languages, contact, and reporter context.
Agents can move their own meal and break times within the day, choosing from slots Genesys calculates won't hurt service level, with optional auto-approval per management unit. Pair this with Requesting Off Queue and you have a real improvement in how break time works for agents on long interactions.
Unavailable times can now be created, updated, and deleted on an agent's behalf through the API, controlled by a new permission scoped by business unit, management unit, and division.
What this means for your contact center
October 1 is the only hard date here, and it's already too close. Decide today whether you're transitioning your agentic virtual agents or accepting the automatic migration, and if it's the latter, book the monitoring time rather than hoping.
The presence and scheduling changes are the ones that affect agents daily. Requesting Off Queue plus flexible break times addresses a long-standing complaint that supervisors have been absorbing manually, and both are configuration rather than projects.
The CRM integration items all reduce tab switching, which sounds minor until you count how many times a day an agent does it.
What to check
- Confirm your agentic virtual agent plan before October 1 and schedule post-migration monitoring either way.
- Enable Requesting Off Queue and brief supervisors on how it changes adherence reporting.
- Turn on flexible meal and break times, choosing per management unit whether changes auto-approve.
- Check your concurrent call-session capacity threshold so the new org metric means something.
- Remove custom data actions that only read or write conversation attributes in bot flows.
- Bring ChromeOS agents into your screen recording policy if you previously exempted them.
- Scope CX Cloud auto-answer by queue and interaction type, and verify agents see the on-screen notification.
Full details are in the official Genesys Cloud release notes for September 28, 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.