Workforce Engagement Management

 Hi Mike,

Time-off requests affected by restricted activity codes do not enter the waitlist because the system treats restricted activities as a preliminary condition that must be cleared before the request can be queued. Agents whose requests satisfy this condition are allowed to submit successful auto-approved requests, potentially consuming the available time-off allowance. As a result, the latter requests were automatically approved, using up the day's allocation.

In this scenario, the admin has two options:

1. Deny the request: No time-off hours will be allocated.
2. Approve the request: The request will count against the time-off limits, and the hours will be deducted from the available time-off balance.

------------------------------
Nilesh Patil
------------------------------

Hi,

The risk of the allowance being used up by other people is too large. We've turned this function off as it doesn't work in the way I'd expect it to do so.

Thanks

Mike

 Hi Mike,

Time-off requests affected by restricted activity codes do not enter the waitlist because the system treats restricted activities as a preliminary condition that must be cleared before the request can be queued. Agents whose requests satisfy this condition are allowed to submit successful auto-approved requests, potentially consuming the available time-off allowance. As a result, the latter requests were automatically approved, using up the day's allocation.

In this scenario, the admin has two options:

1. Deny the request: No time-off hours will be allocated.
2. Approve the request: The request will count against the time-off limits, and the hours will be deducted from the available time-off balance.

------------------------------
Nilesh Patil

Is your expectation that a request with a restricted activity code be waitlisted and suspend any waitlist progression until approved/denied? For that the blocking of the waitlisted requests that do not have restricted activity codes would be terribly undesirable by the majority of users.

Hi,

The risk of the allowance being used up by other people is too large. We've turned this function off as it doesn't work in the way I'd expect it to do so.

Thanks

Mike

 Hi Mike,

Time-off requests affected by restricted activity codes do not enter the waitlist because the system treats restricted activities as a preliminary condition that must be cleared before the request can be queued. Agents whose requests satisfy this condition are allowed to submit successful auto-approved requests, potentially consuming the available time-off allowance. As a result, the latter requests were automatically approved, using up the day's allocation.

In this scenario, the admin has two options:

1. Deny the request: No time-off hours will be allocated.
2. Approve the request: The request will count against the time-off limits, and the hours will be deducted from the available time-off balance.

------------------------------
Nilesh Patil

Hi,

Yes that would be my expectation and how it worked on a previous WFM system we used, further requests would sit behind it until it was reviewed. Could an option/toggle to waitlist conflicting requests be created to cover those that want it and those that won't?

thanks

Mike

Is your expectation that a request with a restricted activity code be waitlisted and suspend any waitlist progression until approved/denied? For that the blocking of the waitlisted requests that do not have restricted activity codes would be terribly undesirable by the majority of users.

Hi,

The risk of the allowance being used up by other people is too large. We've turned this function off as it doesn't work in the way I'd expect it to do so.

Thanks

Mike

 Hi Mike,

Time-off requests affected by restricted activity codes do not enter the waitlist because the system treats restricted activities as a preliminary condition that must be cleared before the request can be queued. Agents whose requests satisfy this condition are allowed to submit successful auto-approved requests, potentially consuming the available time-off allowance. As a result, the latter requests were automatically approved, using up the day's allocation.

In this scenario, the admin has two options:

1. Deny the request: No time-off hours will be allocated.
2. Approve the request: The request will count against the time-off limits, and the hours will be deducted from the available time-off balance.

------------------------------
Nilesh Patil

Hi,

Yes that would be my expectation and how it worked on a previous WFM system we used, further requests would sit behind it until it was reviewed. Could an option/toggle to waitlist conflicting requests be created to cover those that want it and those that won't?

thanks

Mike

Is your expectation that a request with a restricted activity code be waitlisted and suspend any waitlist progression until approved/denied? For that the blocking of the waitlisted requests that do not have restricted activity codes would be terribly undesirable by the majority of users.

Hi,

The risk of the allowance being used up by other people is too large. We've turned this function off as it doesn't work in the way I'd expect it to do so.

Thanks

Mike

 Hi Mike,

Time-off requests affected by restricted activity codes do not enter the waitlist because the system treats restricted activities as a preliminary condition that must be cleared before the request can be queued. Agents whose requests satisfy this condition are allowed to submit successful auto-approved requests, potentially consuming the available time-off allowance. As a result, the latter requests were automatically approved, using up the day's allocation.

In this scenario, the admin has two options:

1. Deny the request: No time-off hours will be allocated.
2. Approve the request: The request will count against the time-off limits, and the hours will be deducted from the available time-off balance.

------------------------------
Nilesh Patil