Skip to content

Workforce Management

Categories

JUMP TO ANOTHER FORUM

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

37 results found

  1. Our agents use the Google Chrome extension daily, throughout their entire shifts, to select from over 30 different statuses. Currently, the statuses are listed alphabetically, forcing agents to scroll through the entire list, which is time-consuming and inefficient. This process slows down workflows, particularly when handle many task during their shift.

    Introducing a search field or filter option would greatly improve efficiency, allowing agents to quickly find and select the correct status, ultimately enhancing both productivity and user experience.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. After running the "Schedule event" or "Optimise" processes, show a pop-up notification that it has finished.
    At this point there is no way of knowing whether the process is still running or not.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Scheduling  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Hello


    Thank you for sharing this idea on UserVoice! We truly appreciate your input, and our team is reviewing this suggestion as we plan future updates. While we can’t implement every idea immediately, your feedback is crucial in helping us shape the product.

    In the meantime, please keep voting on other ideas you’d like to see implemented. Your voice makes a difference!

    Thank you for being part of our community!

    Best regards,

    Fab

  3. The help center states this globally updates across the whole platform, but that isn't actually the case. After contacting Support (Ticket #32414) they told us the feature wasn't intended to perform that way, and the setting only applies to the Roster. We need this is update everything. It's very confusing having different calendar formats scattered everywhere

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. We'd like to be able to schedule changes in bulk by either having the option to schedule a import to "go live" on a certain date OR being able to make a changes to a group of users are the same time and schedule that change to go into effect on a certain date.
    This would help us ensure that things like group/team changes, schedules, availabilities, shift templates, roles, etc are done prepped for the change date without having to schedule each agent individually for that change.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. When entering time off, can we have the ability to add times outside of 15-minute intervals? Currently, if someone is say 20 minutes late, we have to submit the time off in the leave requests using a 15-minute interval and then go into the roster and update the time. It would be better if we were able to do this in one step instead of two.

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. When a shift is removed from the roster management page (sometimes in error), the all associated data is wiped out. From what I understand, "actuals and occupancy are tied to the shift ID, which is a unique ID generated by the application during roster generation." Once an agent's scheduled is mistakenly deleted the agent's schedule and shift ID are removed along with all the metric that were attached to it. When we add a schedule back to the agent, the new shift ID is created but does not marry the metrics already in process or recorded.

    This affects the agent's…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Scheduling  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Under Review  ·  Anonymous responded

    Thank you for raising this concept to the WFM team. 

    The Product Owner will review and update accordingly

  7. Right now when you add events in the roster config feature, you cannot set an end date. If I have a recurring event that will happen for just a week or a month, I would like to set it for only that week/month. As it is, I have to create the event, set it to start on the start date, and then delete it after all rosters are generated with it (and hope I don't have to regen). Alternatively, I can create separate events for each date, but this is very time consuming and leaves a lot of room for…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Scheduling  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Under Review  ·  Anonymous responded

    This item is being prioritised for development.


    We are beginning planning and will provide further updates as we understand when this item can be actioned. 

  8. Currently swapping is enabled only at the shift level (full day).
    As we are doing scheduling at the task level there is a need to have swaps done at this level, as often people swapping have different roles as it relates to the other tasks on their schedule (the ones they are not swapping).

    11 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Under Review  ·  3 comments  ·  Scheduling  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. We're in the process of pulling together the logistics of being able to generate and publish our rosters for the remainder of the year.

    However given the size of our main roster, it does take between 45/55mins to generate one and sometimes results in it timing out.

    As a potential future feature, we would love to see a Roster Generation queuing function built in to enable us to stack all the rosters we wish to generate. We'd then have them begin generating at a defined point in time (end of day/working week) so they can effectively generate in the background…

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Under Review  ·  0 comments  ·  Scheduling  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Example, Customer wants to schedule agents for 4 hours on chat then lunch and then 4 hours on tickets. Cannot be done in today's environment. This request has come up with multiple customers but as they have then churned it does not make the roadmap. Currently would be able to use this solution for an issue we have with eHealth QLD

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Under Review  ·  0 comments  ·  Scheduling  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Ability to change the leave type as agent or admin when in submitted or approved status. Currently can change to full day or partial, but we would like to see the leave type as editable too.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. The ability to allow the system to generate the FTE requirement for the workloads for Chat and Phone based on historical arrival patterns, but to also have a fixed minimum requirement (ie. 1 or 2) to protect the workstream in the event that there's no requirement to guarantee that the workstream will still have some coverage. It would be helpful to not have the min requirement to be added to the historical forecast when the historical exceeds the min requirement, but only utilize the min when the requirement based on the forecast would fall below the min. required set.

    10 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Under Review  ·  0 comments  ·  Forecasting  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Provide an event management screen that allows an overview of existing events, creating events and provide filters.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Under Review  ·  0 comments  ·  Scheduling  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Enabling filtering, sorting and grouping of leave data by configurable criteria; currently
    grouping is done by leave calendars and filtering by leave type.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. If the submitter/approver accidentally cancels a leave request, it would be great if they had the ability to un-cancel the request, rather than the person having to re-submit their time off request

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. 4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Under Review  ·  0 comments  ·  Scheduling  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Having the ability to approve/cancel leaves in bulk will allow clients of larger size to gain efficiency in this area.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. e.g. 20 hours of FTE divided up by users X,Y,Z by role. Similar to a fixed forecast but demand based

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Under Review  ·  0 comments  ·  Scheduling  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Currently the backdating feature only works once, but if a customer creates new historic tags or identifies an issue later on, they're unable to re-backdate to re-align their historical data. This means their workstreams are no longer accurate and they have to wait and go from scratch or manually bulk import new volumes. Can the feature be improved that anytime a backdate is run it overwrites the old data completely and aligns all historic data to the corresponding workstreams as if it was freshly imported for the first time.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Under Review  ·  0 comments  ·  Real Time  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Provide feedback to the agents if a leave request is likely to be approved, based on the threshold.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
← Previous 1
  • Don't see your idea?