58 results found
-
Allow more than 1000 interactions when sampling by quantity
"Create the Total Sampling Using: Quantity" sampling does not allow a number bigger than 1000
3 votes -
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 -
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 -
Ability to set a fixed number in a workload to analyst's distribution.
Currently, the analyst distribution step in a workload only lets us distribute a percentage of the estimated interaction volume to be assigned. We need to be able to set a fixed number for each QA analyst to distribute the estimated volume. That way, across multiple workloads every week we can determine their total assignment.
13 votes -
See the drafted version of the evaluation they started earlier on the actual workload
Whenever the analyst is completing a workload, the client would like to see the drafted version of the evaluation they started earlier on the actual workload without needing to go to the "draft" tab. Also, to avoid confusion the client would want to have only one draft per ticket/ evaluation and not multiple for every time he saves that same evaluation as a draft.
5 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 -
Evaluations increase or decrease based on QA score
The client would like to have automated workloads. The number of evaluations increases when the agent's overall QA score is low and the number of evaluations decrease when the agent's overall QA score is high.
9 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 -
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 -
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 -
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 -
Workload Open Queue
Currently, Workloads assign a static list of evaluations per analyst. This is not an efficient workflow for larger teams.
A setting which ran workloads without analysts assignments would be helpful. The workload would run with the typical date, frequency and filter settings, but instead of assigning lists for each analyst, the user would add their analysts and allow them to work from an open 'bucket' of interactions.
Analysts would take ownership of an interaction by completing the evaluation and it would be removed from the open queue of interactions.
Users would be able to see which analysts completed evaluations and…
14 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 -
Substitutions for Multiple Analysts
Redistribute evaluations across multiple analysts (Team Leaders etc.) for both the substitutions (on PTO) & the re-assignments
19 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 -
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 -
"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 -
Workload connected to multiple filters
We need to discover how choosing more than one filter will work with the sampling
Workloads : Multiple Filters.Assign multiple filters to a Workload to capture omni-channel tickets. (Chat, email, phone). Current work around is to create a workload for each channel. Not scallable. Also, some of our agents work on calls, chats and email. By creating 3 workload, we evaluate some of them more than the scheduled evaluations number to reach.
Assign multiple filters to a Workload to capture omni-channel tickets. (Chat, email, phone). Current work around is to create a workload for each channel. Not scallable.
Two parts.…
23 votes
- Don't see your idea?