Salesforce Scheduler is enabled and configured in Setup, then exposed to users through flows. These are the core steps to get a first bookable appointment working in an Enterprise or Unlimited edition org.
- Enable Scheduler and assign access
In Setup, open the Salesforce Scheduler Setup App and enable Scheduler. Assign the relevant Scheduler permission set licenses and permission sets to internal users, and configure guest access if you plan to offer inbound booking on a public site.
- Build the business data
Create Service Resources for your appointment attendees, set up Service Territories for your locations, and define Operating Hours so the engine knows when each territory and resource is available. Add the skills each resource holds.
- Define what can be booked
Create Work Type Groups as the topics customers choose from, then Work Types under them. Set each work type's estimated duration, block time before and after, and required skills so the slot calculation produces the right windows.
- Set scheduling policy rules
Configure a scheduling policy to control how slots are found. Choose whether to check the Salesforce calendar, enforce the account's visiting hours, and which appointment start time interval applies when a work type does not set one.
- Expose the booking flow
Add the outbound scheduling flow to record pages in the Service Console for assisted booking, and place the inbound flow on an Experience Cloud site or your website for self-service. Test both paths end to end.
Books more than one service resource into a single appointment, for cases that need several people present.
Lets one resource handle multiple appointments in the same window, useful for group or short overlapping sessions.
Spreads new bookings across eligible resources instead of always filling the first available one.
Automatically gives a service resource record access to the appointments assigned to them.
- An empty slot list almost always means an operating hours, skill, or territory gap, not a product bug. Walk the constraint chain before raising a case.
- Test inbound booking as a real guest user, not just an internal user, because the public Experience Cloud path can behave differently.
- Salesforce Scheduler needs Enterprise or Unlimited edition and the right permission set licenses. Confirm licensing before you design the rollout.