Settings and activity
28 results found
-
5 votes
dleite supported this idea ·
-
5 votes
dleite supported this idea ·
-
5 votes
dleite supported this idea ·
-
14 votes
Exciting news! 🎉 Your idea is moving forward!
We’re thrilled to bring your vision to life and deeply value your contribution.
Stay tuned for updates as we make it happen! 😊
dleite supported this idea ·
-
2 votes
dleite supported this idea ·
-
10 votes
dleite supported this idea ·
-
2 votes
dleite supported this idea ·
-
3 votes
dleite supported this idea ·
-
12 votes
dleite supported this idea ·
-
3 votes
dleite supported this idea ·
-
5 votes
dleite shared this idea ·
-
6 votes
dleite supported this idea ·
An error occurred while saving the comment -
8 votes
dleite supported this idea ·
-
5 votes
dleite supported this idea ·
dleite shared this idea ·
-
12 votes
dleite supported this idea ·
-
6 votes
dleite supported this idea ·
-
8 votes
dleite supported this idea ·
-
14 votes
dleite supported this idea ·
-
14 votes
dleite supported this idea ·
-
22 votes
🚀Exciting News: Your input is shaping our product!
Coming soon, the Section and Question reports will allow you to filter and analyze data using:
- Scorecard header custom fields
- Section custom fields
- User custom fields
We can't wait for you to experience this enhancement firsthand!
dleite supported this idea ·
Current workload assignment:
We based the assignment per team member(individually).
Type of sampling -> By Team/Agent
Number of evaluations -> Even distribution per team member (see screenshot below).
For example, team X has 20 agents and we require 10 per agent for a Total of 200 interaction to be Evaluated
New/expected Workload assignment:
The new approach will be based on total interactions that will be evaluated as a team, not at the team member level.
Type of Sampling -> Percentage or exact number
Total Interactions to be Evaluated -> Assign the total number of evaluation by team regardless of the agent distribution.
For example, We need 200 Interactions to Bring From Filter by team x, in that case we are expecting an uneven distribution where some team members would have more interactions than others.
Blocker: we cannot select the team if we use the Type of sampling by "percentage or exact number". This is a problem, because we have multiple vendors working on the same Workflow (using the same Quality filter on Playvox) and we cannot differentiate them on the Quality filter level.
Therefore, we can't create a workload per "vendor + workflow" and it would cause some of our vendors to get a lower/higher number of evaluations that is against our Key Performance Indicators.