Ability to configure maximum overlapping time off requests by seasonal period
B
Bellflower Raccoon
We operate with distinct peak and non peak seasons, and based on these seasons, we need the ability to configure maximum overlapping time off requests differently depending on seasonal periods.
Current limitation:
- Maximum overlapping time off rules apply globally.
- There is no date range or seasonal logic.
- Only individual dates can be manually selected.
Desired functionality:
- Define seasonal date ranges (for example July to September and December to February).
- Apply stricter maximum overlapping limits during peak.
- Allow more flexibility during non peak months.
- Configure per team if necessary.
Example:
- During peak season: maximum 2 agents off per team.
- During non peak: up to 5 agents off per team.
Business impact:
- Aligns time off approvals with operational demand cycles.
- Reduces manual rule adjustments throughout the year.
- Improves capacity protection during high volume months.