Considerations for Performance Improvement in Salesforce Scheduler

For a duration of 14 days, we recommended that you keep the number of qualified resources to 20. If you enable skill matching and engagement channel types, then limit the service resources that are associated with the same work type group and the same engagement channel type to 20 per service territory. The limitation applies if you use Salesforce Scheduler standard flows.

Note If more than 20 service resources are available for a time slot, then use Appointment Distribution to limit the list of qualified service resources.

• If you use standard flows, the value of the Time Slot Preload Multiplier attribute on the Select Service Appointment Time Slot screen component determines the number of days that time slots are fetched for by each server call. For example, if your device's page can show time slots for 7 days and the value of the attribute is 2, then Salesforce Scheduler fetches time slots for 14 days (7x2). To reduce the load, fetch time slots for only 7 days by setting the value of the attribute to 1.
• If you use APIs, specify a shorter duration using the Start Time and End Time fields in the API request. The default duration is 31 days.