Skip to content

Quality

Categories

JUMP TO ANOTHER FORUM

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

58 results found

  1. We created a few Skipping Categories that were relevant at the time but no longer have any use case. It would be helpful to either delete or archive these categories so the dropdown list of all selectable items becomes short and "clean" again.

    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

    Acknowleged  ·  0 comments  ·  Workloads  ·  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. When using a Standalone workload, the ticket ID input doesn't pull up the interaction in Playvox so analysts can't use the full scoring features, like highlighting text. This results in longer evaluation time and less specific feedback

    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

    Acknowleged  ·  0 comments  ·  Workloads  ·  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. Assign not the # but percent of evaluations, like 5% per previous week

    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

    Acknowleged  ·  0 comments  ·  Workloads  ·  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. Add the ability to substitute a manually located interaction ID into an existing workload. When workload generated interactions aren't within scoring parameters, the substituted interaction will count as an evaluation in that workload. This would make Workload Reporting display an accurate % of evaluations completed.

    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

    Acknowleged  ·  1 comment  ·  Workloads  ·  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. When workloads are assigned to specific agents within a team, but not the entire team, it's difficult to figure out which agents don't have interactions available, but are supposed to.

    In the image of agent assignments, the first two 0/0 are on the team, but were never added to interaction assignments in the workload configuration. An agent who was added to assignments and should have 4/4 but has 0, will also show as 0/0. Adding a clear distinction of who is missing interactions will make it much easier to follow up.

    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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Want to delete workloads that not needed anymore (or have like a trash button) https://flmst.net/s/2ZHqMarjHdPFXmR/preview

    Without assignments deleted immediately. They are annoying.

    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

    Acknowleged  ·  1 comment  ·  Workloads  ·  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. When you're skipping one chat/ticket in workload, another one is not
    loading instead of skipped one, and that reduce the total amount of chats.

    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

    Acknowleged  ·  1 comment  ·  Workloads  ·  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. Need ability to delete an individual assigned workload, not just the entire workload. We can the, delete workloads with incorrect sampling, update the workload and then rerun the workload.

    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

    Acknowleged  ·  1 comment  ·  Workloads  ·  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. That the workload stops completely, when the end date is reached. Although no more interactions are assigned, currently the status of the workload is still "Live" and analysts can enter that workload and complete the evaluations, the idea is that the workload will stop completely when an end date is set.

    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

    Acknowleged  ·  0 comments  ·  Workloads  ·  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. Currently we can see the completion of all workloads within Playvox, but only up until "Last quarter" - we want to track this data for a whole year if possible to evaluate the yearly performance of an analyst (did they complete all workloads in time, etc.).

    Currently this is only possible using API data, so an Export functionality would be a lot simpler to implement. Or maybe allow a custom date range for Workload filters.

    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

    Acknowleged  ·  1 comment  ·  Workloads  ·  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. Currently, workloads that are scheduled to run daily will run everyday. We do not have the ability to restrict workloads from running on certain days. If, for example, all of our QAs are off on weekends, we want to be able for the workload to not run on Saturday or Sunday.

    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

    Acknowleged  ·  2 comments  ·  Workloads  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Ability to snooze assignments or set as 0% so the QA doesn't have to be removed from the workload if they are OOO.

    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

    Acknowleged  ·  1 comment  ·  Workloads  ·  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's very difficult to determine what percentage has already been assigned amongst QAs in the workloads. With 40+ QAs, it is very difficult how many more percentage has to be assigned/deassigned to reach 100%

    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

    Acknowleged  ·  0 comments  ·  Workloads  ·  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. Currently the Workloads API can only return information of workloads that have ran. If scheduled workload information is retrievable, it will help with sampling and managing the workloads before it runs.

    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

    Acknowleged  ·  0 comments  ·  Workloads  ·  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. When an Analyst is added / removed from a workload, it redistributes the evaluations equally amongst all Analysts. This requires us to take note of existing distribution and then recreate them. It should not reset distribution by default and users should be able to click on a button to reset it if needed.

    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

    Acknowleged  ·  0 comments  ·  Workloads  ·  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. Evaluations assigned via workloads should be showed to Analysts in chronological order, with older first and newest last. If we do weekly evaluations, then the time gap between ticket resolution to evaluated can be up to 13 days.

    Ex.
    Ticket resolved on Aug 1st, 2022
    Ticket assigned to Analyst on Aug 8th, 2022 via workloads.
    Analyst evaluates ticket on Aug 14th, 2022.

    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

    Acknowleged  ·  0 comments  ·  Workloads  ·  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. When an evaluation gets deleted, it marks it as "Not Evaluated" for the analyst, impacting their completion rate. It should not impact their completion rate if deleted. It's sometimes out of QA's control.

    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

    Acknowleged  ·  0 comments  ·  Workloads  ·  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. We would really benefit from being able to run a report to confirm any agents that are NOT allocated to a workload.

    It is confirmed via User Management if an agent is assigned to an active workload, so there is some kind of link of this data in the system.

    Going forward and extension to this request would be to be able to export a report that lists all agents and what workloads they are allocated to.

    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

    Acknowleged  ·  0 comments  ·  Workloads  ·  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. Allow the Interaction ID field to display as it is set in the filter. If you set to display the case number, it shows the case number on the workload interaction and not the interaction ID.

    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

    Acknowleged  ·  1 comment  ·  Workloads  ·  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. To be able to delete massively workloads insted of one by one.

    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

    Acknowleged  ·  0 comments  ·  Workloads  ·  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?