Assembled Workforce Management

Currently, shift rules that enforce a max number of hours per X days are calculated on a rolling basis. For customers with labor laws tied to a fixed work week (e.g., Sunday-Saturday), this can cause false positives or compliance gaps. Example use case: A customer has a labor law requiring a maximum number of overtime hours per work week (Sunday-Saturday). Because our rule logic uses a rolling 7-day window, it may flag violations that don't actually exist within the legal work week, or miss violations that span across the rolling window differently than the law intends. Request: Allow admins to configure whether a scheduling rule is evaluated against a fixed calendar week (with a configurable start day, e.g., Sunday) or the current rolling 7-day window. This gives teams the flexibility to align Assembled's rules with their specific legal and operational requirements.

It's highly disappointing and feels being controlled to take breaks on a pre-decided schedule. Given the 9hr schedule is being adhered to, the little changes in break time should be auto-approved.

Problem: Shift swaps currently process without checking against scheduling/shift rules. When a swap violates a rule, the system only surfaces it post-approval via the broken rule notification, requiring a manual reversal after the fact. For customers operating under legal or regulatory scheduling constraints, this is a meaningful risk - agents don't always know the rules, and a swap that breaks labor law can't simply be undone cleanly. It also makes the swap feature feel redundant: customers either avoid using it or layer manual review on top, which defeats the self-service value. Proposed solution: Run shift/scheduling rule validation before a swap is approved. If the proposed swap would violate a rule, block it and surface the reason to the requester - rather than letting it go through and flagging it after.

While the new multi-select functionality is exciting and something we’ve been anticipating, I believe the current implementation is a bit lacking in utility and could be further improved. Blockers: You cannot enter multiple email addresses into the search box and “Select All,” resulting in a very manual and repetitive process of: a. Enter email 1 b. Select the agent c. Remove the email d. Copy/paste email 2 e. Select the agent f. Remove the email g. Repeat While this may be manageable for small populations, it makes it very tedious to update schedules for say, an All-Hands meeting that has 50+ attendees. 2. You cannot deselect one (or multiple) agents without entering their email addresses 1-by-1 and de-selecting them (unless you want to remove all agents and start over). It would be better if, open clicking into an empty "Search Agents…” box, it would show a dropdown of all agents already selected. There could also be a button directly on the timeline, maybe next to the agent name, for a “quick remove” action. Given these limitations, it is unlikely that I (personally) will leverage multi-select beyond very niche cases.

Add ability to edit an agent's scheduled events from the Real Time Analysis page without needing to navigate to the Staffing Timeline

We have agents that are available to work at any time during the day, and these agents help us cover staffing gaps. However, we have their availability listed in an excel sheet and it's time consuming to be changing from Excel to Assembled. Many tools have a section where you can let the system know the number of hours an agent can work as well as the time frames. When generating, the system schedules the number of hours at the needed times (basing on forecast).

For agents who work daily shifts of non-contiguous blocks

Make schedule change request details exportable via CSV

This request is for more granular control over which event types count toward working hours, specifically for "Shift" Scheduling Rules. Right now, all events are included - but there are certain non-productive events, like appointments, that shouldn't count towards these rules. However, there are also certain default events that should count - like meetings or paid breaks. The fact that all events count towards "Shift" Scheduling Rules can cause false positives in some cases. For example, rules like "Max X hours per day" or "Max X days per week" can end up being exceeded by certain events that don't need to be counted.

We need the ability to create scheduling rules with conditional logic that differentiates between agents extending an existing shift vs. agents picking up a new shift on a day they're not scheduled. Current Limitation: Today, scheduling rules can't check "Does this agent already have a shift scheduled on this day?" This means we cannot set different min/max hour constraints based on whether the request is extending an existing shift or creating a new one. Desired Functionality: Add a new conditional option when creating constraints: "Apply this rule when agent is [already scheduled / not scheduled] on this day" This would allow rules like: IF agent is already scheduled that day → Allow schedule change requests between 2-6 hours IF agent is NOT scheduled that day → Allow schedule change requests between 2-8 hours Both rules: Total hours per day cannot exceed 12 Without this feature, we have to: Manually review every single bonus shift request to determine if it's an extension or new shift Manually calculate whether it violates our 6-hour extension limit Deny and re-communicate correct parameters to agents who submit incorrect requests Specific example / use case: Our team offers "bonus shifts" where agents can request additional hours. We have different requirements depending on whether someone is already working that day: Shift Extensions (agent already scheduled that day): Minimum: 2 hours Maximum: 6 hours Total shift cannot exceed 12 hours Bonus Shifts (agent NOT scheduled that day): Minimum: 2 hours Maximum: 8 hours Total shift cannot exceed 12 hours