57 results found
-
Allow the ability to pull cases for 90 days
Allow the ability to pull cases for more than 60 days, such as 90 days, so can perform quarterly audits more easily.
2 votes -
Ability to substitute interactions
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 -
Workload Team Alignment and Current Week ONLY Contact option
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 -
Evaluate the analysts: Type of sampling
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 -
Workload sampling issue: creating the total sample using > quantity
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 -
Skip evalutation
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 -
Notify Analyst when standalone interaction is already assigned in Workloads
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 -
Add display of agents who are expected to have interactions assigned, but no available interactions were found
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 -
Delete or archive Workloads Skipping Categories
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 -
Ability to delete assigned workload
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.
2 votes -
Delete workloads
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 -
Allow tickets to sync from Zendesk in Standalone workloads
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 -
Ability to set the days of the week (ex. M - F) when workloads will run
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 -
Workload export functionality
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.
3 votes -
Workloads - End date
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 -
Manual agent assignment in workloads
It would be very helpful to have the option of assigning specific agents for evaluation to specific analysts. Reason: some analysts may not be fully capable of evaluating specific agents due to language barriers, etc... YES, one could technically make a separate workload for that language, but there are other instances in which this could be useful, especially if agents can be reassigned MID-WORKLOAD period (an analyst is away on vacation or is ill, etc...).
10 votes -
% (PERCENT) OF EVALUATIONS PER TEAM MEMBER
Assign not the # but percent of evaluations, like 5% per previous week
1 vote -
Ability to snooze workload for QAs
Ability to snooze assignments or set as 0% so the QA doesn't have to be removed from the workload if they are OOO.
2 votes -
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.
4 votes -
Ability to use decimals in a workload for QA assignment
We need the ability to use decimals when dividing the estimated volume to QAs in a workload. I.e. Currently, if you have 5,000 interactions estimated to be divided among 100 QAs the difference between the allocation of 1% (50 interactions) and 2% (100 interactions) is not providing a fair distribution.
5 votes
- Don't see your idea?