The June 29 release is bigger than it looks. Behind a couple of visible UI changes, Genesys is rewiring two foundational layers of the platform: how conversation data leaves Genesys Cloud, and how call sessions get managed inside it. Here's my read on the four items that matter this week.
TL;DR
- New Lakehouse Extraction API: near real-time, flattened conversation data as Parquet files with a rolling three-day lookback. If you feed Redshift or Snowflake today, this is the big one.
- The Call Session Service (CSS) rollout has started for eligible low-volume orgs. Core telephony change, nothing for you to configure.
- Supervisors can now watch an agent's desktop live during ACD interactions. Note this one slipped to July 2, 2026.
- Architect gets dark mode and a refreshed UI. Visual changes only.
Platform and Data
Lakehouse Extraction API for conversation data
If your reporting team has ever stitched together the Analytics API and nightly detail-record jobs to build a warehouse picture of your contact center, read this one twice. The new Lakehouse Extraction API continuously publishes updated Parquet files covering conversation, participant, session, segment, and metric data, flattened and ready to land in Amazon Redshift or Snowflake. A rolling three-day lookback window handles late-arriving updates, which has always been the ugliest part of incremental conversation extracts.
Genesys pitches this as the foundation of its broader data lakehouse strategy: one query-ready environment instead of a patchwork of purpose-specific APIs. I think that's the right direction. You'll need a CX 1–4 license, and Genesys is routing access through account teams, so expect an enablement conversation rather than a self-service toggle.
Call Session Service phased rollout
Genesys has started enabling the Call Session Service for eligible organizations with low call volumes. CSS is a core telephony service that handles call session management, and this is the first wave of customer traffic after internal validation. Nothing to configure, no action required. But if you run a small org, your voice traffic may be riding new infrastructure soon, and you won't get a ticket telling you so. Write the date down.
Workforce Engagement
Live screen monitoring for agent supervision
Supervisors can now view an agent's desktop live while the agent handles ACD interactions, alongside the existing voice and digital monitoring. You can start it from an active interaction (it ends when the agent leaves it) or from the agent's profile card, where it persists across interactions while the agent is on queue. It shows all of an agent's screens, requires Genesys Cloud Background Assistant (GCBA) 1.7.468 or later, and orgs can cap simultaneous monitoring sessions to manage bandwidth.
Two details matter. Agents are notified when monitoring starts and stops by default, and a roster indicator shows monitoring status. Admins can switch those notifications off org-wide. That's a policy decision, not a technical one, and I'd treat it like one. All monitoring activity is written to audit events, so usage is reportable. Also note the rollout for this feature slipped to July 2, 2026.
Self-Service and Automation
Dark mode and UI refresh for Architect
Architect gets an updated interface with a light/dark theme toggle. Genesys is explicit that this is a visual change only; flow behavior, features, and navigation are untouched. If you spend all day in the canvas, you'll like it. Everyone else can opt in whenever.
What this means for your contact center
The Lakehouse Extraction API is the strategic item here. If you maintain custom ETL against the Analytics APIs, start evaluating whether the lakehouse feed can replace part of that pipeline. Flattened Parquet with a defined lookback window means less code for retries and late-update reconciliation, which is where conversation ETL breaks most often. It's early, and access goes through your account team. But the direction is clear: Genesys wants warehouse integration to be a supported product surface, not something every customer rebuilds from scratch.
Live screen monitoring is useful and it's risky. Decide your policy on agent notifications before any supervisor gets the permission, and put it in writing. In some jurisdictions and union environments, silently watching desktops carries real compliance weight. Audit events cover usage, but assign someone to review them on a schedule.
CSS and the Architect refresh are lower stakes. Still, log the CSS rollout date. When a voice issue appears, knowing you were moved to a new session service last week is the difference between a five-minute triage and a day of guessing.
What to check
- Inventory your current conversation-data extracts, then ask your Genesys account team about Lakehouse Extraction API access and schema docs.
- Confirm your Redshift or Snowflake ingestion can handle incremental Parquet drops with a three-day lookback. Idempotent upserts, not blind appends.
- Draft a screen-monitoring policy: who gets the permission, whether agent notifications stay on, and who reviews the audit events.
- Verify GCBA is at 1.7.468 or later before enabling screen monitoring, and plan the upgrade if it isn't.
- If you run a small org, note the CSS rollout date in your change log in case voice behavior questions come up later.
- Try the new Architect UI and dark mode while the rollout is fresh, and report any rendering oddities.
Full details are in the official notes: Genesys Cloud Release Notes — June 29, 2026.
Questions about what this release means for your environment? Get in touch.