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.