Three items. That's the whole week, and two of the three are confined to outbound. Light weeks happen, usually after a heavy one, and the August 31 release was heavy.
Don't let the short list fool you on the retention item though. It's the only thing in these notes that can destroy data.
TL;DR
- Outbound contact lists and individual contact records can now have retention periods, after which Genesys Cloud deletes them automatically.
- Campaign managers can ask for AI-generated summaries and diagnostics of campaign configuration, runtime state, and blocking conditions in natural language.
- Digital Bot Connector is now called Digital Connector. Functionality is unchanged.
Outbound Campaigns and Dialer
Contact list and record retention is the item to read twice. Admins can configure a retention period at the list level and at the individual record level, and when that period expires Genesys Cloud removes the data. Genesys says lists and records actively in use by a campaign are protected.
This solves a real problem. Outbound contact lists accumulate, nobody owns the old ones, and eventually you're holding phone numbers you have no lawful basis to keep. Automating the expiry is the correct answer and plenty of compliance teams have been asking for it.
But it's a feature whose failure mode is permanent. "Actively in use by campaigns" is doing a lot of load-bearing work in that sentence, and I'd want to know exactly how the platform defines it before I set a retention period on a list that a seasonal campaign touches twice a year. Set this on a copy of a low-stakes list first, watch what happens at expiry, and only then apply it to anything that matters. If you have a recycle or suppression workflow that reads from an old list, trace it before you configure anything.
The AI campaign diagnostics are the friendlier item. You can ask in plain language why a campaign isn't dialing and get an explanation grounded in the actual configuration and runtime state, instead of opening six screens and a log viewer. Campaign troubleshooting is tedious work where the answer is usually one wrong setting, so a tool that reads all the settings at once and points at the wrong one is a fair use of an LLM.
I'd still verify what it tells you before acting on it. Evidence-backed is not the same as correct, and a confident wrong answer about why a campaign is blocked costs you more time than the manual check would have.
Connectors
Digital Bot Connector is now Digital Connector, reflecting that it handles more than bots these days. Existing functionality is untouched, so there's nothing to migrate.
There is something to update, which is every runbook, onboarding doc, and internal wiki page where you wrote the old name. The Architect action is now "Call Digital Connector action". Renames are cheap for the vendor and mildly expensive for everyone documenting the vendor. Search your docs once and be done with it.
What this means for your contact center
If you run outbound at any scale, retention is this week's only real decision. The right move is to define the policy before you touch the configuration: how long do you keep a contacted record, how long an uncontacted one, and who signs off on that. Setting a period in the UI because the field now exists is how you discover a dependency you forgot about.
The campaign diagnostics tool is worth putting in front of whoever currently gets the "why isn't this campaign running" message. If it shortens that loop even half the time, it pays for the five minutes of learning the prompt style.
The rename is a documentation chore and nothing more. Treat it as one.
What to check
- Write down your outbound data retention policy before configuring retention periods in the UI.
- Test retention expiry on a disposable copy of a contact list and confirm what survives.
- Trace any recycle, suppression, or reporting workflow that reads from older contact lists.
- Try the campaign diagnostics on a campaign you already understand, so you can judge its accuracy.
- Update internal documentation and runbooks that reference Digital Bot Connector by its old name.
Full details are in the official Genesys Cloud release notes for September 14, 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.