Skip to content

Quality

Categories

JUMP TO ANOTHER FORUM

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

58 results found

  1. Instead of having users randomly assigned in a workload, we'd like to see a feature that allows us to exclude certain users. For example, there are analysts who also take calls in these queues but we don’t want them to get assigned to audit themselves.

    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. Could you please add an option to create workloads to evaluate the internal comments left on the ticket by a person other than then one handling the ticket?

    Example:

    Person A is handling the ticket on Zendesk and needs help in order to solve the issue so they escalate the ticket. Person B looks at the escalation and leaves an internal comment with instructions or with the solution on the ticket and then Person A continues to solve the ticket.
    We would like to create a Workload to evaluate the internal comments left by Person B, even if the ticket…

    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. Allow to set up a workload that would allow analyst to focus on a team instead of having a distributed sampling or random agents to evaluated. This will allow the analyst to create a targeted action plan or recommendation for the specific team evaluated.
    Also, can we have an option to set up workloads to just focus on current week contacts of the agents instead of pulling data from previous week. This would allow Analyst to draw conclusion on the current behavior captured on that week instead of having to evaluate contacts for past weeks.

    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. Allow sampling by scorecard and doesn't require us to select QA Analysts names. Instead workload will pull every QA Analysts who completed an audit for that particular scorecard. Current process is challenging to add and remove QA Analyst for clients with multiple BPOs and sites.

    Additionally, Playvox blank out QAs when QAs are removed from the program but not in time to remove them from the workload list. Please see attachment

    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)
  5. Workload pulls the latest x number of interactions. Based on UAT observations, we've noticed that workload fully sampled ~15 minutes (23:45 till midnight), while ignoring remaining interactions within the 2 day time frame.

    We require random sampling to be able to use this feature.

    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)
  6. Even though every Quality Specialist has a specific distribution rate (%), same analysts have less tickets assigned than others, week after week. Ideally, Playvox would keep an eye on the overall distribution over the time of each workload to ensure that each analyst receives roughly the same amount of tickets to evaluate.

    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)
  7. When an Analyst enters an interaction ID into a Standalone workload, they should get a visual notification if that interaction is already assigned, evaluated, or calibrated so that they don't unintentionally double up on scoring and interfere with agent's QA averages.

    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)
  8. 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)
  9. 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)
  10. 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)
  11. 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)
  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. 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)
  17. The client would like to have automated workloads. Whenever the workload does not get enough samples to match the ones requested when creating it (because no other interactions match the filter and date range requirement), these missing evaluations should be added automatically to the next trigger and therefore complete the quota of established tickets to evaluate.

    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. For QA filters, it would be great to add a filter for requiring an agent to have had at least 2 interaction within a thread and/or were the last ones to have connected with the guest.

    This would help us ensure that agents we are evaluating are the ones who finished the conversation and it would help us ensure that the person we were evaluating had a substantial impact on the conversation.

    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)
1 3 Next →
  • Don't see your idea?