31 results found
-
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 -
Edit Super Admin Custom Fields
Allow Super Admin to edit other Super Admin user's custom fields. I recently needed to move a Super Admin to a new job code (via custom field) and I was not able to edit anything.
2 votes -
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 -
Central To Do List
Would be great to have a spot for users to see across the different products what they had pending and needing to look at. For leads, something that showed their assigned disputes, upcoming coachings, recent evals for their teams, and any learnings they have assigned, unread notifications, etc. For agents, upcoming coachings, recent evals, currently assigned learnings, pending disputes, unread notifications, etc. It can be extremely challenging to manage the different items requiring attention across multiple products within Playvox,
4 votes -
Make saving/updating UX consistent
The saving/updating behavior is inconsistent across the platform. Some edits are saved automatically (ex. Scorecards) but some require me to click "Save" to make the changes (ex. Teams).
For filters, some places require us to click "Done" whereas in other places is not required.
2 votes -
Dark Mode
Have a dark mode option within Playvox
7 votes -
Ability to add more than 60 team leaders to a team
Ability to add more than 60 team leaders to a team.
3 votesHi 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
-
Option to complete delete users from Playvox
Currently there is only an option to deactivate users. However, if there are issues with SSO provisioning users need to be removed completely. The only way to do this is via Playvox support which takes time and hurts our internal SLA for issue solving and means that users might not be able to use PlayVox on time/when needed.
If at least Super_Admins had the option to completely delete users, this would solve that issue.2 votes -
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?