38 results found
-
Dark Mode
Have a dark mode option within Playvox
7 votes -
Mandatory date formatting when adding new users
Currently this can be a string of random numbers or different formatting for dates. Hard to manage start times this way. Ideally this would be a calendar pop-up so all users start dates are formatted the same on the export.
1 voteGreat news! 🎉 Your idea is moving forward!🎉
Supporting custom date fields is now part of our roadmap. We're excited to bring your vision to life and appreciate your valuable contribution.
Stay tuned for updates as we work to make it a reality!😊
Karina from Product
-
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
-
To stop new users being automatically added to the All Users 'team'
Its very time consuming and frustrating to have to remove everyone from 'All Users' everytime we create new accounts, along with manually sending invites, its another step to the process.
We don't want the All Users team, but have been told we have to have it, yet we remove everyone from it, can all users going to this team be an option rather than automatic?
2 votes -
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 -
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 -
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 -
Automatically send new accounts an invite
At present its a painful process to create accounts and then have to manually go into another screen to send them an invite.
Could there be a field to click to automatically send an invite when the account is created? Or when you bulk create new accounts there would be another column confirming to send an invite automatically?
Or even the ability to sort the 'Pending invitation' list in to 'send invite' and 'resend invite'?
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 -
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 -
Add deleted evaluations data to Playvox API
Playvox API doesn't have information on which evaluations were deleted. Thus we cannot efficiently removed deleted evaluations from our internal database. The team has to recurrently compare the Playvox and Internal datasets and remove those not present in the Playvox dataset. This is resource expensive.
2 votes -
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 -
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 -
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?