Thirteen items, and the one that matters most is not new. The Salesforce data action credential deprecation I wrote about back in August hits its deadline on October 7, two days from now, and Genesys is restating it here. I'll start there.
TL;DR
- Last call on the Salesforce (legacy) credential type for data actions: it stops working October 7, 2026. Genesys announced this on August 10. Migrate to the OAuth Client Credential Flow type.
- Genesys will run network maintenance to introduce its own ASNs, by region, on Sundays between January 10 and January 31, 2027. Expect brief voice disruptions in a 2:00 to 4:00 a.m. local window.
- BYOC Cloud inbound carrier trunks can now use SIP digest authentication instead of relying on IP ACLs alone.
- Object dependency tracking shows which flows and data actions depend on an integration before you change it.
Deprecations
Genesys is restating a deprecation it announced on August 10, not announcing a new one. On October 7, 2026, the Salesforce (legacy) credential type stops working for Salesforce data action integrations. That credential type uses the Salesforce OAuth Username-Password Flow, and Salesforce is retiring that flow, so Genesys is following. You migrate to the Salesforce (OAuth Client Credential Flow) credential type, which uses OAuth 2.0 client credentials. It's been on the deprecation tracker since August and I covered it in the August 10 post.
So you had about eight weeks. What you have now is two days. A restatement this close to a deadline usually means the vendor can see how many customers haven't moved yet, and if you're one of them, treat this as the last warning rather than a notice.
Go and look now, and look at all of them. The dangerous one is never the integration you configured last month. It's the one somebody set up for a single use case three years ago, which still sits in a flow branch that fires for two percent of calls, and which nobody will connect to this deadline when it breaks.
The fix is not entirely in your hands either, which is the part that makes two days uncomfortable. Moving to client credentials means changes to the connected app on the Salesforce side, so if your Salesforce admin is a different person on a different change calendar, start that conversation before you start the audit.
Voice and Telephony
Genesys is introducing its own Autonomous System Numbers for regional network prefixes, with maintenance running by region on Sundays from 2:00 to 4:00 a.m. local time between January 10 and January 31, 2027. Customers may see brief service disruptions including dropped or failed voice calls during their region's window. No firewall or network changes are required on your side.
Three months of lead time on a maintenance window is good practice and I'll say so. Put it in your change calendar now and work out which Sunday is yours, because "2:00 a.m. local time" is a quiet window for a domestic contact center and the middle of the shift for anyone running follow-the-sun support. If you have 24/7 coverage, that's a staffing conversation, not a networking one.
BYOC Cloud inbound trunks also gain SIP digest authentication, which verifies the sender of inbound SIP requests rather than trusting an IP allowlist. If your carrier supports it, turn it on. IP ACLs are a reasonable first control and a weak only control, and anyone who has watched a carrier change source IPs without warning knows the operational pain too.
Platform and Integrations
Object dependency tracking lets admins see relationships between integrations, data actions, and Architect flows, so you can tell whether something is safe to modify or remove. This is the tool that would have made the Salesforce credential work above a ten-minute job instead of an archaeology project, and it arrives in the same release. Use it for that migration, then use it before every integration change after.
The Embeddable Framework gets a configurable interaction deallocation period, so the default two-minute delay that keeps completed interactions on the agent roster can be shortened or turned off entirely. Worth adjusting if your agents complain about roster clutter, worth leaving alone if they rely on that window to finish notes.
Analytics and Journey Management
Bulk metric exports from the agent, queue, skill, and DNIS performance views now handle high volumes without splitting a year-to-date pull into separate date ranges. Anyone who has built a quarterly reporting process out of six stitched-together CSVs will appreciate this more than the one-line release note suggests.
Journey Management adds a read-only details panel when you click an event card, showing the event name and type, applied filters and whether they include or exclude, and any time or count rules. Journeys built six months ago are hard to read, and this makes reviewing one possible without opening every card.
Social listening picks up Facebook engagement metrics for owned pages, covering likes and reactions, shares, comments, and video and Reels views, with filtering and sorting. Useful if social is part of your service channel mix rather than purely marketing's problem.
Agent Copilot and Quality
Agent checklists can now be tested during configuration. Paste or select a transcript and see which items match, with supporting evidence where available. Testing a checklist by publishing it and waiting for real interactions was never a sensible loop, so this is a straightforward fix.
Quality gets two numbers worth knowing: evaluations generated by Agent Auto-Evaluation Forms are now distinguishable from manual ones in analytics, Interaction Search, and Evaluation views, labelled as Virtual Supervisor. And the agent scoring rule limit per program goes from five to twenty.
The attribution change is the more consequential of the two. If you run automated evaluations alongside manual ones and your quality reports blended them, your trend lines were measuring two different things at once. Split them and look at the automated scores on their own before you trust them.
Work Automation and Workforce Management
Case plans can now have between one and five configurable stages, replacing the fixed three-stage structure. If you bent your process to fit three stages, you can unbend it.
The Time-Off Requests view gets its quick status filters and previous and next date navigation back, with the range controls stepping by the length of the range you selected. Small restoration, noticeable to anyone who reviews time off weekly.
What this means for your contact center
Do the Salesforce credential audit today. Not this sprint, today. It's the only item here with a deadline inside the week, the failure is silent until a flow tries to call Salesforce, and the remedy needs someone with Salesforce admin rights.
The January ASN maintenance is the opposite kind of work: nothing to configure, one calendar entry, and a decision about whether anyone needs to be awake. Make that decision in October rather than in January.
Object dependency tracking changes how carefully you can make integration changes generally. If you have been reluctant to delete an old data action because nobody could say what used it, you can now answer that question in the UI.
What to check
- Inventory every Salesforce data action integration and migrate any using the legacy credential type before October 7.
- Confirm which Sunday in January 2027 your region's ASN maintenance falls on and brief anyone staffing that window.
- Enable SIP digest authentication on BYOC Cloud inbound trunks if your carrier supports it.
- Use object dependency tracking to find the flows depending on each integration you plan to touch.
- Separate Virtual Supervisor evaluations from manual ones in your quality reporting before reading the trends.
- Adjust the Embeddable Framework deallocation period if agents are working from a cluttered roster.
- Rerun any year-to-date performance export you previously had to split by date range.
Full details are in the official Genesys Cloud release notes for October 5, 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.