A short week, six items, and a clear theme running through half of them: Architect workflows are reaching further into events that used to be invisible to automation.
TL;DR
- Architect workflows can trigger on Collaborate chat messages being created, updated, or deleted.
- Architect workflows can also trigger on user presence events from UC integrations like Microsoft Teams, Zoom, and 8x8, not just Genesys Cloud presence.
- Embedded client agent settings now persist server-side instead of in browser storage, so they survive a machine change.
- Work items support custom iframe panels published by developers and added by administrators.
Employee Productivity
The two new trigger types are the interesting pair. Workflow triggers on Collaborate chat messages mean automation can respond to internal chat activity, and triggers on external UC presence mean a workflow can react when someone goes available in Teams or Zoom rather than only in Genesys Cloud.
That second one closes a real gap. Plenty of organizations have expertise sitting in Teams rather than in the contact center, and until now Genesys had no event to hang automation off when that person became reachable. Escalation paths that depended on a human noticing can become something the platform notices.
I would treat presence-driven automation carefully all the same. Presence is a noisy signal, people leave themselves Available while walking away, and a workflow that routes work on presence alone will find that out. It works best as one input among several, not as the whole rule.
Persistent agent settings for embedded clients is the small fix that saves repeated annoyance. Settings like prompt for queue on click-to-dial and remember the last selected queue now live server-side rather than in browser local storage. Agents on shared machines, or anyone whose browser data gets cleared by policy, stop losing their configuration.
Administrators can also let users suppress profile notifications, which previously arrived by default with no way to turn them off.
Customer Engagement and Reporting
Work items now support custom panels. Developers publish custom iframe panels and administrators attach them to work items, which is the usual pattern for surfacing an external system next to the work rather than in another tab. As with any iframe integration, the authentication story is the part to design first.
Dashboards gained a responsive layout with auto-scaling widgets, so a dashboard holds up on a screen it was not built for. If you have wall displays at one resolution and supervisors on laptops at another, this is the change that stops you maintaining two versions.
Suppressing profile notifications deserves a line of its own, because the previous behaviour was the kind of thing people quietly work around. Users received them by default with no opt-out, which trains everyone to ignore the notification area, and once that habit forms the notifications that do matter get ignored with it. Letting users turn off the noise is how the signal survives.
What this means for your contact center
The trigger work is the part worth exploring, and it is exploratory rather than urgent. If you have an escalation or notification process that currently depends on somebody watching something, these events are the raw material for automating it.
Everything else this week is quality-of-life. Useful, but nothing that needs a plan.
What to check
- List the escalation paths that currently rely on a person noticing a chat or a colleague becoming free, and see whether the new triggers cover them.
- Design the authentication approach before building a custom work item panel, not after.
- Confirm embedded client agent settings now persist for agents on shared or locked-down machines.
- Test a key dashboard at both wall-display and laptop resolutions now that layouts scale.
Full details are in the official Genesys Cloud release notes for September 23, 2024. 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.