34 results found
-
Web trends through each module
It would be beneficial to see how many times each user clicked and spent time in each module. This would allow us to see if:
- more frequent check of perfromance data increases overal performance
- if agents are spending enough time in coaching sessionsThis would help us to Excellerate performance, track trends and find the most optimal use of each module
1 vote -
Warning message when leaving a running evaluation
Sometimes it happens that you click the wrong way during an ongoing evaluation and leave the evaluation. It is super annoying to find the started evaluation again and all entered answers are gone. Here you need a warning message or an additional confirmation like: "Do you really want to leave the evaluation?
As you can see on my screenshot, the button "Chats" is close to "scorecards" etc. so its easy to missclick1 voteHi there!
Thank you for sharing your valuable ideas with us!
We appreciate your input and believe that every idea contributes to making Playvox even better.
We at the Product Team regularly assess and prioritize features based on user feedback. Rest assured that your idea will be carefully evaluated alongside others. If it gains traction among our user community through votes, it could significantly influence our development roadmap.
Thanks for being a valuable part of our community.
Karina from Product
-
Ability to edit all fields of "cloned Users" profiles OR Ability to access the original user profile and edit it
We have experienced in the past the following problem: The system allows to create a user profile even if it already exists, this is called "cloned user", however we cannot edit certain fields of the cloned user profile neither can we access the original user and edit from there. Solution: Ability to edit those fields in the profile of either the cloned user or the original user, or inability for us to create "cloned users" (unless cloned users are needed for another purpose).
1 voteHi there!
Thank you for sharing your valuable ideas with us!
We appreciate your input and believe that every idea contributes to making Playvox even better.
We at the Product Team regularly assess and prioritize features based on user feedback. Rest assured that your idea will be carefully evaluated alongside others. If it gains traction among our user community through votes, it could significantly influence our development roadmap.
Thanks for being a valuable part of our community.
Karina from Product
-
Export options
An ability to export data within workloads - Example for skipped interactions. Be able to export what cases are being skipped and why to send to teams that are not in playvox (WFM teams/vendors etc).
1 voteHi there!
Thank you for sharing your valuable ideas with us!
We appreciate your input and believe that every idea contributes to making Playvox even better.
We at the Product Team regularly assess and prioritize features based on user feedback. Rest assured that your idea will be carefully evaluated alongside others. If it gains traction among our user community through votes, it could significantly influence our development roadmap.
Thanks for being a valuable part of our community.
Karina from Product
-
Access to an overview of all roles and their access
It would be super helpful to be able to view a table of all roles and what access they each have as an overview, rather than having to go in and out of every role to see who does and doesn't have access, especially when I'm overseeing several instances of Playvox across different countries, a table for each country would make these tasks much quicker.
1 vote -
Bulk update without limit
Bulk updates are limited to a total of 300 agents in the same file which isn´t a sufficient amount for our BPO groups so we have to update one group through several files what makes it very inefficient.
1 vote -
View Employee ID field in the Edit User section and in the Manage Users table
Employee id field is available and can be filled in the User Details section but is not visible in the Edit User page after saving it. We need to enter again in the User details section to view it. Moreover, the field is not available to display in the Manage Users table, even if it's included in the .xls file after data export.
1 vote -
Do not use ALL CAPS
All caps being used throughout the platform impacts readability.QAs especially struggle reading feedback options as they are all caps. The only place all caps might be suitable are headers and titles.
1 vote -
Make sorting order of teams consistent
How Teams are sorted is inconsistent between pages. Evaluations page, Reports page, User settings page in User Management, and Teams settings all have different sorting order. Make it consistent in alphabetical order
1 vote -
Ability to grant multiple roles to a user
Sometimes there is a sudden need for a user to perform responsibilities of two roles (ex. Analyst and Arbitrator) temporarily. We have to either create a new role or update the existing role to enable it, with the latter impacting all users. It will be great if we can assign multiple roles to a user, with the higher permission of either role superseding the lower permission. It'll also make role management much simpler.
1 vote -
Ability to distinguish users with same name
We have many users who share the same name but they cannot be distinguished throughout the platform. There should be a way to also view their usernames so we can select the appropriate users.
I attached a list of users who share the same name on our platform.
1 vote -
Roles
Team Leaders added to 'All Users' should obtain access to all agent reports. This is specifically useful for QAs who need access to all agent reports.
1 vote -
Include Playvox user ID as seen in the URL when exporting active users
When exporting active users in User Management, it would be useful for it to include the user ID as it is seen in the URL (e.g. the user ID for this profile https://nubankmx.playvox.com/user-management/61f9ab92f605f7 , would be 61f9ab92f605f7 )
1 vote -
Fix Group push from Okta to Playvox
We have provisioning set up in our Okta application integration with Playvox and have created a number of Okta groups that need pushing to the Playvox tenant too. Currently this fails with an error below.
We've had a call with support and this requires some product work and a new endpoint to be enabled to allow for group push.
"Forbidden. Errors reported by remote server: Invalid JSON: Unexpected character ('<' (code 60)): expected a valid value (JSON String, Number, Array, Object or token 'null', 'true' or 'false') at [Source: (String)"<html><title>403: Forbidden</title><body>403: Forbidden</body></html>"; line: 1, column: 2]"
1 vote
- Don't see your idea?