Set up a self-service inbound flow so customers can request a meeting that becomes a Service Appointment once confirmed. This assumes Salesforce Scheduler is enabled with service resources, service territories, and work types already created.
- Confirm Scheduler foundations
Make sure service resources are created and mapped to service territories, and that work type groups and work types define your appointment topics, durations, and required skills. These records control which slots a request can offer.
- Add the inbound flow to a page
In Experience Builder, drag the Flow component onto a public page and select Inbound New Guest Appointment for unauthenticated visitors, or Inbound New Appointment for logged-in customers and partners.
- Configure the review and booking step
Use the Review Service Appointment flow screen so the customer confirms date, time, location, and topic before the record is saved. Enable guest handling if you want a Lead created automatically for anonymous bookings.
- Decide on assignment and approval
Choose whether a resource is assigned automatically by skill and territory, or whether the request waits for a person to confirm or approve. Keep the pending step only where the wrong booking would be costly.
- Test the full path and publish
Walk the flow as a real customer, including the guest path, and confirm the request lands as a Service Appointment with the right resource. Add reminders and a modify or cancel option, then publish the site.
Standard template that lets authenticated customers or partners request a meeting with one or more employees or contractors.
Template for unauthenticated visitors on an Experience Cloud site or embedded page, creating a Lead during booking.
Flow screen component that shows read-only and editable appointment details for final confirmation before the record is created.
Option to let Scheduler pick a qualified service resource based on skills and service territory instead of manual selection.
- A requested meeting is not a confirmed booking. Reporting, reminders, and reassignment run on the Service Appointment record that is created after confirmation, not on the raw request.
- Misconfigured operating hours, shifts, or service territories let customers request slots your team cannot honor, which drives cancellations and rework.
- Do not add a confirmation or approval step where any resource can take the appointment. The extra hop adds friction and lowers conversion for no benefit.
- Guest flows need the right user and object permissions plus sharing for guest users, or anonymous booking will fail silently.