This is a valid concern, and I agree that the main issue is not the initial 0-hour request itself, but what happens later when the agent's work plan changes and the request becomes paid time off without being revalidated against the time-off limits.
From an operational standpoint, I would expect the request to be rechecked when the underlying schedule/work plan changes and the request moves from 0 paid hours to paid time. Otherwise, the original auto-approval can bypass the staffing/time-off limits that would normally protect coverage.
A few things I would look at or recommend:
- Review whether your time-off plan or auto-approval rules allow requests on non-working days, and whether those should be limited or require manual review.
- Consider disabling auto-approval for partial/non-working day requests if there is a risk that work plans frequently change afterward.
- Build an operational review process for agents who have approved time off during future schedule/work plan changes.
- Raise this with Genesys Support as a product behavior issue, because the system should ideally revalidate the request when paid hours are recalculated.
- Submit or support an enhancement request for automatic revalidation when a previously unpaid time-off request becomes paid due to a work plan or schedule change.
In my opinion, the cleanest solution would be for Genesys Cloud to either re-run the time-off limit validation when the work plan changes, or flag the request for supervisor review before it becomes paid time off. That would avoid the poor agent experience of having something approved and then later manually denied, while still protecting staffing requirements.
------------------------------
Jonathan Nolan
President, Dunamis Consulting Inc (DCX)
jonathan.nolan@getdunamis.com------------------------------