51 results found
-
Update leaves from manage roster to be reflected on leave history
Ability to edit/delete leaves from Manage Roster which is then reflected properly in Leave History (and connectors)
1 voteThank you for taking the time to bring this feature request to Playvox.
A Product Owner will review the request for potential inclusion within the backlog / roadmap. Updates will be provided as the feature progresses.
Regards,
The Playvox Team
-
Annual Leave Threshold
Within our organisation, the normal process to adhere to if an individual is to request a period of Annual Leave in excess of 2 weeks is that they need to get approval from an Ops Manager.
However we have noticed a number of instances where individuals have requested AL above and beyond a 14day stretch which would then auto approve and plan it into roster without getting prior authorisation.
As a feature request, could something be built which would automatically put any request above any given threshold into pending approval. This would allow us to carry out due diligence checks…
1 voteThank you for taking the time to bring this feature request to Playvox.
A Product Owner will review the request for potential inclusion within the backlog / roadmap. Updates will be provided as the feature progresses.
Regards,
The Playvox Team
-
Display Updated Business Role Name in Time Off Calendar
When updating a Business Role in the Time off Calendar the new name is not automatically updated. You can see it in the drop down, but not on the display name.
1 vote -
Allows Rolling Periods for Leave Calendar Thresholds
We would love for the Leave Calendar to update thresholds based on rolling windows. For example, I would like to have the threshold set as "1" for every day in a rolling 60-day period, but 0 for anything outside of that.
1 vote -
Give Leave approval feedback to agents
Provide feedback to the agents if a leave request is likely to be approved, based on the threshold.
1 vote -
Update Leave Mgmt to align with the changes made to account for future leave / RDOs in Fixed Rotations
Roster Generation was updated for fixed rotations to ensure that future approved leaves outside of an agent's set rotation pattern for a given week were accounted for.
What we need to do now is ensure that the Leave Management side of the system is also updated to reflect the new logic in this scenario.
1 voteUnder review for prioritisation
-
1 vote
-
Introduce Reporting on Leave Thresholds
Tie this into the leave summary and potentially provide comprehensive insights into:
- reporting leave taken in relation to thresholds
- trends surrounding leave thresholds
- identification of calendars with approvals continuously exceeding threshold limits,
- monitoring users approving leave beyond the defined thresholds.0 votes -
Leave Thresholds - Capture users who are approving leave requests over threshold
Systematically track and flag users who repeatedly approve leave requests beyond the defined leave thresholds. This monitoring would ensure that leave management processes remain aligned with organisational policies and resources.
0 votes -
Leave Thresholds - Implement a limit on exceeding the defined threshold value
Introduce a field or functionality to allow users to establish and uphold limits on the quantity of agents (leave requests) permitted to surpass the defined leave thresholds. Presently, team leaders or managers possess the authority to override the leave thresholds by manually approving leave requests.
Implementing a mechanism to regulate the count of leave requests that surpass a predefined threshold would be advantageous to customers who have a global workforce with multiple calendars.
Additionally, integrate tie this feature in to permissions, ensuring that only designated users possess the ability to access and define this capability.
0 votes -
Recategorise RDO's to a non-leave task
This will allow for Shift swapping of RDO shifts that have been generated by a manager - currently these create a leave request and cannot be swapped. RDO is also not classified as Leave, it is a rest day so should be a non-productive task rather than leave.
This must not impact the ability for the roster to generate RDOs as part of roster generation0 votes
- Don't see your idea?