Workforce Management

Current behavior: When a time off request is submitted, it undergoes an evaluation process that checks various rules, including concurrent time off limits. This evaluation happens in real time at the moment of submission/approval. If multiple requests are approved very close together, they may all pass the evaluation phase before any of them are fully processed. Feature Improvement: A longer buffer/delay to allow for each request to go through the necessary checks

It would be great to be able to apply an optimization rule for a certain amount of days in the week (for example, apply a rule to just Tues-Thurs) rather than just a week or day rule. This would be helpful for scheduling non productive tasks during times of low volume.

Assembled currently does not offer an API endpoint that returns both required hours and scheduled hours. It would be helpful to have this data available via the API for reporting and tracking staffing coverage more easily.

Requesting support for the HRIS platform Deel in order to sync HRIS data (such as time off, leaves, and employee details) directly with Assembled, similar to existing integrations with other HRIS platforms. Impact: Enables seamless workforce management and reduces administrative overhead for customers using Deel.

Having the capability to filter out productivity metrics (i.e. solves per scheduled/actualhours) by event types which are multi-channel. An example would be for Overtime - we currently have an event type to track logged OT but are unable to check the productivity being accomplished during this period!

Ask: We shouldn't allow agents to submit a time off request that overlaps with a previously approved request. Or we should at least warn the approver and force them to select between the conflicting requests Why: Agents will sometimes forget that they already submitted a time off request and had it approved. Then, they will submit one that overlaps with that original request. When the second one is also approved, this creates conflicts on the Staffing Timeline that someone then has to manually resolve - this creates additional work when someone wants to save the Staffing Timeline view as a template. It also results in the double counting of 'approved time off events' in Schedule Analytics.

I should be able to customize the name of the type of Threshold I am creating

I should be able to resolve recurring scheduling conflicts in bulk for all future instances where a template has been applied, so I don’t have to fix the same conflict manually each time it appears.

I should be able to see a visual indicator (like a badge or highlight) on the left-hand menu when there is a new or pending item under 'Schedule requests', so I don’t have to click into it to discover there's something waiting.

I should be able to view reporting and analytics related to shift swaps, such as swap acceptance rate, number of shifts swapped per team or per agent, and any trends or patterns over time.