Assembled Workforce Management

I should be able to create a recurring event without specifying an end date, allowing it to continue indefinitely until I choose to modify or stop it.

We would like agents to receive a Slack notification when their schedule change request is approved. They are already working out of Slack, and this would eliminate the need for them to have to check their Email or Assembled to see if their request was approved.

When creating an Event rule that applies to multiple agents, it would be great to be able to select an "attendance threshold" for the rule to keep in mind. For example, I may want to set up a dynamic team meeting that will be placed at the most optimal time for the team, where at least 80% of the agents assigned to the rule can attend: They are scheduled during the window They do not have PTO or other Default events within the window This way, the system can balance FTE requirements vs shrinkage requirements in a more effective manner.

When using Schedule Assistant to generate schedules, approved PTO/time-off events are not included in the test schedule because PTO is only applied to the default schedule. This means the generated schedule doesn’t reflect agents’ time off and requires manual workarounds. Current workaround Teams must either: Manually apply a PTO template to the test schedule, or Use Schedule Generation, which automatically incorporates time-off events. Suggestion Allow approved PTO/time-off events to automatically carry over to test schedules generated by Schedule Assistant so schedules more accurately reflect agent availability and reduce manual steps.

When configuring Scheduling Rules, it would be nice if the "Assign" section allowed you to use AND conditions on assignment. For example, I may want a rule for breaks that applies to anyone in Arizona, New York, OR California, then I may want an additional break rule that applies only to teammates in Arizona AND assigned to Queue A. This would allow for more dynamic and specific assignment rules while reducing the overall amount of rules necessary for a complex organization.

Sorting the timeline by the queue/skills column doesn't group agents cleanly because most agents are assigned to multiple queues (e.g. Underclass + Spanish, Underclass + Collections). The sort treats each unique combination as distinct, resulting in agents with similar primary skills being scattered throughout the list rather than grouped together. This works correctly in the People section but not in the timeline. What's the requested change? Improve the sorting logic for the skills/queue column in the timeline so that agents with overlapping skill sets are grouped more intuitively — ideally matching the behaviour already present in the People section view.

In the timeline view, only the agent name column stays fixed when scrolling horizontally. Other columns — particularly the skills/queue column — scroll away, meaning users lose that context when looking at later parts of a shift. For agents with long shifts, the skills column may never even be in view at the same time as the relevant schedule. What's the requested change? Allow additional columns (particularly the skills/queue column) to be pinned/frozen so they remain visible when scrolling horizontally, in the same way the agent name column currently behaves.

Have a dedicated page of all recurring meetings currently scheduled where they can be adjusted in one place

Mark certain trainings as "mandatory" and have the system alert us and/or reschedule to another shift