Enabling Peak Hour Scheduling is a configuration change on Service Territory records inside Salesforce Scheduler. The walkthrough below assumes Scheduler is already deployed and active in the org, and the goal is to add peak-hour bias to existing scheduling.
- Analyze current utilization before enabling
Pull the Scheduler utilization report for the last 90 days. Identify which hours of which days actually drive the most demand, and which hours have available capacity that consistently goes unused. The pattern that emerges defines your true peak window, which may not match assumptions. Document the findings as the baseline against which the feature's impact will be measured. Without this baseline, you cannot tell whether enabling Peak Hour Scheduling improved utilization or just moved the same demand around.
- Configure peak hours per Service Territory
From Setup, navigate to Service Territories. For each territory where Peak Hour Scheduling should apply, edit the territory record. Add the peak-hour configuration block: days of week, start time, end time. Save. Repeat for every relevant territory. For multi-time-zone orgs, the configuration is automatic in territory-local time; you do not need to convert to UTC manually. Test the configuration by booking a test appointment as a sample customer and confirming peak hours appear first.
- Update self-service booking flow if needed
Open the Experience Cloud or Lightning page hosting the self-service appointment booking. Confirm the slot-selection component shows peak slots prominently and includes a clear option to view all slots (including off-peak). If the flow does not expose this filter, add it via a custom Lightning Component or a built-in filter option. The customer experience should make peak slots the default but not the only choice. Run a usability check with a non-technical user to confirm the flow is intuitive.
- Monitor and iterate
Two weeks after enabling Peak Hour Scheduling, pull the utilization report again. Compare to the baseline. Peak utilization should be measurably higher; off-peak should still be filling at a reasonable rate. If peak utilization did not rise, the configured window may be wrong, and you should adjust based on actual demand patterns. If off-peak utilization dropped too far, consider widening the peak window to capture more of the day rather than concentrating booking in a narrow strip. Iterate monthly until the utilization shape matches the business goal.
- Peak Hour Scheduling does not enforce capacity. It only biases the order of slot presentation. Overbooking still requires capacity overrides, which is a separate setting.
- Customers who want off-peak times can be frustrated if the self-service flow does not expose an off-peak filter clearly. UX matters here.
- Peak hours vary by territory. A single global peak-hour configuration will misfire for territories with different demand patterns.
- Peak-hour appointments have higher no-show risk in some businesses. Monitor the no-show rate segmented by peak versus off-peak and adjust reminder cadence accordingly.
- Enabling Peak Hour Scheduling without intentional staffing during peak windows produces frustrated agents, not improved utilization. Align staffing and scheduling together.