Workforce Management

It would be very nice to be able to offer Voluntary Time Off Slots for all channels or for multiple channels at a time.

Would be a great feature in the “add multiple agents” option, if one could type the associates schedule to filter and select. for example entering “sun” would allow to schedule all sunday associates without having to go down the list and select associates one by one, or selecting all and then having to go through the schedule to delete some events." "for example in the search box, you could type “John” the search world return every agent named “John” and you could “select all” to add the same event for all of the “johns”. The same functionality would be helpful if that search box recognized schedules, you can see by my name in the screenshot it says (Sun-Thurs), so if I could type “sun” to sort and select everyone that is on the “Sun-Thurs” schedule, that would be a great benefit.

Submit schedule change requests for multiple agents at once (e.g., for a team meeting), rather than being limited to one agent per request.

We have agents trained in multiple queues, but when extra work slots are made available for more than one of these queues for the same hours/intervals there does not appear to be an option for the agent to select which workflow they would like to request. It defaults to one of the options, which may not be the correct queue. Being able to select which type of workflow to request would make this tool much more robust and usable for our teams. Thanks!

I should be able to set the default option to "Just this once" when editing a recurring meeting, so I don't have to manually select it every time I make a change.

Description: We need a way to schedule multiple 1:1 meetings between two groups based on their availability in Assembled. Currently, we export CSV timelines and manually map availability in spreadsheets, which is time-consuming and quickly falls out of date. Desired feature: Select two groups, specify number of meetings needed per person and duration, then have Assembled suggest or auto-schedule meetings based on overlapping availability and create calendar events. Sample use case: We need everyone in group A to meet with everyone in group B once.

The error message for scheduling conflicts (when you're trying to create a template) are not useful for a few reasons: It tells you to fix the errors, but you have to exit out of the window to fix them You can't see the entire list, which means you have to manually go through, line by line, to fix the issues The error bar is very small and red, and often impossible to see without expanding the layers. Solution: Have a button you click that takes you to each error and has you address it.

Assembled should allow schedule requests to be automatically routed to specific approvers based on event type (e.g., “Interviewing” requests → James, “Onboarding” requests → Claire), in order to ensure the right leads review the right types of schedule changes. Currently, all schedule requests route to a single designated approver or require users to manually select approvers. For large or cross-functional teams, this creates inefficiency and increases the risk of missed or misrouted approvals. Adding configurable routing logic by event type, tag, or role group would help: • Reduce manual triage for admins who manage multiple functional teams • Ensure accountability by aligning approvals with subject matter experts or team leads • Improve visibility and accuracy of approvals for different types of work (training, admin, clinical, etc.) This would be especially valuable for organizations with multiple departments or distinct scheduling categories that require separate oversight.

We would like the ability to change the length of the VTO blocks offered. E.g. someone has to sign up for a minimum 3 hours. Today, they are based on your company's interval on the Staffing Timeline.

Ability to configure auto-scheduled breaks and events to occur only at specific time intervals (e.g., every 15 minutes — :00, :15, :30, :45), so that schedules remain optimized but operationally consistent and easy to communicate.