Workforce Engagement Management

 View Only

Sign Up

  • 1.  #WEMay | Genesys WEM Mythbusters: Workforce Management (WFM) 📅

    Posted 05-16-2025 05:00
    Edited by Tracy Vickers 08-05-2025 09:24

    Workforce Management might sound like spreadsheets, chaos, and last-minute shift changes—but it doesn’t have to be. In fact, a lot of what people think they know about WFM is stuck in the past. During #WEMay, we’re setting the record straight on what modern Workforce Management really looks like.

    Let’s break the myths and bring some clarity to the calendar.

    • Myth: Genesys WFM is only for voice channels. 
      • Reality: Genesys Cloud WFM solution supports voice, chat, email, messaging, and back-office work, across multi-skill, multi-channel environments. Learn more 
    • Myth: Schedules are fixed and agents have no flexibility. 
      • Reality: Agents can bid on preferred shifts, trade shifts with others, and access schedules from mobile devices — all built into native WFM. Learn more 
    • Myth: Intraday monitoring just shows service level. 
      • Reality: Genesys Intraday tools compare actual vs. planned metrics across occupancy, adherence, staffing, and handle time — all in real time. Learn more 
    • Myth: You need external tools for time-off requests. 
      • Reality: Genesys Cloud includes integrated time-off management, request approvals, and adherence impact visibility — no need for third-party systems. Learn more 
    • Myth: WFM tools are complex and require extensive training. 
      • Reality: Genesys WFM offers an intuitive interface with guided workflows, making it accessible for users without extensive training. Learn more 
    • Myth: WFM doesn't account for agent skills. 
      • Reality: Genesys WFM considers agent skills and proficiencies when forecasting and scheduling to ensure optimal task assignments. Learn more 
    • Myth: Schedule changes are cumbersome to implement. 
      • Reality: Genesys WFM allows for quick adjustments to schedules, accommodating unexpected changes efficiently. Learn more 
    • Myth: WFM can't handle complex scheduling scenarios. 
      • Reality: Genesys WFM is equipped to manage complex scheduling needs, including varying shift patterns and agent availability. Learn more 
    • Myth: Forecasting doesn't adapt to sudden changes. 
      • Reality: Genesys WFM's forecasting tools can adjust to real-time data, allowing for responsive scheduling adjustments. Learn more 
    • Myth: WFM doesn't support remote workforces. 
      • Reality: Genesys WFM supports remote and distributed teams, providing tools for scheduling, monitoring, and communication. Learn more 
    • Myth: WFM doesn't integrate with other systems. 
      • Reality: Genesys WFM offers integration capabilities with various systems to ensure seamless operations. Developer Center 
    • Myth: WFM lacks real-time adherence monitoring. 
      • Reality: Genesys WFM provides real-time adherence features to monitor agent activities against schedules. Resource Center 
    • Myth: WFM doesn't support shift trading. 
      • Reality: Genesys WFM includes shift trading functionalities, allowing agents to swap shifts with appropriate approvals. Resource Center 
    • Myth: WFM can't accommodate part-time agents. 
      • Reality: Genesys WFM supports various employment types, including part-time scheduling. Resource Center 
    • Myth: WFM doesn't provide mobile access for agents. 
      • Reality: Genesys WFM offers mobile-friendly interfaces, enabling agents to access schedules and make requests on-the-go. Resource Center 
    • Myth: WFM doesn't support forecasting for back-office tasks. 

      • Reality: Genesys WFM can be configured to forecast and schedule back-office activities effectively. Resource Center 
    • Myth: WFM lacks reporting capabilities. 

      • Reality: Genesys WFM provides comprehensive reporting tools to analyze performance and adherence metrics. Resource Center 
    • Myth: WFM can't handle multiple time zones. 

      • Reality: Genesys WFM supports scheduling across different time zones, accommodating global operations. Resource Center 
    • Myth: Shift bidding is unavailable. 

      • Reality: Genesys WFM includes Work Plan Bidding functionality, which allows agents to bid for available shifts based on predefined business rules, eligibility, and fairness policies, improving employee flexibility and engagement while maintaining operational needs. Learn more 

    Gone are the days of guesswork forecasting, copy-paste schedules, and mysterious adherence reports. WFM is powered by AI, backed by data, and designed for humans—not just planners.

    Whether you’re optimizing a team of 20 or 2,000, today’s WFM tools help you schedule smarter, respond faster, and keep your agents (and customers) happier.

    So yes, you can stop dreading the schedule. WFM just got an upgrade—and it’s kind of a vibe.


    #Workforce Management
    #WEMay

    ------------------------------
    Tracy
    Genesys
    ------------------------------



  • 2.  RE: #WEMay | Genesys WEM Mythbusters: Workforce Management (WFM) 📅

    Posted 05-19-2025 12:02

    Hi Tracy,

    I like this, however I think item 8 and 12 are the same.



    ------------------------------
    Richard Chandler
    Connect
    ------------------------------



  • 3.  RE: #WEMay | Genesys WEM Mythbusters: Workforce Management (WFM) 📅

    Posted 05-19-2025 12:26

    Good spot, Richard, thank you!

    I've looked and read them so many times my eyes must have given up 😃🫨



    ------------------------------
    Tracy
    Genesys
    ------------------------------



  • 4.  RE: #WEMay | Genesys WEM Mythbusters: Workforce Management (WFM) 📅

    Posted 05-19-2025 12:45
    Edited by Tracy Vickers 08-05-2025 09:26

    Hi Tracy!

    I have lots of questions (as per usual); I have pasted them below. Please let me know if there is a better/more appropriate method of communication: 

    1: Genesys WFM Is only for voice channels:

    • Can you confirm how Genesys cloud handles omni channel agents (agents who can handle all media types in several queues)? How does this impact capacity planning/headcount forecast? Does the system optimize the agents in certain queues?
      • Are agents considered a scheduled resource in each planning group or partial agent in each planning group)
      • Example: agent can work voice and chat; schedule says 2 agents scheduled, 4 agents required.  Dees the agent who can handle chat and voice get counted as 1 scheduled agent for each planning group and as 2 of the required? 
    • Can you confirm that Genesys only forecasts inbound volume and any plans to forecast outbound volume based on connection rate?

    3: Intraday

    • Currently the intraday shows data for the plannings when the forecast the schedule was based on was created; it does not account for adding/removing of agents to/from queues+skills+Languages.  This means that if an agent has been removed from a queue (or planning group) since the creation of the forecast, they are still considered a "scheduled" resource on the intraday report but are not an "actual" agent in the same report.  Any thoughts on managing this or upcoming changes to reflect the CURRENT resourcing?

    4: Time Off Requests

    • Can you confirm what is passed between the HRIS system and the Genesys Cloud system?  It was my understanding that it would just be time off balances (allowing us to create criteria for approve/deny based on personal allotments), but this makes it seem like  the request itself will be passed between the two?
      • If the request is passed between the two, do both systems have record of it?

    6: WFM doesn't account for agent skills

    • "WFM Considers agent skills and proficiencies when forecasting and scheduling" Can you clarify this statement? I have not, to date, seen proficiencies taken into consideration when scheduling and don't see anywhere in the documentation that this is indicated.  The system seems to treat any agent who can work the planning group volume the same.
    • Can we confirm:
      • Agents are optimized in planning groups that they are most proficient?
      • Is the above visible anywhere in the WFM system (not on the agent page but anywhere else?)
      • Scheduling optimization/planning group membership does not take activation/deactivation state into consideration

    7: Schedule changes are cumbersome to implement

    • Is there anything on the roadmap for the following enhancements or any work arounds I may not be aware of:
      • Work Plan assignments during published schedules are automatically implemented
      • Agents moved to a new work plan can be synced into existing schedules without full reschedule (if based on forecast) or completely rebuilt (if not based on forecast)
      • Recurring events for all attendees (i.e. scheduling a weekly team meeting for ALL team members)
      • Notifications if a break/meal is overridden by an activity plan or externally scheduled work plan (still only works if breaks/meals are considered "interruptible")
      • Schedules may not be unpublished if published in error

    9: Complicated scheduling scenarios

    • Would like to see some use cases of what are considered "complicated" and how Genesys manages them.
    • To date, the system does not manage multi-skilled agents that activate/deactivate in queues throughout the date.  No real work around for this that I am aware of either.

    10: Forecasting doesn't adapt to sudden changes

    • Does the WFM team have recommendations on how to "exclude" data for known outliers in the Automatic Best Method forecasting method?

    13: Real Time monitoring:

    • Are there any plans to put "real time queue activity" and "real time adherence" into the same view?
    • Any plans to allow WFM admins to make real time management changes to queues, skills, proficiencies from any views vs. going through Admin>People?

    19: WFM can't handle multiple timezones

    • Can we clarify this? It is my understanding that the work plans must be created in the time zone of the business unit but the agent will see the schedule in their own timezone (via their browser settings). Is this accurate?  If so, is there a way to build work plans in the agent's timezone vs. having to do mapping?  Also, if I have global agents in the same time business unit and schedule for forecasting purposes, I can only view the schedule in one timezone; I would have to separate agents into management units by timezone to separate them out by timezone, correct?

     

     



    ------------------------------
    Shelby Cronk
    ------------------------------



  • 5.  RE: #WEMay | Genesys WEM Mythbusters: Workforce Management (WFM) 📅

    Posted 05-20-2025 04:00

    Hi Shelby,

    Lots of questions😀 

    Bear with me, whilst I try to find some answers for you!



    ------------------------------
    Tracy
    Genesys
    ------------------------------



  • 6.  RE: #WEMay | Genesys WEM Mythbusters: Workforce Management (WFM) 📅

    Posted 05-23-2025 10:42

    Hi Shelby,

    Thank you for your comments, questions, and ideas; and apologies for the delay in responding. I wanted to ensure I provided you with as much detail as possible.
    Please don't hesitate to reach out if you have any further questions or need additional clarification.
    Also, I will provide my answers in a couple of posts.

    Myth 1: Genesys WFM is only for voice channels

    Reality: Genesys Cloud WFM is fully omni-channel, supporting voice, chat, email, messaging, and back-office work for inbound interactions, not outbound.

    Questions breakdown:

    • How does Genesys Cloud handle omnichannel agents (agents who can handle all media types in several queues)?
    • How does this impact capacity planning/headcount forecast?
    • Does the system optimize the agents in certain queues?
    • Are agents considered a scheduled resource in each planning group or partial agent in each planning group?
    • If an agent can work voice and chat, and the schedule says 2 agents scheduled, 4 required, does that dual-skilled agent count as 1 scheduled agent for each planning group and 2 of the required?
    • Can you confirm that Genesys only forecasts inbound volume and any plans to forecast outbound volume based on connection rate?

    Answer:

    Genesys Cloud WFM was designed with omnichannel and multi-skill environments in mind. It enables businesses to plan and schedule for agents handling a mix of voice, chat, email, messaging, and asynchronous back-office tasks within a unified interface.

    Omnichannel agents: Genesys Cloud WFM fully supports omnichannel operations. Agents can be configured to support multiple interaction type, including voice, chat, email, messaging, and back-office tasks; via queue and skill assignments. Their membership in different planning groups allows them to be factored into multiple workload forecasts, though they are only scheduled once per interval. Agents can be assigned to multiple media through their planning group memberships, which combine queue, media type, and skill.

    About Planning Groups

    Impact on forecasting and scheduling: Each planning group has its own forecast based on volume, AHT, and shrinkage assumptions per media type. The same agent can be eligible for multiple groups, but Genesys does not double-count scheduled hours. An agent is scheduled once, and WFM does not optimize across queues in real time, it assumes static membership for the duration of the planning period.

    Each planning group, defined by a unique combination of queue, media type, and skill; has a separate headcount requirement forecast. Agents eligible across multiple groups are not double-booked, but can contribute to capacity where applicable. Care must be taken to model overlapping media demands appropriately, especially for real-time channels like voice and chat.

    The multiskill and multimedia capabilities of each agent are fully considered when forecasting workload and scheduling. This includes fractional contributions to blended workloads, ensuring accurate workload coverage based on the specific skills and qualifications of each agent across all work types.

    Agent count logic (example explained):
    In your example, a dual-skilled agent is:

    • Counted once in the scheduled headcount.
    • Contributes capacity to both groups if their skills match and if WFM configuration permits.
    • However, this does not mean they fulfill both requirements simultaneously. Overlapping demands must be modeled carefully to avoid under- or over-staffing.

    Optimization and partial scheduling: There is no dynamic real-time optimization that reallocates agents across queues during the schedule. WFM assumes static planning group membership for each agent for the purpose of forecasting and scheduling.

    Clarifying the example: If two agents are scheduled and four are required, and one of those agents supports both voice and chat, that agent contributes to both groups. However, they are only counted as one scheduled agent overall-not two. This means they cannot fully meet both needs simultaneously without overlap, so dual-skill agents need to be managed carefully to avoid gaps.

    Outbound forecasting:
    Genesys Cloud currently does not forecast outbound interactions (predictive dialing, proactive messaging, etc.) based on connection rates. Only inbound interactions are supported for forecasting purposes.

    Best practices:

    • To avoid schedule collisions in multi-media planning, stagger agent group assignments and use weighted forecasting assumptions.

    #WEMay Clarity: Genesys Cloud WFM isn't just for voice-it's omnichannel by design.  Genesys WFM is built for multi-skill, multi-channel environments, not just voice. Forecasting, planning, and intraday management work across all channels natively and accounts for diverse workloads across digital and voice channels, ensuring accurate forecasting and intelligent workforce alignment.

    Roadmap: Support for Outbound work in Genesys Cloud WFM is on evaluation on the Ideas Lab. Customers can follow progress and contribute feedback by voting on the related idea in the Genesys Ideas Portal and can join the User Sponsor Program

    Ideas Portal: Great ideas are more than welcome, share them with us or vote for existing ones https://genesyscloud.ideas.aha.io/  

     

    Myth 2: Intraday monitoring just shows service level

    Reality: Genesys Cloud WFM provides real-time intraday dashboards that allow planners and supervisors to compare actual versus forecasted staffing, adherence, occupancy, and handle time-beyond just service level.

    Questions: breakdown

    • If an agent is removed from a queue after schedule creation, do they still appear as scheduled in intraday but not actual?
    • Are there any plans to reflect real-time queue/skill changes in intraday views?

    Answer:

    WFM's intraday module uses the forecast and schedule context established at the time of planning. If queue or skill assignments are changed after this point, intraday views do not dynamically update to reflect these changes.

    This can result in mismatches where agents still appear as "scheduled" but no longer contribute to "actual" metrics.

    In Genesys Cloud WFM, you can connect a new forecast to an existing work plan and schedule. Doing so updates Intraday Monitoring to reflect the revised forecasted demand, allowing you to adapt to changes without needing to recreate your schedules from scratch. This capability is also foundational to our Work Plan Bidding solution, where you can initiate a bid based on a forecast and set of work plans. Once employees submit their preferences, you can regenerate the forecast with the latest inputs and generate schedules, based on the defined structure, that align with both demand and employee selections.

    Intraday Monitoring Overview

    How it works:

    • Intraday comparisons are based on the snapshot of queue and skill assignments from when the forecast and schedule were generated.
    • If agents are removed from a planning group after schedule creation, they remain shown in the "scheduled" column but will not appear in "actuals."

    Intraday Monitoring Overview

    • Best practices and recommendations:
      • Reforecasting and/or rescheduling using current queue assignments is required to align metrics.
      • Regular audits of agent queue/skill configurations before publishing schedules will minimize these discrepancies.

    Roadmap: There is no published roadmap item for dynamic intraday adjustment based on real-time queue reassignments, but this feedback is valuable.

    #WEMay Clarity: Genesys Cloud WFM delivers real-time visibility into performance, but forecast and schedule accuracy depend on maintaining alignment between planning groups and live configurations.

    Ideas Portal: Great ideas are more than welcome, share them with us or vote for existing ones https://genesyscloud.ideas.aha.io/  

     



    ------------------------------
    Natalia Abad
    Senior Product Marketing Manager
    ------------------------------



  • 7.  RE: #WEMay | Genesys WEM Mythbusters: Workforce Management (WFM) 📅

    Posted 05-23-2025 10:46

    Part 2:

    Myth 3: You need external tools for time-off requests

    Reality: Genesys Cloud includes native time-off management, approval workflows, adherence impact visibility, and integration capabilities with HR systems.

    Questions Breakdown:

    • What data is passed between the HRIS system and Genesys Cloud WFM?
    • Is it only balances, or also the requests?
    • If requests are passed, do both systems record them?

    Answer:

    Genesys Cloud WFM supports integration with HRIS systems to streamline the employee time-off management process. The depth of integration can vary depending on your implementation.

    When a time-off request is submitted, Genesys Cloud WFM first checks all relevant constraints defined in the associated Time-Off Plan, which includes checks against line-of-business-specific balances, activity types, and other rules. Only after passing these checks is the request sent to the integrated HRIS system, which then applies its own approval logic based on its configuration.

    What's passed depends on your integration level:

    Basic Integration:

    • Passes time-off balances only, which WFM uses for request validation (approval/denial logic).
    • Allows time-off balances transfer information into Genesys Cloud.
    • Enables time-off approval logic based on accrued or available balance.

    Advanced Integration:

    • Supports two-way syncing of time-off requests, approvals, and statuses.
    • When configured (e.g., with Workday), time-off requests initiated in Genesys Cloud can be reflected in the HRIS, and vice versa.
    • Both systems maintain a record of the request, and updates can be mirrored between them.

    Time-off integration

    • Data Sync Capabilities:
      • Basic Integration: Syncs balances to apply criteria for auto-approvals/denials.
      • Advanced Integration: Full bidirectional sync (e.g., Workday) allows requests, approvals, and statuses to pass between systems.
    • Record Location: When requests are synced, both systems retain a record, with approval logic driven by WFM or the HR system, depending on the setup.

    #WEMay Clarity: Native time-off request management in Genesys Cloud WFM is robust and extensible. It works well as a standalone or integrated solution, enabling smart scheduling and agent self-service.

    Ideas Portal: Great ideas are more than welcome, share them with us or vote for existing ones https://genesyscloud.ideas.aha.io/  

     

    Myth 4: WFM doesn't account for agent skills

    Reality: Genesys Cloud WFM considers agent skills (but not proficiencies) when building planning groups and schedules.

    Questions Breakdown:

    • Genesys says WFM considers skills and proficiencies. But is proficiency actually used?
    • Are agents optimized for groups they are most proficient in?
    • Can we see this prioritization anywhere in the UI?
    • Does activation/deactivation of queues affect planning group assignment?

    Answer:

    Genesys Cloud Workforce Management (WFM) currently supports a fully blended model for work routing and agent scheduling. This means that when an agent is scheduled to be on queue, the system assumes they are available to handle any type of work they're qualified for, regardless of channel or interaction type.

    In fact, Genesys Cloud WFM fully supports skills-based routing. Routing skills are used when defining route paths within Planning Groups, and agent skills are taken into account during scheduling to ensure each agent is assigned work they're qualified to handle.

    Skills: Yes, WFM uses skills (e.g., "Spanish", "Tech Support") to determine planning group eligibility.

    Genesys Cloud WFM does consider skill, queue and language (these are all used to map users to Planning groups) we do assume 100% proficiency when simulating workloads and generating staffing requirements.

    • What's Considered: Agents must match the queue, media type, and skill required to be included in a planning group.
    • What's Not Considered: Skill proficiencies (i.e., agent A is better at sales than agent B) are not used in scheduling logic.

    Proficiencies: No, WFM currently does not use skill proficiency levels to prioritize scheduling. It treats all eligible agents equally.

    Optimization based on proficiency:

    • Agents are not optimized for the groups they are most proficient in.
    • Proficiency is visible on the agent profile but not used in scheduling logic or seen elsewhere in planning views.

    Queue activation state:

    • WFM does not dynamically update planning group membership based on queue or skill activation/deactivation during the day.
    • Once schedules are generated, they are based on the static agent configuration at that time.

    Agent skills

    • Agent Optimization: There is no automatic preference for more proficient agents.

    About Planning Groups

    • Visibility: Planning group membership is managed in the Admin interface but proficiency-based optimization is not shown anywhere.

    Best practices:

    • Regularly audit agent queue/skill assignments prior to scheduling.
    • Clearly communicate to supervisors that proficiency is not factored into planning.

    #WEMay Clarity: Skills are essential to WFM eligibility and accuracy, but today, proficiencies are not part of the optimization engine. Keep this in mind when defining planning groups and coverage.

    Ideas Portal: Great ideas are more than welcome, share them with us or vote for existing ones https://genesyscloud.ideas.aha.io/  

     

    Myth 5: Schedule changes are cumbersome

    Reality: Genesys WFM allows flexible changes, but some actions require full rescheduling or creative workarounds.

    Questions Breakdown:

    • Are there any roadmap updates or workarounds for:
      • Work plan changes post-publishing?
      • Recurring events for all attendees?
      • Breaks overridden by meetings?
      • Unpublishing schedules?

    Answer:

    In the Schedule Editor, the 'Schedule Count' reflects all agents included in your current filter, while the 'Service Goal Metrics' display data based on the planning groups you've selected. To ensure accurate and meaningful comparisons, we recommend filtering the bottom panel to include only the agents who are assigned to the planning groups you're analyzing; this way, you're truly comparing apples to apples.

    Work Plan changes after publication:

    • Currently, updates to work plans do not apply retroactively to published schedules.
    • Work plan changes after schedule publication require manual re-scheduling.
    • No support for recurring meetings across multiple agents for selfservice.
    • Override warnings for meals/breaks only appear when activities are interruptible.
    • Once published, schedules cannot be unpublished.
    • To reflect a new work plan, remove the agent, save the schedule, re-add the agent, and publish using the updated plan.

    Recurring events for all agents:

    • Use activity plans to simulate recurring team events across a schedule.

    Unpublishing schedules:

    • There is no direct unpublish option.
    • Instead, create and publish a new schedule for the same period that overrides the previous one.

    Emerging Capabilities:

    • Shift trading, time-off approval visibility, and real-time adherence are live.
    • Auto-implementation of new work plans mid-cycle is not yet available.

     About Work Plans

    Tip: Use activity codes with external event triggers and work plan rotation rules to handle repeating meetings.

    Best practices:

    • Use templates or bulk edits to add recurring meetings.
    • Train team leads to submit corrections early to reduce schedule churn.
    • Use rotation rules or calendar-based templates for recurring tasks.
    • For team events, create an activity category like "Team Meeting" and manually insert into schedules.

    #WEMay Clarity: Schedules can adapt quickly, just not always automatically. With smart use of templates, activity codes, and version control, teams can stay flexible and resilient.

    Roadmap: Batch Editing in Schedule Editor
    We're planning enhancements to the Schedule Editor that will allow for batch editing of activity and shift start times. This will streamline updates across multiple agents and improve efficiency for workforce planners.

    Ideas Portal: Great ideas are more than welcome, share them with us or vote for existing ones https://genesyscloud.ideas.aha.io/  

    We have heard your comment and others have been requested via the Ideas Portal, and are under review.

     



    ------------------------------
    Natalia Abad
    Senior Product Marketing Manager
    ------------------------------



  • 8.  RE: #WEMay | Genesys WEM Mythbusters: Workforce Management (WFM) 📅

    Posted 05-23-2025 10:53

    Finally, part 3.

    Myth 6: WFM can't handle complex scheduling Scenarios

    Reality: Genesys Cloud WFM supports complex scheduling patterns, but does not currently support intraday activation/deactivation of skills or queues. 

    Questions Breakdown:

    • What complex scenarios are supported?
    • Can agents be scheduled for skill/queue changes intraday?

    Answer:

    Supported Scenarios:

    • Multi-skill, multi-channel, part-time, split shifts, rotations, and back-office support.
    • Part-time schedules, variable shifts, split shifts, back-office work, shrinkage, and multi-channel skills are supported.

    ·         Create Schedules

    Not supported:

    • Dynamic skill/queue activation throughout the day.
    •  Agents are planned based on their static group membership at the time of scheduling. – We don't support this per best practice, but block scheduling will help ;)

    Best practice/Roadmap:

    • Consider scheduling blocks using distinct activities if partial-day assignments are known.
    • Use adherence monitoring to flag manual queue changes when needed and use triggers to receive notifications. (als,o we have ideas on our roadmap)

    Roadmap Update: Block Scheduling will enable the ability to designate specific times of day for particular types of work, configurable at the Planning Group level. This enhancement is currently in development.

    #WEMay Clarity: Complex coverage needs? Covered. Just remember, Genesys WFM is great at planned complexity but doesn't yet handle dynamic real-time queue toggling.

    Ideas Portal: Great ideas are more than welcome, share them with us or vote for existing ones https://genesyscloud.ideas.aha.io/  

     

    Myth 7: Forecasting doesn't adapt to sudden changes

    Reality: Genesys Cloud WFM forecasting is powered by statistical models, but outlier management must be handled manually.

    Questions Breakdown:

    • Can WFM exclude outlier data automatically when using "Automatic Best Method"?

    Answer:

    Genesys WFM's "Automatic Best Method" chooses the best statistical fit but does not auto-exclude outlier dates.

    How Automatic Best Method works:

    • It evaluates several forecasting algorithms and selects the most accurate based on historical data.
    • However, it does not auto-filter holidays, spikes, or data anomalies.

    Best practice:

    • Manually remove outlier days (e.g., holidays) before running the forecast.
    • Use the Edit Historical Data function to remove non-representative days before running the forecast.
    • Validate historical data inputs for known exceptions.
    • How to Exclude Outliers:
      • Before creating a forecast, manually remove outlier dates from historical data.
      • Use the "Edit Historical Data" tool to deselect holidays or spike events. 

    Create a Forecast

    #WEMay Clarity: Forecasting is smart-but not psychic. Help it along by curating clean, relevant history to get the best predictions.

    Roadmap: Forecast Adjustments for Special Events
    We are planning to release tools to account for special events, where you will be able to use to inform or modify the forecast based on known events, anomalies, or trends. Currently, Genesys allows forecast modifications and further enhancements are on the roadmap to expand these capabilities.

    Ideas Portal: Great ideas are more than welcome, share them with us or vote for existing ones https://genesyscloud.ideas.aha.io/  

     

    Myth 8: WFM lacks unified real-time monitoring

    Reality: Genesys Cloud WFM offers real-time queue and adherence monitoring, though they remain in separate interfaces today.

    Questions Breakdown:

    • Will queue activity and adherence be viewable in the same interface?
    • Can WFM admins edit queues/skills directly from these views?

    Answer:

    • Adherence and queue metrics are currently available and accessible in separate interfaces.
      • Adherence Monitoring: Found under Workforce Management > Adherence
      • Queue Monitoring: Found under Performance > Queues
    • All updates to skills, queues, and proficiencies must still go through Admin > People.
    • Admin Changes: Still must be made in Admin > People > Skills/Queues. No in-line WFM edit capabilities yet.

    #WEMay Clarity: Genesys Cloud gives real-time insight, but real-time reconfiguration still relies on the admin console. Seamless control is a future-facing opportunity.

    Ideas Portal: Great ideas are more than welcome, share them with us or vote for existing ones https://genesyscloud.ideas.aha.io/  

     

    Myth 9: WFM can't handle multiple time zones

    Reality: Genesys WFM supports scheduling across different time zones and global operations, with agents seeing their schedules in their local time.

    Questions Breakdown:

    • Are work plans fixed to the business unit timezone?
    • Can they be built in the agent's timezone?
    • Can I view schedules by agent timezone?

    Answer:

    Genesys Cloud WFM allows you to define your organizational structure with a headquarters time zone at the business unit level. Administrators can manage shifts and schedules in this time zone for ease of planning. Agents, however, always see their schedules in their personal browser's time zone, ensuring clarity and consistency from their perspective.

    Genesys Cloud WFM is designed to support globally distributed teams and can accurately handle time zone differences with the following considerations:

    Work plan configuration:

    • All work plans are created in the business unit's time zone.
    • Scheduling logic is applied based on that time zone context.

    Agent experience:

    • Regardless of the time zone of the work plan, agents will see their schedules in their local browser/system time zone.
    • This allows for intuitive viewing and mobile access without time zone confusion.

    Recommendation:

    • Create BUs and management units strategically per time zone where granular schedule visibility is needed.
    • Use time-zone-aware labels in work plan naming conventions.
    • If you want to manage schedules in multiple time zones, you must create separate management units for each timezone.

     Work with Management Unit

    #WEMay Clarity: Global scheduling is possible, but proper BU/management unit setup is required for timezone-specific planning views.

    Genesys WFM supports distributed workforces with localized time displays. With thoughtful setup, it enables global scheduling that works for everyone, everywhere.

    Roadmap: Daylight Saving Time Enhancements
    We're planning improvements to handle Daylight Saving Time differences between the business unit's time zone and the agent's local time zone.

    Ideas Portal: Great ideas are more that welcome, share them with us or vote for existing ones https://genesyscloud.ideas.aha.io/  



    ------------------------------
    Natalia Abad
    Senior Product Marketing Manager
    ------------------------------