Workforce Engagement Management

Sign Up

  • 1.  Having practically a single work plan per agent. Good or bad?

    Posted 8 days ago

    I have so many clients that insist that they need to have a work plan for every agent out there. My reply is that by doing so, you are leaving very little for WFM to do. Sure you can keep track of adherence or compliance, but as far as forecasting and scheduling what do you expect the WFM to do when you are dictating schedules. Have any of you run into this or are you doing this with your contact center? What is the justification for this and how should we approach our clients with an answer to help WFM work for them instead of them working against it?  


    #ScheduleManagement
    #WFMConfiguration,BestPractices

    ------------------------------
    Robert Wakefield-Carl
    ttec Digital
    Sr. Director - Innovation Architects
    Robert.WC@ttecdigital.com
    https://www.ttecDigital.com
    https://RobertWC.Blogspot.com
    ------------------------------


  • 2.  RE: Having practically a single work plan per agent. Good or bad?

    Posted 7 days ago

    I have many clients who take the same approach, and also some that do not. The decision point is usually around whether activity plans can work to populate the individual requirements for agents sharing work plans. The other factors are whether the individual work plans contain any flexibility. If they do, then WFM still does some work, if not then as you have said, WFM does very little.

    Chris Perry | Business Analyst & WFM Consultant, Customer Experience

    Chris.Perry@nttdata.com



    ------------------------------
    Chris Perry
    Ts Systems Integration Specialist
    ------------------------------



  • 3.  RE: Having practically a single work plan per agent. Good or bad?

    Posted 7 days ago

    I've found a lot of this is based around existing contracts. Working times were tailored to the agent and then in the future WFM came along and long tenured agents all had bespoke plans with fixed meal times. As customer contact patterns change the older contracts are no longer fit for purpose. There is then a bigger picture than purely WFM although that plays a big part in modelling. How can the organization provide better service to clients as well as offering flexibility to staff and taking advantage of swapping with a later shift in the system (alternative shifts), or unavailable times for future appointments without having to take time off.

    A lot of this will depend on industry and country regulations. Certainly in the UK that almost always means a new contract of employment and 2 weeks notice is not a thing here.

    Without some business level architectural change WFM will largely tell you how bad your service level is or where you are overstaffing but not resolve the problem.



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



  • 4.  RE: Having practically a single work plan per agent. Good or bad?

    Posted 6 days ago

    Hi Robert, 

    We are seeing a shift back toward per-employee Work Plan configurations to better accommodate flexible working requests. In this model, employees have the option to request specific working hours or flexibility to better manage their work–life balance.

    We recognise that this can be a challenging discussion. Our hope is that features like those outlined below, which can be layered on top of a Work Plan, will enable organisations to maintain more standardised, business-flexible constraints while empowering employees to make short-term adjustments when needed.


    • Agent Unavailable Times - the ability for employees to submit hard scheduling constraints for periods of the day when they are not available to work. 
      • This is most often the best fit for those organisations that are starting to move towards a Work Plan per employee configuration, as it allows for the personal "customisation" without the admin of having to manage large numbers of Work Plan configurations
    • Schedule Set bids - fixed schedule set of 1-6 weeks in length that Employees can bid on, which are valid, optimised options created from an underlying Work Plan
      • provides the employee with some flexibility and preference on which resulting work patterns they work from a range of optimal schedules that meet the business requirements.
    • Schedule Preferences - the ability for employees to provide soft scheduling constraints on when they would prefer to work. 

      Tagging my fellow Product Manager @Andrew Boland as we'd love to hear more about the challenges you are facing around this topic and the solutions that businesses are implementing. 

      Paul


    ------------------------------
    Paul Wood
    Product Manager for Genesys Cloud Workforce Management
    ------------------------------



  • 5.  RE: Having practically a single work plan per agent. Good or bad?

    Posted 6 days ago

    Thanks, Paul, for chiming in. Would love to hear from you and Andrew about what it handicapped when you let the agents dictate schedules in WFM and how Work Plan Bidding allows for the flexibility without tying the hands of AI for scheduling.  



    ------------------------------
    Robert Wakefield-Carl
    ttec Digital
    Sr. Director - Innovation Architects
    Robert.WC@ttecdigital.com
    https://www.ttecDigital.com
    https://RobertWC.Blogspot.com
    ------------------------------



  • 6.  RE: Having practically a single work plan per agent. Good or bad?

    Posted 5 days ago

    Thanks Robert and Dave, really appreciate you both sharing how you're seeing this play out in practice.

    A lot of what you're describing is exactly the tension we're trying to address:

    • If every agent has a completely bespoke work pattern, optimisation space shrinks and admin overhead increases.

    • If everything is rigid and standardised, it becomes hard to support flexible working requests.

    The approach we're working toward isn't about letting agents dictate schedules, but rather layering flexibility on top of a standardised Work Plan.

    To touch on the examples Paul gave:

    Agent Unavailable Times (now live)
    Agents can add times on a day-by-day basis that they cannot work. These are treated as hard constraints, and the system will honour them, but the schedule is still built from the underlying Work Plan. Agents are warned if what they enter would prevent a viable shift being assigned.

    The intention here is to reduce the need to create lots of structurally different Work Plans just to reflect personal constraints.

    Agent Preferences
    This is similar in concept, but softer. Agents can mark times as Strongly Prefer, Prefer, Avoid or Strongly Avoid. The system scores potential shifts accordingly and will try to assign the highest-scoring option, provided doing so doesn't negatively impact Service Level.

    So preferences influence outcomes, but coverage and service targets still take priority.

    The overall idea is:
    Keep Work Plans more standardised and business-flexible, while giving agents structured ways to express constraints and preferences, without exploding the number of work patterns that need to be maintained.

    Dave, your comment about having to create more work patterns than in previous systems because of the lack of an "unavailability equivalent" really resonated, that's exactly the type of overhead we're trying to reduce.

    I'm really interested in your perspective on this:

    • Does this type of layered flexibility help in practice?

    • Would it reduce the need for bespoke patterns in your environments?

    • Or is there something still missing that forces you back toward structural customisation?

    Would genuinely value the feedback, this is an area we're actively thinking about.

    Thanks



    ------------------------------
    Andy Boland
    Product Manager
    ------------------------------



  • 7.  RE: Having practically a single work plan per agent. Good or bad?

    Posted 5 days ago

    Hi Andy.

    In the previous system we would have standard work patterns which could still be used even if an agent had a slight variation to the norm.

    for example:  A standard work plan with flexible start time of 08.30-09.30.  Agent A has an agreement to start at 9 or later every Tuesday, so we could use a recurring unavailability block on a Tues 08.30-09.00 and still apply the standard work plan rather than having to create their own bespoke work plan.

    We also used recurring unavailability to manage weekend patterns instead of rotations.  Teams work 1 weekend in 5 with agents are marked as unavailable for 4 weekends in 5. Then you could use a single work pattern covering all 7 days instead of having to use multiple work patterns and a 5 week rotation.  Historically we have tried both approaches and found the unavailability route to be the simpler option.

    Personally I would really appreciate the ability to create these recurring hard blocks.

    The option for agents to submit their own unavailable time is good, but would it be possible as an administrator to have sight of these before they are committed to the schedule?  (else I can foresee the possibility of agents making themself unavailable for every Friday late!)

    I hope this covers the questions you asked!

    Thanks



    ------------------------------
    Dave T
    RCN
    ------------------------------



  • 8.  RE: Having practically a single work plan per agent. Good or bad?

    Posted 6 days ago

    If all staff have a bespoke work pattern, then it's a huge amount of work to set up and to maintain.  if they are all inflexible patterns, then why not schedule using excel!

    We use a mix of bespoke and group work patterns for staff - depending on contracted shift length and whether they have any agreed variations to their working pattern.

    We have had to create a lot more work patterns in Genesys than in the previous system (starting with a V) as there isn't an equivalent to the unavailability that the previous system has.



    ------------------------------
    Dave T
    RCN
    ------------------------------