Assembled Workforce Management

I’d love to see more flexibility added to Scheduling Rule conditions, specifically the ability to exclude certain days of the week or times of day without tying those exclusions to an advisor’s shift properties. For example, I’m trying to create a rule that schedules three 1-hour Email segments per week on three separate shifts. Using Choose days automatically, I can set the event to occur once per shift across three shifts each week, which gives Schedule Assistant the flexibility to place that time where staffing best supports it. The challenge is that I also need to exclude Mondays due to our business needs. Currently, the available conditions are based on the advisor’s schedule—shift start time, shift end time, or shift length—rather than the day or scheduling window itself. It would be helpful to have conditions such as: Day of week: Include/exclude selected days Time of day: Only schedule before, after, or between specified times Ideally, the ability to combine these with Choose days automatically This would allow WFM teams to essentially tell Schedule Assistant: Schedule this activity 3 shifts per week, wherever staffing best supports it, but do not schedule it on Monday. That would preserve the benefit of automatic scheduling and staffing optimization while giving WFM teams the ability to set business-specific guardrails around when an activity should or should not be scheduled.

Problem The Guide step in Workflows always works as a reply-generation step. Even when a workflow only uses Guide to reason over a ticket and pass outcomes to later decision steps, the step still tries to write a reply. Sometimes it sends free text straight to the end user. Use case Some teams only allow approved macros for outbound messages, for regulatory, contractual or brand reasons. In these workflows: Guide reads the ticket and produces outcomes (e.g. a classification, eligibility or next action). Later decision steps branch on those outcomes. A macro or dedicated reply step sends the only outbound message. Because Guide can't be stopped from replying, it sometimes sends non-macro text. Why prompting isn't enough Compliance risk: When non-approved text reaches an external party this is a compliance breach. Slow to validate: The errors can be rare, so it can take ~3 months of volume to confirm that a prompt change has worked. That's too long to leave a compliance gap open. Not deterministic: Prompt instructions guide the model but can't guarantee anything. Customers need a guarantee at the configuration level. Request Add a Guide mode or setting, or a separate step type, that: Returns only structured outputs or variables for downstream steps Can never send a reply to the end user, whatever the prompt says Leaves outbound messaging entirely to macro or reply steps later in the workflow Expected impact No unapproved replies from reasoning steps Safe to use Guide in compliance-sensitive workflows Less prompt workarounds, and less need for long monitoring periods after workflow changes

Having a setting to optimize for an event that only happens once a week or month.

Feature Request: Automated Schedule Approvals Based on Coverage and Policy Objective Transition our schedule change process from a manual review to an automated system that immediately approves or denies requests based on strict coverage thresholds and country-specific labor policies. Auto-Approval Criteria A schedule change should only be automatically approved if it meets all of the following conditions: The total scheduled hours perfectly align with the region's specific working hour policies. The requested change maintains adequate staffing levels without creating any coverage gaps. Auto-Denial Criteria The system must automatically deny a schedule change if any of the following occur: Coverage Gaps: The change causes scheduled headcount to drop below the required staffing levels. Overstaffing: The change schedules more staff than is required for those hours. Policy Violations: The total working hours violate country-specific compliance rules (e.g., exceeding maximum allowed hours). Incomplete Shifts: The shift duration contains unassigned or "blank" time on the calendar. Operational Standard: India (Example) Shift Duration: Engineers must be scheduled for an exact 9-hour shift. Comprehensive Scheduling: The entire 9-hour block must be completely filled with designated events. Allowed Events: The schedule must account for every minute of the shift, including productive time, Lunch, Breaks, Meetings, Trainings, and any partial Time-Off events (applicable if the time off exceeds one hour). If there are any requests to delete the schedule as they are taking week offs during weekdays as they are scheduled for weekend working, do not auto approve to deny those schedule deletion requests and keep it in the bin to manually approve.

When optimizations fail or cannot be applied currently only the name of the agent it wasn't applied to and the span the optimization was ran against is shown. Having verbose reporting about why the failure occurred would help us identify and troubleshoot what may be causing optimization issues.

Assembled should allow admins to define auto-approval rules for schedule requests (similar to existing rules for time-off requests) in order to reduce unnecessary manual review and speed up workflow management. For example, a team might want to automatically approve all schedule changes under a certain duration (e.g., <5 hours) or requests submitted within defined parameters, while still requiring manager approval for larger or exceptional edits. This would be especially valuable for teams where individual contributors regularly adjust their own schedules (e.g., clinical, operations, or flexible teams) and where admins currently need to manually approve hundreds of short edits each week. Adding configurable auto-approval thresholds would help: • Reduce bottlenecks in high-volume approval queues • Ensure consistency across different teams or event types • Save time for admins and managers without sacrificing oversight

Would love to have the ability to auto approve (or deny) extra time sign ups based on user defined rules. For example, "approve if > x slots available and total hours worked by requestor this week is <= y hours" or "deny if <=0 slots available."

It would be fabulous to get real time report via automation in Slack.

would like a feature that helps with scenario-planning, so we can see in advance what the optimizations will recommend, then we can essentially choose from the actions: “accept” “decline” or “edit and then accept”. further, it would be great to have a button/function to “optimize” - and when you run this optimization, the product would automatically recommend the most optimal schedule against the upcoming forecast.

It would be helpful to allow optimizing an event and still have it be in the list of events not to edit. The use case here would be: agents 1 through 10 already have a training scheduled. Optimize agents 11 through 50 and add trainings for them. Do not touch agents 1 through 10 because those folks have already had this planned, maybe around some exceptions