Gibson Technology Partners Blog

Genesys Cloud Release Notes — July 13, 2026

2026-07-13T00:00:00Z

Three changes stand out this week, and two of them are Genesys removing things: a billing meter and a tuning knob. Both removals are good news. Here's my read on the July 13, 2026 release notes.

TL;DR

Journey Management no longer charges for event overages. Ingestion is part of the base offering now; the per-agent event allotments and tiered overage fees are gone.
The transcription confidence threshold setting is going away. The default drops to 0 and the control disappears from Speech and Text Analytics settings, so every transcription segment is kept.
The Genesys TTS Connector is generally available on AppFoundry. You can plug third-party text-to-speech providers like Cartesia and ElevenLabs into Architect flows under the BYOT model.

Data, Analytics & Reporting

Journey Management: event overage charges removed

Until now, Journey Management billing came with an event budget tied to your seat counts (on the order of tens of thousands of events per agent per month), and blowing past those fair-usage thresholds triggered tiered overage charges. So someone on your team had to watch event volume and explain the surprise line item after a busy month.

That whole mechanism is gone. Event ingestion is now just included in the base Journey Management offering. No event-based fair usage limits, no overage billing. The one guardrail left is on the analysis side: query usage is still governed by the existing limits (Journey Analyzer has historically been capped at a set number of query analyses per day per org). This changes ingestion billing only; the analysis limits didn't move.

Transcription confidence threshold configuration removed

Speech and Text Analytics used to let you set a confidence threshold below which transcription segments got filtered out. Genesys is retiring that control: the default drops to 0 and the setting comes off the Speech and Text Analytics Settings page entirely.

The reasoning holds up. Transcription engines are accurate enough now that confidence filtering discards more signal than noise, so from here on every segment is preserved regardless of score. You get fuller transcripts. You also lose a subtle failure mode where sentiment analysis and topic spotting silently missed content because someone set a threshold years ago and forgot about it.

Open Platform

Genesys TTS Connector general availability

The Genesys TTS Connector is now generally available and installable straight from AppFoundry. It's a vendor-agnostic bridge: if you already pay for a supported third-party text-to-speech provider (Cartesia and ElevenLabs are the named examples), you can wire that voice into your Architect flows instead of settling for the natively integrated engines.

It follows the Bring Your Own Technology model and bills at the BYOT-A rate. You pay Genesys a platform rate; your provider contract and its pricing stay your own. Two caveats from the product docs: you have to configure both the Genesys side and the provider side, and the connector is not PCI-compliant. No connector-driven TTS in secure flows, full stop.

What this means for your contact center

The Journey Management change is the sleeper here. Event-based pricing was an adoption blocker, plain and simple: teams instrumented fewer touchpoints than they wanted because every event carried a marginal cost and somebody had to babysit the meter. With ingestion included, go back and look at what you didn't instrument, whether that's web events you skipped or custom milestones you trimmed to stay under the allotment, because the reason you held back no longer exists. Query limits still apply, though. Heavier instrumentation doesn't buy you unlimited analysis.

The transcription change is low-drama for most orgs. It matters if you ever customized the threshold. If you deliberately set a high confidence bar to keep noisy transcripts out of downstream tooling, that filter is gone, and any process that consumed transcripts assuming low-confidence segments were pre-filtered will now see them. Expect transcripts to run a little longer and occasionally messier.

The TTS Connector GA is the most strategically interesting of the three. The synthetic voice market moves much faster than any platform's native offerings, and a vendor-agnostic connector lets you swap providers as quality improves without rebuilding flows. I like it. But model the BYOT-A rate plus your provider's per-character pricing against native Genesys TTS before you commit, and remember the PCI limitation: secure flows stay on native engines.

What to check

Confirm the Journey Management billing change is reflected on your account, retire any event-volume monitoring or alerting you built to dodge overages, and revisit instrumentation plans you scoped down.
Check whether your org had a non-default transcription confidence threshold, and warn downstream consumers of transcripts (QA tooling, BI pipelines) that low-confidence segments will start appearing.
Evaluate the Genesys TTS Connector on AppFoundry if you've wanted a specific third-party voice, and verify none of the target flows are secure flows, since the connector isn't PCI-compliant.
Compare BYOT-A billing plus your third-party TTS provider's costs against your current native TTS spend before rolling the connector out broadly.

Full details are in the official Genesys Cloud release notes for July 13, 2026. Questions about how any of this lands in your environment? Email me.

Genesys Cloud Release Notes — July 6, 2026

2026-07-06T00:00:00Z

Three changes in this week's release are worth your time. Bot flows can finally call other bot flows. In-queue flows get an error-recovery option that should have existed from day one. And Quality Management forms are now division-aware, which will quietly change who sees which forms in multi-division orgs.

TL;DR

Bot flows can now call other bot flows (voice-to-voice, digital-to-digital). Modular bot design and parallel development across teams are finally on the table.
In-Queue Message and Email flows can transfer to another queue on error, instead of being limited to ending the state or the whole flow.
Evaluation and survey forms are now division-aware. Users only see and edit forms in their assigned divisions, and some workflows now prompt for a division.

Self-Service and Automation

Bot flows calling bot flows

Architect now lets a bot flow invoke another bot flow, and a digital bot flow invoke another digital bot flow, via new Call Bot Flow and Call Digital Bot Flow actions. The pairing is strict: voice calls voice, digital calls digital. Within that constraint, you can finally split a monolithic bot into smaller flows that different teams own and publish on their own schedule.

Know the boundaries before you refactor everything:

NLU is scoped per flow. A called bot doesn't inherit the caller's intents, slots, or knowledge configuration, so shared understanding has to be designed on purpose.
The whole chain runs inside one session, and the usual session ceilings still apply (200 turns per session, per-turn action limits). Recursive task invocation is capped at five iterations.
Subflows can inherit the core flow's language when configured for it, and the core flow's voice processing settings apply across the session.

The action configuration covers naming, target flow selection, and variable passing. So you can hand context into a subflow and get results back, which is everything you need for a hub-and-spoke bot architecture. Licensing spans CX 1 through CX 4 and the AI Experience tiers.

Transfer to queue from the In-Queue Flow Error event

In-Queue Message and In-Queue Email flows used to give you two options when the Flow Error event fired: end the state or end the flow. Now there's a third: transfer the interaction to another queue. An error in your in-queue logic no longer strands a digital interaction. You can shunt it to a fallback queue where a human picks it up.

One catch. If the target queue is invalid at runtime (deleted, misconfigured), the transfer doesn't happen and the system falls back to End State handling. A broken queue reference fails silently into the old behavior. Nobody gets alerted. Requires Communicate or CX 1–3 licensing.

Workforce Engagement

Evaluation and survey forms become division-aware

Quality Management evaluation and survey forms can now be managed by division. Users see and modify only the forms in divisions they're assigned to, and workflows that reference forms (voice survey flows, for example) now surface a division badge and may require selecting a division when you pick a form.

On the flow side: selecting a form auto-populates its division into the flow's division list, and Architect warns you when the flow's division doesn't match the form's, or when a form has no division assigned but the flow does. Access to published survey forms in flows requires the Quality > Survey Form > View permission. Licensing: CX 2/3 or the CX 1/CX 2 WEM add-ons.

What This Means for Your Contact Center

The bot-to-bot calling change is the strategic one, and it's overdue. Until now, a large bot estate meant picking your poison: one sprawling flow that everyone edits, with the merge pain and risky publishes that come with it, or duplicated logic across many bots that drift apart over time. Composable flows let you build a router bot that hands off to specialist bots, say a billing bot and an orders bot, each owned by its own team and released on its own cadence. Respect the per-flow NLU scoping when you design this. Your entry bot needs enough understanding to route correctly, because the specialist bot's intents won't help it.

The in-queue error transfer is smaller, but I like it. Digital interactions sitting in queue belong to customers who have already waited, and losing one to a flow error is the worst failure mode there is. A fallback queue staffed by generalists turns a silent drop into a handoff someone can recover. But watch that invalid-queue fallback. Delete the target queue six months from now and error handling quietly reverts to End State. Put those queue references on your change-management checklist.

Division awareness for forms is the one most likely to surprise people. If your org runs a flat division model, nothing changes. But in a multi-division org, quality analysts may suddenly lose sight of forms they used yesterday, because those forms live in a division they aren't assigned to. Audit before your evaluators notice.

What to Check

Inventory your largest bot flows and find the natural seams for splitting into called subflows. Plan NLU coverage for the router flow explicitly.
Confirm variable handoff needs between prospective caller/callee bots before committing to a decomposition.
Add a Transfer to Queue action to the Flow Error event in your In-Queue Message and Email flows, pointed at a monitored fallback queue.
Document that fallback queue as a protected dependency, because deleting it silently reverts error handling to End State.
Review division assignments on all evaluation and survey forms, and verify evaluators and survey flow authors hold membership in the right divisions.
Check that flow authors have Quality > Survey Form > View where voice survey flows reference published forms.

Full details are in the official Genesys Cloud release notes for July 6, 2026. Questions about how any of this lands in your deployment? Email me.

Genesys Cloud Release Notes — June 29, 2026

2026-06-29T00:00:00Z

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.

Genesys Cloud Release Notes — June 22, 2026

2026-06-22T00:00:00Z

Good week for the people running the floor. Supervisors get a real intervention tool for messaging, and agents get to decide when AI summaries happen instead of waiting for the system. Outbound admins pick up three new Campaign Health signals too. Here's what I think matters.

TL;DR

Supervisors can now remove an agent from an active messaging conversation and continue with the customer directly. It's gated behind a new permission, so nothing happens until you assign it.
Agent Copilot can generate an interaction summary on demand, mid-conversation, and the agent can edit the result.
The Campaign Health view adds recycle events, compliance abandon rate, and calls per agent for voice campaigns.
Social listening gains automatic explicit-image masking, and Analytics dashboards get a visual refresh with redesigned pagination.

Agent Experience

Supervisor takeover for messaging conversations. Until now, a supervisor watching a messaging interaction go sideways could coach the agent or barge in alongside them. That was it. This release adds a real takeover: a supervisor with the new permission can remove the agent from an active messaging conversation entirely and continue with the customer themselves. The permission is new, so nobody has it until an admin hands it out. Requires CX 1, 2, 2 Digital, 3, 3 Digital, or 4 (Add-on II).

On-demand summaries in Agent Copilot. Agents can now trigger an AI summary of an active interaction with a button press instead of waiting for the automatic end-of-interaction summary. The summary lands in an editable text box, so the agent can fix it while the conversation is still fresh, and it persists after the interaction ends. Two gotchas. Genesys allows one summary per interaction, so generating one on demand means the automatic end-of-call summary is skipped. And on transfers, the summary carries over to the next segment but the agent's edits to it do not. Also check your summary retention window (configurable from 1 hour to 10 days) against your after-call work timeout; if ACW outlasts retention, edits stop being saved.

Outbound

Campaign Health view enhancements. Voice campaign admins get three new data points in the Campaign Health view: recycle events, compliance abandon rate, and calls per agent. These are the numbers you reach for when a campaign is pacing strangely. Is the dialer abandoning above your regulatory threshold? Are agents saturated or starved? Until now you stitched that together from exports. Small change, real value.

Customer Engagement

Explicit-image detection and masking in social listening. Organizations doing social listening can now enable automatic detection of explicit or suggestive images in ingested posts. Flagged images are replaced with a placeholder in the Social Listening Performance and Posts views, users with the right permission can review and unmask them, and flagged posts are not escalated to the agent desktop at all. If your brand monitors public social channels, I'd turn this on. It's an agent-wellbeing and HR-risk control that used to require manual moderation.

Analytics

Dashboard and Performance view refresh. Analytics dashboards and Performance views get updated styling, redesigned pagination controls, refreshed empty states, and updated modals, menus, and widget displays. No data changes, purely cosmetic. But supervisors who live in these views will notice, and any internal training screenshots or documentation you maintain are now out of date.

What this means for your contact center

Think hard about supervisor takeover before you enable it. Yes, sometimes a conversation needs a supervisor to step in, on a regulatory complaint or an escalating customer. But pulling an agent out of a live conversation is a blunt instrument, and your agents will have opinions about how it gets used. Decide who gets the permission, define when takeover is appropriate versus coaching or conferencing, and write that down before anyone uses it in anger. The permission is brand new, so nothing changes until you act. Set policy first.

The on-demand summaries are the quieter win, and probably the bigger time-saver in aggregate. An agent who summarizes during a lull arrives at wrap-up with the work already done. The catch is the one-summary rule: summarize early in a long interaction and you skip the automatic summary that would have covered the whole thing. Brief your agents on when to press the button.

On the outbound side, compliance monitoring gets more immediate. If you operate under abandon-rate regulations (TSR, Ofcom, ACMA), the compliance abandon rate now sits in the same view you use to watch pacing. Check it against whatever external tracking you've built. You might get to retire some of it.

What to check

Decide your policy for messaging takeover, then assign the new supervisor permission only to the roles that policy names.
Enable on-demand summaries in Agent Copilot settings if summarization is already on, and brief agents on the one-summary-per-interaction behavior.
Verify your Copilot summary retention period is at least as long as your after-call work timeout, or edited summaries won't be saved.
Review the new Campaign Health metrics against your current outbound compliance reporting for any discrepancies.
If you use social listening, evaluate turning on explicit-image masking and decide who gets unmask permission.
Update any internal documentation or training material that screenshots Analytics dashboards or Performance views.

Full details in the official Genesys Cloud release notes for June 22, 2026. Questions about how any of this lands in your deployment? Email me.

Genesys Cloud Release Notes — June 15, 2026

2026-06-15T00:00:00Z

Two things in the June 15 release are worth your time: an overdue security control for server-side integrations, and a smarter way to build topics in Speech and Text Analytics.

TL;DR

You can now restrict OAuth client credential grants by IP range. If a client ID and secret leak, token requests from outside your allowed CIDRs get denied. If you run backend integrations, turn this on.
Speech and Text Analytics gets semantic topic spotting. Instead of enumerating every phrasing of "I want to cancel," you let semantic matching catch the intent. English only for now.
Both are opt-in, so nothing breaks on day one. Schedule them anyway.

Identity & Access Management

Restrict OAuth client credential grants by IP address range

Client credentials grants are the workhorse of Genesys Cloud integrations: middleware, scheduled jobs, anything that authenticates as an application rather than a user. They're also a standing risk. A leaked client ID and secret is a bearer of whatever roles you attached to it, usable from anywhere on the internet.

This release closes that gap. When you create or edit a client credentials OAuth client, you can now list allowed IP addresses as CIDR ranges, one range per line, in the grant configuration alongside role assignment. Token requests from outside those ranges get rejected. The stolen secret does an attacker no good unless they're also inside your egress range.

This should have shipped years ago. But it's here, and it's included in all license tiers, so there's no commercial excuse to skip it. You'll need the usual OAuth client admin permissions to make the change. And while you're in there: role assignments on client credentials grants default to the Home Division, so re-check that each client's roles and divisions still follow least privilege.

Speech and Text Analytics

Semantic topic spotting for topic configuration

Topic spotting has always been lexical. You define a topic, feed it phrase variations, and detection depends on the transcript containing something close to one of them. Anyone who's maintained a "cancellation" topic knows how that goes. Dozens of phrasings, and it still misses.

The new semantic method matches on meaning instead. "I'd like to close my account" and "stop my subscription" land in the same topic without you having authored both. Genesys says it also improves detection across English dialects, which matters if your queues span US, UK, and APAC English speakers.

Before you rebuild your topic library:

English only at launch. Multilingual programs keep using lexical topics for other languages.
Semantic topics take up to 20 phrases each, fewer than lexical topics allow, because the phrases are seed examples rather than an exhaustive match list.
Confidence scoring works the same as lexical topics (0–100 during matching), and semantic is a per-topic choice in the configuration workflow, so you can migrate one topic at a time.
Licensing isn't universal: you need a WEM add-on (CX 1 WEM Add-on II or CX 2 WEM Add-on I), CX 3 / CX 3 Digital, or CX AI Experience.

What this means for your contact center

Move on the OAuth change first. Credential leakage from CI logs or a departing contractor's laptop is one of the most common real-world compromise paths, and IP restriction turns that from an incident into a denied token request. The catch is operational: you have to know the actual egress IPs of everything using each grant, and anything running with dynamic egress (serverless, autoscaling NAT pools) needs a stable egress IP or a deliberately wider range before you can lock it down. Do the inventory before you flip anything. Change one client at a time.

Semantic topic spotting is a quality-of-results play. Most teams have underinvested in phrase lists, and those teams should see better recall on intent-style topics with far less curation. I'd pilot it on two or three high-value, intent-shaped topics like cancellation or competitor mention, compare hit rates against the existing lexical versions, and only then convert anything wholesale. Keep lexical topics for compliance phrases such as mandated disclosures; there you want the exact words matched, so don't migrate those.

What to check

Inventory your client credentials OAuth clients and map each to the systems and egress IPs that use it.
Add allowed CIDR ranges to your highest-privilege grants first; watch for denied token requests after each change.
Confirm integrations with dynamic egress IPs have a stable NAT or proxy before restricting them.
Re-review roles and division scoping on each grant while you're editing it.
Verify your license tier includes Speech and Text Analytics topic features before planning semantic topics.
Pilot semantic spotting on two or three intent-heavy English topics and compare detection against the lexical equivalents.
Keep exact-phrase lexical topics for compliance and disclosure monitoring.

Full details are in the official release notes: Genesys Cloud Release Notes — June 15, 2026.

Questions about rolling any of this out in your org? Email me and I'll help you sort it out.

Genesys Cloud Release Notes — June 8, 2026

2026-06-08T00:00:00Z

June 8 is a good week if you own workforce management in Genesys Cloud. All three changes I'm covering land in WFM or agent self-service.

TL;DR

Agents can now view, rank, and submit preferences for complete schedule sets during a bidding window. A real upgrade over queue-style shift bidding.
Manual schedule edits now sync back to Activity Plan occurrences, so the schedule editor and the plan view stop drifting apart.
Tempo shows blocked days and manual-approval days during time-off requests, and stops blackout-date submissions before they ever hit a supervisor's queue.

Workforce Engagement: Scheduling

Schedule set bidding

Administrators can now open a bidding window where agents browse full schedule sets, rank them in order of preference, and submit their choices. Once bids are processed, each agent's schedule follows their assigned set's pattern until the next bidding cycle.

This is the more interesting of the two scheduling changes. Genesys Cloud's bidding model already differed from traditional queue-based bids: every agent submits preferences at the same time instead of waiting for a turn in a seniority queue, and the system resolves assignments using hire date or performance ranking against available slot capacity. Extending that from individual work plans to complete schedule sets means agents pick a coherent, repeating pattern of shifts instead of piecing together one-off selections. The platform also analyzes the bid configuration and suggests how many agents each option should get, which takes a lot of the spreadsheet math out of running a bid.

Agents get more say and more visibility into how shifts are allocated. Planners get a repeatable process instead of a manual allocation exercise every cycle. One thing to watch: schedule bids and bid groups have their own WFM permissions (add, edit, publish, view, delete). Grant those deliberately. Don't assume your existing work plan bid permissions cover it.

Sync manual schedule edits with Activity Plan occurrences

Until now, Activity Plans and the schedule editor lived in an awkward relationship. Activity Plans generate sessions like training and coaching into interruptible time on published schedules. But if a scheduler manually edited one of those sessions in the schedule editor, the Activity Plan occurrence kept showing the original version. The two views disagreed, and anyone auditing plan compliance had to reconcile them by hand. That's a pain, and it's been one for a while.

With this release, administrators can turn on automatic synchronization: manually editing a session that came from an Activity Plan updates the corresponding occurrence to match. The occurrence view becomes a trustworthy record of what's on the schedule, not just what the plan intended.

Quality-of-life change, but a real one if you run recurring coaching or training programs at scale. Fewer arguments about why the plan says Tuesday 2pm and the schedule says 3pm.

Employee Productivity: Tempo Mobile App

Blocked days and manual approval days in time-off requests

Agents requesting time off in the Tempo mobile app now see which days are blocked and which need manual administrator approval before they submit. Tempo stops submissions on blocked days outright, and flags requests that include approval-required days so agents know not to expect an instant answer.

Small feature, big effect on request hygiene. Most blackout periods (peak season, all-hands days) get enforced today by rejecting requests after the fact, which wastes agent goodwill and supervisor time. Showing the rules at the point of request means fewer doomed submissions and fewer awkward denials. This one spans essentially the full license range, including Genesys Cloud EX.

What this means for your contact center

The through-line this week is transparency between planners and agents. Schedule set bidding and Tempo's blocked-day visibility both take information that used to live only in the WFM team's head, or in a policy document nobody reads, and put it in the agent's workflow. Agents argue less about shift allocation when they can see the process instead of just the outcome.

If you administer WFM, pilot schedule set bidding on one business unit before a broad rollout. Bidding changes how agents think about their schedules, and the first cycle will surface configuration surprises around ranking criteria and slot capacity per set. Decide up front whether hire date or performance ranking drives assignment priority. Agents will see that choice, and it's hard to walk back quietly.

The Activity Plan sync is lower stakes. But check whether your team built manual reconciliation habits or reports around the old divergent behavior. If someone exports occurrence data to audit training completion, the numbers may shift once manual edits start flowing back into occurrences. More accurate numbers, but different ones.

What to check

Review the new schedule bid and bid group permissions in your WFM roles before opening a first bidding window. Hold publish rights tightly.
Pilot schedule set bidding with one planning group, and write down your ranking criteria (hire date vs. performance) before agents ask.
Enable Activity Plan sync in a test business unit and confirm occurrence reports still line up with your compliance tracking.
Configure blocked days and manual-approval days for your time-off policies. Tempo can only show agents the rules you maintain.
Tell agents about the Tempo change: requests on blackout days now get stopped at submission instead of denied later.

Full details are in the official notes: Genesys Cloud Release Notes — June 8, 2026.

Questions about rolling any of this out, or want help planning your first schedule bid cycle? Email me.

Genesys Cloud Release Notes — June 1, 2026

2026-06-01T00:00:00Z

Two things worth your time in the June 1, 2026 release: Journey Management can finally import Architect flows, and WFM got a smarter way to chew through time-off requests. Both cut busywork rather than adding new surface area to learn.

TL;DR

Journey Management now imports published Architect flows directly and renders them as Sankey diagrams. No more rebuilding flows by hand on the journey canvas.
WFM supervisors can filter and sort time-off requests by criteria like hire date and performance, and run a sequential auto-approval pass that pauses when a request needs a human decision.
Adoption cost is low for both. If you already use Journey Management or WFM time-off plans, these slot right in.

Journey Analytics

Import Architect flows into Journey Management

Until now, analyzing a single IVR or bot flow in Journey Management meant recreating its structure on the journey canvas by hand. Tedious, error-prone, and enough of a chore that most people skipped flow-level analysis entirely. This release fixes that: you can pull a published Architect flow into Journey Management directly.

The workflow: from the journey canvas, choose Import Flow, pick a published flow, and review it in the Journey Flows Sankey view. Select the nodes you want to analyze, pick the outcomes and milestones you care about, and add them to the journey. Save and calculate, and the flow's real traffic patterns become part of your journey analysis.

This is the feature I'd try first. If you've ever wanted to know where callers bail out of a specific menu, or which branch of a bot flow correlates with escalations, you can get there in minutes now instead of burning an afternoon on canvas work. One catch: the import only works against published flows. Drafts don't count.

Workforce Engagement

Time-off request filtering, sorting, and sequential approval

The second update goes after one of the least glamorous supervisor chores there is: the pending time-off queue. Two things changed.

Filtering and sorting got deeper. On top of the existing agent, date-range, status, and activity-code filters, supervisors can now order requests by criteria such as hire date and performance, and stack up to three sort categories at once. If your time-off policy awards priority by seniority or scorecard results, the request list can finally match the policy instead of arrival order. Overdue.

There's also a sequential evaluation run for requests flagged for manual review. Kick it off and Genesys Cloud walks the list in your chosen sort order, auto-approving each request against the time-off plan rules and showing progress as it goes, until it hits a request it can't approve on its own (a coverage limit, say, or a plan rule violation). Then it pauses with an action-required prompt. You resolve or skip that request and the run continues. You can also mark items to be skipped automatically in future runs, and export the results to CSV when it finishes.

What this means for your contact center

The Journey Management import is the bigger deal. Genesys has been positioning Journey Management as the analytical layer over everything customers touch, and flow import removes the main reason people weren't using it on self-service. If your org licenses Journey Management but usage stalled because setup felt heavy, revisit it now. It's the right tool for the IVR containment and bot-abandonment questions Architect reporting can't answer on its own.

Watch your scope, though. An imported flow gives you that flow's structure, and you still have to choose outcomes and milestones that mean something. Import everything and select every node and you'll produce a Sankey diagram nobody can read.

On the WFM side, sequential approval turns the supervisor's job from processing requests one by one into handling exceptions. That's a real workload cut. But the automation is only as good as the limits and policies it evaluates against, and if your time-off plans have loose or outdated rules, the run will either rubber-stamp requests it shouldn't or pause constantly. Tighten the rules first, then turn on the automation.

What to check

Import one high-traffic, published Architect flow into Journey Management and validate the Sankey view against what Architect's own metrics tell you.
Confirm the flows you want analyzed are published. Unpublished work isn't importable.
Review your time-off plan rules and coverage limits before relying on sequential auto-approval. The run enforces exactly what's configured, nothing more.
Decide your sort policy (seniority, performance, submission date) up front, since the evaluation run processes requests in that order.
Check role permissions. Journey creation requires Creator/Editor roles, and time-off evaluation is gated by WFM admin permissions.

Full details are in the official notes: Genesys Cloud Release Notes — June 1, 2026.

Questions about how these changes affect your environment? Email me.

Genesys Cloud Release Notes — May 25, 2026

2026-05-25T00:00:00Z

Big week for routing architects. Also a deadline week for anyone still running OAuth Implicit Grant clients. Here's what I think matters.

TL;DR

ACD skill expression filters let you attach a logical skill expression to a single interaction, evaluated at assignment time, instead of spinning up yet another queue.
Email header fields are now readable in the API, Architect, and Scripter. Header-based routing is finally possible.
The Token Implicit Grant is deprecated. New OAuth clients can't use it as of this release, and existing clients stop working on May 24, 2027. Start moving to Authorization Code with PKCE now.
Email alert notifications now show queue and agent names, not just IDs. Small change, real quality-of-life win.

Routing

Support for ACD skill expression filters. Until now, "this interaction needs Spanish at proficiency 4 AND the billing skill" usually meant a dedicated queue, or skill combinations that bloat your routing design. Skill expression filters fix that. You define a logical expression combining ACD skills, language skills, and proficiency levels, and you apply it to an individual interaction. The system evaluates it when it picks an agent, and you can set or update it from Architect flows or the public API, even while the interaction is already sitting in queue.

Two details matter here. It works with predictive routing (GPR) as well as standard routing, so GPR shops aren't left out. And the filter lives at the interaction level, so queue configuration stays untouched and you can pilot it on a slice of traffic without reworking anything. If your org carries dozens of near-duplicate queues that exist only to encode skill combinations, this is the consolidation tool. Overdue, in my view.

Email

Access to email header fields. Genesys Cloud now surfaces standard and custom email headers where you can use them: Architect gets a Get Email Headers action, Scripter can reference header data, and the API exposes the fields directly. So you can route on a ticketing system's correlation header, or detect auto-reply and loop-prevention headers before they reach an agent. If you integrate email with external systems, this closes a long-standing gap. Header context used to be stripped away before your flow could see it, and that was a pain. About time.

Analytics and Reporting

Email alerts now include queue and agent names. Alert emails used to identify queues and agents by GUID only, which meant logging in (or keeping a lookup table handy) just to know what fired. Notifications now carry the queue or agent name alongside the ID, depending on alert type. Trivial on paper, annoying in practice, and now fixed.

Deprecations

Token Implicit Grant for OAuth clients. Put this one on your calendar. Genesys announced the deprecation on March 2, 2026, and as of this release you can't create new OAuth clients using the Implicit Grant (Browser) type. Existing clients keep working through a one-year window, with full removal on May 24, 2027. That includes Embeddable Framework applications, which historically leaned on Implicit Grant for browser-based login.

The replacement is the Authorization Code grant with PKCE, which Genesys Cloud already supports, including in embedded clients as of this same release cycle. PKCE keeps tokens out of URL fragments and blocks authorization-code interception. The OAuth 2.0 security best practices deprecated the implicit flow industry-wide for exactly those reasons, so none of this should surprise anyone.

What this means for your contact center

The skill expression filter is the strategic item. Queue sprawl is endemic in mature Genesys Cloud orgs: dozens of queues whose only job is to encode "skill A plus skill B at level X." Interaction-level expressions let you collapse those into fewer queues with dynamic filtering, which simplifies reporting and agent membership management. But do a deliberate design review instead of adopting this ad hoc. Decide where expressions replace queues and where queues still earn their keep, like distinct SLAs or separate reporting lines.

The OAuth deprecation is the urgent item. A year sounds generous. It isn't. Inventorying every integration and embedded client that authenticates with Implicit Grant takes longer than you'd expect, especially the ones built by vendors or contractors who are long gone. Anything you miss stops authenticating in May 2027, and that failure looks like agents suddenly locked out of an embedded CRM client.

Email headers are the quiet win. If you've built workarounds like subject-line tokens or SMTP relays that copy headers into the body, you can retire them now.

What to check

List every OAuth client in Admin > Integrations > OAuth and flag anything using Implicit Grant. Build the PKCE migration plan well before May 24, 2027.
Test PKCE-based login in a sandbox if you use the Embeddable Framework, since embedded clients now support it.
Go through your queue estate for queues that only exist to encode skill combinations, and pilot expression filters on one interaction type first.
Confirm how expression filters interact with your predictive routing benefit measurement if you're on GPR.
Look at email flows for header-based routing. Auto-reply detection and external-system correlation are the quick wins.
Update any alert-handling runbooks or mail rules that parse notification emails, since the content now includes names alongside IDs.

Full details are in the official Genesys Cloud release notes for May 25, 2026. Questions about how any of this hits your deployment? Email me. I read these notes closely so you don't have to.

Genesys Cloud Release Notes — May 18, 2026

2026-05-18T00:00:00Z

A practical batch this week. Session timeouts get group-level control, campaigns synced from Salesforce stop drifting out of order, and Agentic Virtual Agents become debuggable without filing a support ticket. The one I'd look at first is the timeout change.

TL;DR

Inactivity timeouts can now differ by user group. You're no longer stuck choosing between one org-wide policy and none at all, and you can pilot the setting on a single team first.
Salesforce CX Connector campaigns get dynamic sorting, so contact lists keep their configured order (by date, for example) as new campaign members sync in.
Queues can carry more than one from email address, so agents pick the right sender identity when composing outbound email on behalf of a queue.
AVA execution history is available via public API, exposing data action inputs and outputs, guardrail decisions, and knowledge query details for troubleshooting.

Identity & Access Management

Group-based inactivity timeout. Until now, the automatic inactivity timeout was an all-or-nothing organization setting. Now you can attach timeout values to individual user groups, arranged in priority-ordered bundles (up to 5 bundles covering up to 25 groups). When a user belongs to multiple bundles, the highest-priority bundle wins, and group rules override the org-wide value for their members. Timeouts range from 5 minutes to 8 hours, with HIPAA orgs capped at 15 minutes. This is overdue.

The win is phased rollout. Trial the timeout on a back-office team before you touch agents, or give supervisors a longer leash than shared-workstation users. Two caveats carry over from the underlying feature: refresh tokens are not issued while the timeout is enabled, and agents logged out while On Queue come back Off Queue and have to re-queue themselves. I don't love that second one, and it will generate tickets if you don't brief people first. Genesys advises against it for orgs relying on the mobile apps.

Outbound & Email

Dynamic sorting for Salesforce CX Connector campaigns. Voice campaigns created from Campaign Management in the Salesforce CX Connector can now enable dynamic sorting. Before this, a contact list was effectively sorted once. Members added to the Salesforce campaign afterward landed out of order, and the fix was recreating the campaign, which is a pain. With dynamic sorting on, the list keeps following the configured sort criteria (date, say) as new members sync in. If you run always-on campaigns fed by Salesforce automation, this kills a recurring source of "why did we dial the old leads first?" tickets. Requires Genesys Cloud 1–4.

Multiple from email addresses per queue. Queues can now be configured with more than one from address. When a queue has several, agents composing outbound email on behalf of that queue choose which address to send from. If you've been running parallel queues purely to control sender identity for different brands or departments, you can stop. Check the licensing first: this sits in the digital tiers (Genesys Cloud 1 Digital Add-on II, 2/2 Digital, 3/3 Digital).

Self-Service & AI

View AVA execution history via public API. You can now pull Agentic Virtual Agent runs through the existing flow instance endpoints and get detailed runtime debug data: the inputs and outputs of each data action call, guardrail information, and the knowledge queries and responses the agent used. Genesys frames this as a stopgap for support teams and Professional Services until the Replay UI catches up. I'd treat it as more than that. Your own developers can finally answer "what did the agent see and decide?" programmatically, and you can log executions into your own observability stack. Requires Genesys Cloud 4 or AI Experience.

Folder visibility for knowledge fabric SharePoint sources. A small fix, but a good one. Admins can now see which SharePoint folders are selected inside a connected knowledge fabric source. Confirming what was being ingested used to mean guesswork or re-running the connection setup. Now you can just look, which helps when a bot starts pulling answers from a folder you didn't intend to connect.

What this means for your contact center

The inactivity timeout change is the sleeper here. The org-wide switch was too blunt for most enterprises. One policy for agents on shared desktops and executives on managed laptops rarely fits both. Group bundles with priority ordering make the control deployable, so treat it like any policy rollout: pick a pilot group, watch the On Queue logout side effect, and configure excluded APIs so background integrations don't keep sessions alive artificially.

The AVA execution history API shows where Genesys is heading with agentic AI: operability. If you're piloting Agentic Virtual Agents, start capturing execution history now. Guardrail and data action traces are exactly the evidence you'll need when a stakeholder asks why the agent said what it said.

The Salesforce dynamic sorting and multi-address queue items are unglamorous fixes that remove standing workarounds. If your runbooks say "recreate the campaign to fix ordering" or "use queue B for brand B email," retire those pages this week.

What to check

Review your current org-wide inactivity timeout (Admin > Organization Settings) and decide whether group-level values fit better. Plan a pilot bundle and brief agents on the On Queue logout behavior.
If HIPAA applies to your org, confirm the 15-minute cap aligns with your group rules before rollout.
Enable dynamic sorting on Salesforce CX Connector campaigns that receive members after creation, and verify the sort criteria match your dialing priority.
Audit queues that send outbound email for multiple brands or departments. Consolidate wherever multiple from addresses now cover the need.
Have developers exercise the flow instance APIs against a test AVA session and decide what execution history you want to retain for troubleshooting and audit.
Open your knowledge fabric SharePoint sources and confirm the selected folders match what you want the bot ingesting.

Full details are in the official notes: Genesys Cloud Release Notes — May 18, 2026.

Questions about how these changes affect your environment? Email me.

Genesys Cloud Release Notes — May 11, 2026

2026-05-11T00:00:00Z

This week's digest covers one item from the May 11, 2026 release notes. It gets a post to itself because it comes with a hard date and a migration project attached.

TL;DR

Genesys Cloud announced the deprecation of the Generic Webhooks integration used for chat notifications.
June 1, 2026 is the first hard date: after that, you can no longer install new instances of the integration.
Existing instances keep working for now, but they will stop functioning at a future end-of-life date and eventually get removed from your org entirely.
The replacement is the Webhooks for Events integration plus Architect workflows that are triggered to send the notification.

Deprecations

Generic Webhooks integration for chat notification is going away

Some history first. Genesys Cloud used to offer a family of chat-notification webhook integrations aimed at specific third-party tools: Bitbucket, GitHub, Jenkins, JIRA, PagerDuty, Pivotal Tracker, StatusPage, Trello, UserVoice, and Zendesk. Those were already retired in an earlier round of deprecations. What survived was the catch-all, the Generic Webhooks integration, which plenty of orgs quietly lean on to push chat notifications into internal tooling and home-grown alerting.

That last survivor is now on the clock. The May 11 announcement says support for Generic Webhooks ends in a future release, and the phase-out follows the usual Genesys pattern:

June 1, 2026: administrators can no longer install new instances of the integration. Existing deployments keep running.
A future end-of-life date, not yet announced: existing instances stop working.
Eventually, Genesys removes the integration objects from your organization altogether.

The prescribed migration path is to move chat notifications onto the Webhooks for Events integration and drive them from workflows: you build a workflow that fires on the relevant trigger and sends the notification payload out through the new integration. The deprecation article points to the "About webhook for events" documentation and the Webhooks overview in the Developer Center. What it doesn't include is a step-by-step conversion guide. The plumbing is on you, or your account team.

What this means for your contact center

The trap is the gap between the two dates. Existing instances keep working after June 1, so it's tempting to file this under "later." Don't. Once the install freeze hits, you can't stand up a fresh Generic Webhooks instance in a sandbox to test against, and you can't rebuild one that gets deleted by accident. Three weeks is not a lot of runway for something your alerting depends on. I don't love that Genesys gave us exactly one month here.

The second problem is discoverability. A generic webhook is usually something somebody wired up years ago to ping a channel when a chat queue backs up, and nobody has touched it since. It works, so it's invisible. When the end-of-life date lands, the notifications just stop, and no customer ever sees an error. Your team stops getting pinged, quietly. Treat that failure mode with more urgency than the "future release" language suggests.

Credit where it's due: the replacement architecture is better. Webhooks for Events plus workflows gives you a real logic layer between the event and the outbound call. You can filter which events fire, enrich or reshape the payload, and branch by queue or priority, and one integration can serve several notification targets. If you migrate deliberately, you'll probably end up folding a handful of crusty one-off webhooks into one or two workflows you can maintain. Budget it as a small integration project (inventory, rebuild, parallel-run, cut over), not a config toggle.

What to check

List every Generic Webhooks instance in Admin > Integrations, in every org you own, production and sandbox included. Note what each one notifies and who depends on it.
Install any new instance you'll need for testing or a parallel environment before June 1, 2026. After that the door is closed.
Stand up Webhooks for Events and prototype one workflow-triggered notification end to end before you touch production.
Rebuild each legacy webhook as a triggered workflow that sends the equivalent notification through Webhooks for Events, and run it beside the old instance until you trust it.
Watch the release notes (or this blog) for the end-of-life date. It hasn't been announced yet, and you don't want it landing mid-quarter.
Ask for help if the payloads are gnarly. Genesys directs migration questions to your account team or the My Support portal; complex payload transformations may need workflow-level data actions.

Full details are in the official notes: Genesys Cloud Release Notes — May 11, 2026.

Running Generic Webhooks and not sure how many you have or where? Email me. A webhook inventory and migration plan is a quick engagement, and it's better to do it now than in a rush after the freeze.

Genesys Cloud Release Notes — May 4, 2026

2026-05-04T00:00:00Z

This week is all self-service. Two changes landed in the Virtual Agent (Bots & IVR) area, both small, both chipping away at the same problem: voicebots and digital bots failing in ways that frustrate customers and are hard for builders to control.

TL;DR

Genesys' own native speech-to-text (STT) is now selectable as a bot transcription engine in Architect, alongside the Google-, Azure-, and AWS-backed "Genesys Enhanced" options.
Native STT launches with en-US, es-US, en-GB, and en-AU dialects, and it's the same engine Genesys already uses for post-call transcription.
Ask for Slot actions now support a configurable skip path, so a customer who doesn't have the requested information can move past the question instead of stalling the flow.
Skip works with every slot type, including AI-powered slots, and with quick replies, carousels, and list pickers.

Self-Service and Automation

Native speech-to-text as a bot transcription engine

Until now, every transcription engine behind Genesys Dialog Engine Bot Flows was a third-party service wearing Genesys branding. Genesys Enhanced v1 is Google Cloud Speech-to-Text, v2 is Azure Cognitive Services (the current default), and v3 is AWS Transcribe. This release adds Genesys' own first-party STT to the lineup as Genesys Enhanced v4.

Why care about a fourth option? Support, mostly. When recognition quality goes sideways on a third-party engine, troubleshooting involves a vendor hop, and vendor hops add days. With the native engine the whole pipeline is Genesys', which should shorten the path from ticket to answer. Consistency is the other reason: if you already run Genesys native transcription for post-call analytics, putting your bots on the same engine gives you one recognition behavior to tune instead of two.

Genesys buried the most useful detail in the STT engine documentation: custom ASR dictionaries only work with Genesys Enhanced v3 and v4. If your bots need to recognize product names or account jargon, the native engine is one of only two choices that let you teach it those terms.

Dialect coverage at launch is en-US, es-US, en-GB, and en-AU. You can set the engine as the org default or override it per Ask for Slot action, so trial v4 on a single collection step before you bet a whole flow on it. Licensing requires Genesys Cloud AI Experience (or Genesys Cloud 4).

Skip paths in Ask for Slot actions

Anyone who's read bot transcripts knows the pattern. The bot asks for an order number, the customer doesn't have one, and the conversation grinds through retries until someone gives up. This release adds a proper escape hatch: a Skip Response Capture path on Ask for Slot actions. Overdue.

When it's enabled, the customer can skip by saying so in natural language or by tapping a skip button, and the flow continues down a dedicated skip output path instead of failing the step. It works with every slot type, including AI-powered slots, and with the rich inputs digital bots rely on: quick replies, carousels, and list pickers.

The design win is that skipping is an explicit branch. You decide what happens next. Route to an agent, look the customer up by a different identifier, or carry on with the slot empty and handle it downstream.

What this means for your contact center

Neither change forces action. Together, though, they raise the ceiling on self-service quality. STT engine choice has historically been set-and-forget, decided at implementation time and never looked at again. With a first-party engine in the mix and per-action overrides available, I'd revisit it. Recognition accuracy is workload-specific, so the only honest answer is to test with your own call audio and your own dialects. If you're outside the four launch dialects, v4 isn't an option yet.

The skip path is what I'd act on first. Retry loops on unanswerable questions are one of the most common causes of bot abandonment, and the workarounds until now were clumsy: global intents that hijack the flow, or exhausting no-match retries and catching the failure path. A first-class skip branch is cleaner to build and much cleaner to report on. Skips become a signal you can count, telling you which questions customers routinely can't answer. That's design feedback you were losing inside no-match noise.

One caution: don't blanket-enable skip on every slot. A skippable required field just moves the failure downstream. Save it for optional data, or for steps where a solid fallback branch exists.

What to check

Check which STT engine your bot flows use today (org default vs. per-action overrides) and whether Genesys Enhanced v4 deserves a bake-off for en-US, es-US, en-GB, or en-AU traffic.
If your bots struggle with domain-specific vocabulary, remember that custom ASR dictionaries only work with Genesys Enhanced v3 and v4.
Confirm you have the licensing for native STT (Genesys Cloud AI Experience or Genesys Cloud 4) before planning a migration.
Pull recent bot transcripts and find the Ask for Slot steps with the highest no-match and abandonment rates. Those are your first skip-path candidates.
When you add a skip path, define the downstream handling explicitly (agent escalation, alternate lookup, or proceed without a value) and add tracking so skips show up in your flow analytics.
If you use dynamic list slots, slot changes still require republishing the flow.

Full details are in the official Genesys Cloud release notes for May 4, 2026. Questions about what these changes mean for your deployment? Email me.

Genesys Cloud Release Notes — April 27, 2026

2026-04-27T00:00:00Z

The April 27 release is a big one if you administer or supervise a Genesys Cloud org. Genesys Cloud Copilot has landed. That's the platform-level conversational assistant, not Agent Copilot, and the distinction matters. This post covers the two items I think matter most this week: the core Copilot launch and the Agent Recognition Assistant that ships as one of its AI agents.

TL;DR

Genesys Cloud Copilot is live. It's a conversational assistant built into the Genesys Cloud UI that gives admins, supervisors, and agents role-based help, from Resource Center answers to carrying out common administrative tasks.
This is platform Copilot, not Agent Copilot. It's aimed at running the platform itself, and it ships with a family of specialized AI agents (user management, queue routing, telephony, audit insights, and more).
Supervisors can create and look up agent recognitions by typing a prompt instead of clicking through screens. There's a confirmation step before anything gets submitted.
Both features need the Genesys Cloud AI Experience entitlement on top of a Genesys Cloud 4 license. Check your licensing before you plan a rollout.

Employee Productivity

Genesys Cloud Copilot (core launch)

Genesys Cloud now ships a conversational AI panel inside the main UI that adapts to who's using it. Ask it how something works and it pulls answers from Resource Center documentation in context. Ask it to do something and it can walk you through common administrative workflows, or carry them out via platform APIs, gated by your existing role-based permissions.

A few things to understand before you turn it on:

It's a different product from Agent Copilot. Agent Copilot helps agents during interactions (summaries, suggested responses). Genesys Cloud Copilot is for running the platform: configuration and knowledge lookup for admins and supervisors.
Under the hood it's a set of specialized AI agents rather than one bot. Genesys documents nine at launch, covering areas like user management, queue and routing changes, telephony and presence, WFM time-off handling, work team coordination, audit/change tracking, and bot analytics. Expect the list to grow.
Actions require human approval. Copilot confirms what it intends to change before it acts, and everything runs inside the permission model you already maintain. If a user can't do something in the UI, Copilot won't do it for them.
Licensing is Genesys Cloud 4 plus the Genesys Cloud AI Experience add-on, and Copilot is only available in regions where Genesys has enabled it.

Agent Recognition Assistant AI Agent

One of the launch AI agents deserves its own callout. Supervisors can now create and retrieve agent recognitions by typing a prompt. Ask Copilot to send a recognition to a specific agent for how they handled an escalation, pick from the standard badge types (Thank You, Congratulations, High Performance, Company Values), and attach a note, tags, or a related interaction.

Retrieval is the more useful half. You can ask for everyone you've recognized in the last 90 days ranked by count, or a summary of recognitions you received this month. Handy prep for coaching sessions and 1:1s. The assistant sits on the Employee Engagement Recognitions API, validates inputs inline, and shows you exactly what it's about to submit before sending.

One real limitation, and it's a pain if you wanted team-level visibility: the assistant only surfaces recognitions tied to the active user. A supervisor can't pull up recognitions that other supervisors sent. If you want a team-wide view of recognition activity, you still need the API or existing reporting.

What this means for your contact center

The direction matters more than any single feature here. Genesys is standardizing on a conversational layer for platform administration. Tasks that used to mean navigating four admin screens or writing an API script become a typed request with a confirmation step. For a lean admin team that's a real time-saver, especially for the infrequent tasks where nobody remembers the exact menu path.

The flip side is governance. Copilot acts through your permission model, so your permission model is now doing more work than ever. Over-provisioned roles that were merely untidy before are now an easy path to fast, conversational misconfiguration. Before enabling Copilot broadly, audit who holds admin and supervisor roles and trim what's accumulated. The built-in confirmation prompts help, but confirmation fatigue is real. People click yes.

Licensing is the other planning item. AI Experience is an add-on. If you haven't adopted Agent Copilot or other AI Experience features yet, this release changes the math on that SKU, because you're now weighing agent-assist and admin/supervisor productivity together.

What to check

Confirm your org has Genesys Cloud 4 with the AI Experience entitlement, and that Copilot is available in your region.
Review the enablement docs and decide which roles get Copilot access first. Start with a pilot group of admins and supervisors.
Audit role permissions before rollout. Copilot inherits them, so tighten anything over-provisioned.
If you use recognitions today, test the Agent Recognition Assistant with a pilot supervisor group, and warn anyone expecting team-wide reporting about the active-user limitation.
Flag internal runbooks that document click-paths for common admin tasks; Copilot-guided steps may replace several of them.
Brief supervisors that recognition entries created via Copilot are standardized (badge types, titles, notes) so coaching records stay consistent.

Full details are in the official notes: Genesys Cloud Release Notes — April 27, 2026.

Questions about rolling out Copilot or tightening permissions ahead of it? Email me. I help contact centers adopt Genesys Cloud features safely.

Genesys Cloud Release Notes — April 20, 2026

2026-04-20T00:00:00Z

Good week for builders. An async version of the aggregate analytics API, guide generation from transcripts in AI Studio, and, at long last, scheduled triggers for workflows. Here's my read on each.

TL;DR

Submit big analytics queries as a queued job instead of chopping them into interval-sized chunks. Same request body as the synchronous aggregate endpoint; results when the job finishes.
Point AI Studio at a queue and it turns 30–1,000 real transcripts into structured, step-based guide drafts.
Run workflows on a clock (interactive schedule or cron expression) without an external scheduler or a data action hack.

Platform and API: async aggregate queries

The aggregate metrics endpoint has always been the workhorse of Genesys Cloud reporting integrations, and its biggest pain point. Pull a wide date range at high granularity and you had to split the work into a pile of smaller synchronous requests, then stitch the results back together around rate limits. That code is a pain to write and a bigger pain to maintain.

The async variant flips this to request-and-wait: you submit the query, the platform queues it, and you collect results when the job completes. The input contract is the same as the existing aggregate endpoint, so migrating is mostly swapping the call pattern (submit, poll, fetch), not rewriting your query logic. I'd move nightly warehouse loads and big historical backfills over first. Keep the synchronous endpoint for dashboards where you need an answer now.

Self-service and automation: guides drafted from your transcripts

Genesys AI Studio can now generate draft guides directly from real customer–agent conversation transcripts. You pick a single queue, a channel (voice or message), a language, and a date range containing at least 30 transcripts. The system analyzes up to 1,000 of them, clusters the conversations by topic, and produces a structured, step-based draft that mirrors how your agents resolve those issues in practice.

This attacks the blank-page problem in automation design. Instead of interviewing supervisors and reverse-engineering desktop procedures, a designer starts from a draft grounded in real interactions, then edits and publishes.

The prerequisites: Virtual Agent enabled in the org, AI Insights enabled at the program level, AI Studio guide permissions, and queue view permission. Licensing is Genesys Cloud 4 or the AI Experience add-on; if you're on neither, skip this section. Generation can take several minutes on larger transcript sets. It's a design-time tool, not something you run in a loop.

Treat the output as a first draft in the strictest sense. Transcripts capture what agents do, including workarounds and policy drift, so review each generated guide against your intended process before it gets anywhere near a production Virtual Agent flow.

Self-service and automation: scheduled triggers for workflows

Triggers in Genesys Cloud have always been event-driven. This release adds a Scheduled Triggers tab (Admin > Orchestration > Triggers) where a workflow can run on a recurring schedule, either through an interactive picker (times, weekdays, days of month, months) or a five-field cron expression. An explicit time zone is required at creation.

Two constraints. Frequency is capped at two executions per hour per trigger, so this is for hourly and daily housekeeping, not near-real-time polling. And execution lands anywhere up to five minutes after the configured time (the offset is consistent per trigger), so don't build anything that assumes to-the-second precision. Scheduled triggers also pass no inputs to the workflow; the flow has to work out its own context when it wakes up.

Even with those limits, this closes a real gap, and it should have shipped years ago. Teams have been faking cron with external schedulers calling the API, or with awkward in-flow loops. Nightly data syncs and morning readiness checks can now live entirely inside the platform, governed by the Process Automation > Trigger permission set.

What this means for your contact center

The common thread this week is Genesys moving work you used to do around the platform into the platform. The async aggregate endpoint removes a whole category of client-side batching code from reporting integrations. Scheduled triggers remove the external cron box, along with its credentials and monitoring. Both shrink the amount of custom glue you own, which is where most Genesys Cloud integrations break.

Guide generation is the more strategic one. If you're on Genesys Cloud 4 or AI Experience and haven't adopted guides because authoring them is labor-intensive, a pilot just got a lot cheaper. Start with your highest-volume, best-transcribed queues; topic clustering does its best work on repetitive conversations.

One caution. Anything that generates content from transcripts inherits the quality of your transcription and program configuration. If transcription accuracy is poor on a target queue, fix that first or the drafts will reflect it.

What to check

Inventory the reporting jobs that split aggregate queries into chunks to dodge limits, and plan to move the biggest ones to the async endpoint.
Prototype the submit/poll/fetch pattern against one existing query before committing; the input contract is the same.
List every external cron job or third-party scheduler that exists only to kick off a Genesys Cloud workflow. Those are retirement candidates.
Check that the two-runs-per-hour cap and the five-minute execution window fit your use case before migrating anything time-sensitive.
Pick one high-volume queue with at least 30 transcripts in a recent window, generate a draft guide, and review it against your documented process.
Confirm who holds Process Automation > Trigger permissions and AI Studio guide permissions before turning either feature on broadly.

Full details are in the official Genesys Cloud release notes for April 20, 2026. Questions about your deployment? Email me. Reading these notes closely is my job.