Skip to content

Workforce Management

Categories

JUMP TO ANOTHER FORUM

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

487 results found

  1. Improve or enforce stricter rules around how long a task can be. Currently the generation will create tasks in the 15-30 minute range surrounded by other tasks. If we can enforce a task should be X amount of time at a minimum this will reduce manual work for adjusting these small tasks.

    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  ·  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)
  2. Business metrics available on the Playvox landing page after login are based on Team.

    A user must currently be a member of a team for the team’s configured Business Metrics to display to them.

    This improvement requests that Business Metrics configured for a Team also appear for the team leader and the team manager.

    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  ·  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)
  3. Clear review of over/understaffing forecasted / The ability to export Forecasted HC vs Required HC at different intervals instead of just 15 mins (i.e. 30 min, hourly, daily, 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

    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)
  4. It would be great if we could see accurate team information when drilling down into User / Date in the report.

    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)
  5. Have the ability to restrict access to the user management page to only the agents in the Groups/Teams you are granted access to
    Also to add an override permission for the Super admins who should be able to see all users (Similar to the override for manage roster)

    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. We have some existing customer who already run a 4 week roster but with smaller user numbers, running a 4 week roster is not great once you have more than 100 agents involved. We should restrict the current 'Frequency / Duration to generate roster in (Weeks)' drop down (which currently allows up to 8 weeks) to 2 weeks for all new site builds if that is possible.

    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. 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)
  8. 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)
  9. 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)
  10. 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)
  11. 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. 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)
  13. 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)
  14. 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)
  15. 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)
  16. 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)
  17. 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)
  18. 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)
  19. 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)
  20. 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)
  • Don't see your idea?