Skip to content

Workforce Management

Categories

JUMP TO ANOTHER FORUM

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

500 results found

  1. Tie this into the leave summary and potentially provide comprehensive insights into:
    - reporting leave taken in relation to thresholds
    - trends surrounding leave thresholds
    - identification of calendars with approvals continuously exceeding threshold limits,
    - monitoring users approving leave beyond the defined thresholds.

    0 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

    Acknowleged  ·  0 comments  ·  Leave Management  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Systematically track and flag users who repeatedly approve leave requests beyond the defined leave thresholds. This monitoring would ensure that leave management processes remain aligned with organisational policies and resources.

    0 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

    Acknowleged  ·  0 comments  ·  Leave Management  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Introduce a field or functionality to allow users to establish and uphold limits on the quantity of agents (leave requests) permitted to surpass the defined leave thresholds. Presently, team leaders or managers possess the authority to override the leave thresholds by manually approving leave requests.

    Implementing a mechanism to regulate the count of leave requests that surpass a predefined threshold would be advantageous to customers who have a global workforce with multiple calendars.

    Additionally, integrate tie this feature in to permissions, ensuring that only designated users possess the ability to access and define this capability.

    0 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

    Acknowleged  ·  0 comments  ·  Leave Management  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. This will allow for Shift swapping of RDO shifts that have been generated by a manager - currently these create a leave request and cannot be swapped. RDO is also not classified as Leave, it is a rest day so should be a non-productive task rather than leave.
    This must not impact the ability for the roster to generate RDOs as part of roster generation

    0 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. 0 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. Could we consider switching the roster access permission to System role e.g. all admins can see this roster, could it be multi-select?

    0 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)
  7. It would be great to allow a calendar event to be rotated through a selected group of agents. At present you can only do an event rotation using the demand based events which can schedule around breaks and shrinkage tasks. Use case is that I need to create a calendar event for just one person per day for 4 hours but this is not possible as a calendar event cannot overwrite breaks and the schedule rules mean that breaks are added before events so the event a) does not work due to the fact that there is always a shrinkage…

    0 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)
  8. Example: from Polygroup
    Team A
    Week 1 Phones/Email M,W,F and Back Office Tu,Th
    Week 2 Phones/Email Tu,Th and Back Office M,W,F
    Team B
    Week 1 Phones/Email Tu,Th and Back Office M,W,F
    Week 2 Phones/Email M,W,F and Back Office Tu,Th

    0 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

    Acknowleged  ·  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)
  9. We spend a ton of time creating overrides for different workstreams or sets of workstreams. Sometimes we'll be creating overrides different overrides for 12 months, each of which covers 16 workstreams that we have to create over different scenarios, which leads to hundreds of clicks and hours of time. So much time would be saved if we could duplicate scenarios and overrides and then just make the small edits to dates/percentages.

    0 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

    Acknowleged  ·  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)
  10. Removes the workaround of sending reset links to external system when emails are not active
    Handy: We will have a bunch of new agents coming/going soon. It'd be nice to highlight a bunch of agents and do a batch password reset/schedule template update. Instead of going through them one by one

    0 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)
  11. Currently a deleted team is not visible in admin and users just see a generic error message if they try to create a team that contains the same name. Engineering is required to reinstate or rename to allow the new team to be created.

    0 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. Universally known terminology would be simpler to explain to onboarding customers. Matches majority of CRM and Telephony skills based terminology

    0 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)
  13. We need an option on the Forecast Configuration UI for users to choose if they want to COMBINE (default) SLA when calculating forecast workstream by workstream, or to not combine.

    The reason we need this is because workstreams can have different SLAs so if you combine / don't combine it changes the staffing requirement noticeably.

    0 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  ·  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)
  14. This is not the same as first answer on a ticket, but rather how it takes an agent to publically update a ticket once it has been assigned to them. This assignment can happen at any point during first answer, first resolution or re-opening, etc.

    0 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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. It would be really helpful if some of the metrics available on Performance Summary could link through to a pre-filtered list on Workstream Details so I can get an understanding of what data is generating the metric.

    For example, I would love to be able to click on the 'Abandoned' metric on Performance Summary and be taken to the Workstream Details page, where a filter is already applied to show me all the abandoned workstreams over the date range I had selected.

    0 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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. It would be great to be able to see the actual amount of overtime worked vs. the rostered overtime in the Schedule Summary report.

    Right now we can only see the rostered overtime in Schedule Summary

    0 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  ·  Reporting  ·  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. It would be nice to filter pages like Performance Summary and Leave Summary by location, particularly for location-based teams.

    0 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  ·  Reporting  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Playvox WFM doesn't currently flag users who never log into a shift as out of adherence (as it's supposed to be an unplanned absense).

    It would be nice to have the option to flag users who don't login as either out of adherence or have an associated unplanned leave type so it's easy for managers to identify and follow up on in reporting.

    0 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  ·  Reporting  ·  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. Add insights to Playvox WFM that allow us to see:

    • When a workstream was assigned to a particular group / queue

    • How many workstreams are assigned to a particular group / queue

    • When a workstream was first updated / the average time it takes for a workstream to receive its first update after it was assigned to a particular group / queue

    • When a workstream had its first public reply posted / the average time it takes for a workstream to have its first public reply posted after it was assigned to a particular group / queue

    0 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

    Acknowleged  ·  0 comments  ·  Reporting  ·  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. The names suggested are:

    1. Updated time --
      This is the timestamp of the service request's last update. We can use this to help determine effort by filtering.

    2. Created by --
      This is the name of the agent who initially raised the service request on behalf of the customer. If a request is raised by a customer themselves, the field would be blank or a static value (such as 'Customer').

    Both columns would need to be filterable.

    0 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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
1 2 21 22 23 25 Next →
  • Don't see your idea?