57 results found
-
Report that lists any agents NOT allocated to a workload
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 -
List assigned evaluations in chronological order
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 -
Workload - Interaction ID
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 -
New type of sampling -> Percentage or exact number of evaluation by team
We'd like to have an additional type of sampling function based on the "Percentage or exact number of evaluation by team", not by team member or by filter as these are the options available now.
6 votes -
Large Team Workload Automations
Create a more efficient way for larger groups of analysts to be updated & managed within workload creation & edits as team changes happen
6 votes -
Show percentage already assigned in workload settings
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 -
Add scheduled workload data to Playvox API
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 -
Add the ability to approve or remove the ability to skip interactions in WL
Analysts are skipping interactions that they consider too hard, too long or too low scoring and don't want to score, approving will make it easier to track
5 votes -
To be able to delete massively workloads insted of one by one.
To be able to delete massively workloads insted of one by one.
2 votes -
Do not reset evaluation distribution percentage everytime Analyst is added / removed from Workload
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 -
Remove deleted evaluations from workload report
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 -
Updating the "created by" assignment or edit access for current workloads for other admins to be able to edit
Would be great to have the ability for Super Admin to update edit access on particular workloads to new admin(s) to access/edit vs creating brand new ones for select teams (and vs updating permissions so they can access all workloads for editing).
OR ability for new admins assigned as team leaders to be able to access existing workloads tied to their team created by other/previous team leaders.There's quite a bit of transition at points throughout the year with admins/team leaders and having to create new workloads that new admins are able to edit for their team is pretty tedious.…
2 votes -
Backlog Completion Settings
If a workload is not completed before a new assignment is distributed, analysts are unable to work on the previous items that were assigned to them and can create a gap in work that QA needs to complete. This must manually be captured and completed outside of the workload.
Would love to see the ability to complete the previous assignment and/or have the functionality to catch this and the future assignment to reflect what was missed. This will ensure that there are no gaps from a controls perspective
2 votes -
"Live" workloads, not looking at past interactions
Currently you need to set up workloads based on past interactions, I can't set up a workload to find one call randomly per agent for calls taken this week unless I re-assign a workload everyday and still the analyst will need to keep note on who've they've evaluated and who they haven't
4 votes -
automated workload
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 -
Workload progress bar color
It would be great if the color of the progress in the workload can be different in different statuses. So that we can easily identify completed workload from workloads in progress. I have attached an exemplary screenshot. When the workload is 100% the progress bar turns green.
2 votes -
Filter Improvement: Agent Must Have Had 2+ Interactions on a Thread
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
- Don't see your idea?