You want to put a “Schedule Appointment” button in your Salesforce Community, so your community users can self-schedule appointments with your staff. Assuming the community user is already logged into the community and only accessing this “Schedule Appointment” button from an authenticated page, you would like the user to not have to re-identify themselves, since they are already logged in.
The process you are trying to achieve may be something like this:
- A community user logs into our Salesforce Community (Partner Community, Customer Community, or otherwise).
- They see a “Schedule Appointment” button on an authenticated page and they click it.
- A popup window appears providing the user options to self-schedule an appointment.
- The user chooses a time that works for them and books it.
- The popup concludes with the “You’re Booked!” page summarizing the details.
- The user can now close the window and both the user and the person they scheduled with receive reminders and can access the appointment on their calendars.
Can my Salesforce Developer set this up?
Yes, you can have your own Salesforce Developer (or contract our Customer Success Team) write the small amount of code required to achieve this. Here are the basic steps:
STEP 1: First you must setup a self-scheduling site and produce the URL to the site. You can click on the “SUMO Help” tab in the application and watch the Admin Videos to see how to achieve this or work with our Support or Customer Success Team.
STEP 2: Next you will write some Apex to query the logged in user’s contact record id and then append this to the URL. We call this our “PASS THE ID” functionality, and in doing so, will instruct SUMO to not present our Login/Registration/Guest Mode page to the user.
STEP 3: It is also recommended that you read this article to launch the self-scheduling site in a popup window above the community — “How to Launch a Self-Scheduling Site in a Popup“.
How long should it take my Salesforce Developer to set this up?
Our Customer Success Team estimates 1-2 days of development, testing, and deployment to get this solution up and running.