Shift Scheduling configuration is a multi-week effort spanning data preparation, scheduling engine setup, and rollout. The workflow below covers the standard sequence for getting a Workforce Engagement Management deployment from initial Setup to live, scheduled agents.
- Enable Workforce Engagement and import historical data
From Setup, search for Workforce Engagement Settings and enable the feature. Confirm WEM licenses are assigned to the workforce manager and any supervisors. Import at least 13 weeks of historical contact volume data, broken down by channel, day, and interval. The data drives the forecast, and 13 weeks is the typical minimum for the forecast engine to identify weekly and seasonal patterns. Import existing agent skills, preferences, and tenure data so the scheduler has the context it needs.
- Define service territories, shift patterns, and agent assignments
Create Service Territories for each functional or geographic grouping (Tier 1 Support, Tier 2 Support, Spanish-speaking Team). Define Shift Patterns for each recurring schedule template the business uses. Assign each agent to a Service Territory and one or more Patterns. Set per-agent preferences and constraints (max hours per week, weekend availability, training restrictions). Run a small pilot generation against one Service Territory to validate the configuration before scaling up.
- Generate forecasts and run the scheduling engine
Use the Forecast Builder to produce a 4-week or 13-week forecast against the imported historical data. Review the forecast against business knowledge and adjust for known anomalies (a product launch driving extra demand, a planned outage reducing volume). Run the scheduling engine against the forecast and the configured agent pool. Review the generated shifts in the Schedule view. Iterate the parameters (service level targets, agent constraints) until the schedules look reasonable to the workforce manager.
- Publish schedules, train agents, and run intraday management
Publish the schedules to the agent self-service portal. Agents see their upcoming shifts and can request time off or post shifts to the swap board. Train the workforce manager on intraday management: monitoring real-time staffing, calling in offered shifts when demand spikes, releasing agents when demand drops. Run for two weeks with active workforce manager oversight, then settle into the steady-state cadence of weekly schedule generation, daily intraday adjustments, and bi-weekly review of forecast accuracy.
- Forecast accuracy depends on historical data quality. Bad input data produces bad schedules, and the engine has no way to detect or fix this.
- Constraints that are too strict cause the engine to fail with "no valid schedule found." Start loose and tighten incrementally rather than starting at the ideal state.
- Agent self-service shift swaps need approval workflows for skill-mismatched swaps. Skip the approval and agents end up working shifts they are not qualified for.
- Schedules generated for far horizons drift from reality as agents change roles or take leave. Most orgs publish one to two weeks at a time, not three months.
- Intraday adjustments without payroll signoff can create overtime liability. Always confirm overtime rules in the configuration before letting the workforce manager call in extra agents.