The ScheduleOnce connector for Salesforce enables complete scheduling integration through all phases of the Customer lifecycle.
The ScheduleOnce connector for Salesforce is an official app in the Salesforce AppExchange and was approved by the Salesforce Security Review, ensuring the connector meets industry best practices for security. Learn more about the Salesforce connector security
Setting up the ScheduleOnce connector for Salesforce
Before you can begin sending your booking data to Salesforce, you must set up the connector. This first step of the setup process is connecting the API User. The API User in Salesforce ensures that all API calls between ScheduleOnce and Salesforce have the required permissions.
Once you have connected to Salesforce using the API User, you can install the ScheduleOnce connector for Salesforce.
Note You can test the ScheduleOnce connector for Salesforce with a Salesforce Sandbox environment. The setup will be kept when you switch back to your production environment.
To test the connector in your Sandbox environment, connect ScheduleOnce to an API User created in your Salesforce Sandbox environment and complete the connector setup. Then disconnect and connect to an API User created in your production environment. Learn more about connecting to a Salesforce Sandbox environment
Permission Sets in Salesforce define what functions and features your Users have access to in Salesforce. To use the ScheduleOnce connector for Salesforce, the API User you create must be granted the appropriate permissions. This is done by assigning the ScheduleOnce permission set.
Salesforce Activity Events
When a booking is made, a Salesforce Activity Event is always created and related to a Salesforce Lead, Contact, Person Account, or Case record. After the Activity Event is created, it is continuously updated through all phases of the booking lifecycle: Scheduled, Rescheduled, Completed, Canceled, or No-show. Learn more about activity statuses
The Event status (which indicates the current phase of the booking in the booking lifecycle) and the Cancel/reschedule reason fields are provided with the ScheduleOnce connector for Salesforce and are mapped to ScheduleOnce data. You can track the Event Status and the Cancel/reschedule reason by adding these fields to the Activity Event layout.
Configuring the connector
There are two types of mapping which must be created between ScheduleOnce and Salesforce:
- Universally required Salesforce fields: Universally required fields that do not have a default value in Salesforce must receive a value for an object to be created. For example, if Company is a universally required field for a Lead record, the record cannot be created via the Salesforce API unless a value is provided for the Company field. If it has not been mapped in the field validation step, ScheduleOnce will pass a default value to this field.
- Non-mandatory Salesforce fields: Non-mandatory fields can contain additional Customer data and booking data, some of which is mapped to non-mandatory Salesforce fields by default. You can use these to pass any other optional data to Salesforce.
Note There are some restrictions on the type of data which can be passed between ScheduleOnce and Salesforce. See Supported and non-supported field types in the Salesforce integration for full details.
After configuring the field validation mapping and field mapping, you must define your creation rules. Here you can specify what happens when a new Lead, Contact, Person Account, or Case is created from a booking or when it is updated.
For example, you can decide whether a booking should override an existing Salesforce Lead or update it and who it should be assigned to.
Using the Salesforce integration
After you've completed the connector setup process, you'll need to connect your ScheduleOnce User account to Salesforce in order to use the Salesforce integration. Each User connects to their own personal Salesforce Account. If you're an Administrator, you can also make changes to the connector setup after connecting to your Salesforce Account.
In the Salesforce settings section of your Booking page, you can map Salesforce Record Types to the Lead, Contact, Account, Event, and Case records, add an Event to the Salesforce calendar, and select which type of records should be created when you use General links.
When scheduling with existing Salesforce Leads, Contacts, Person Account, or Case records, you can either use our Personalized links (Salesforce ID) for your Salesforce email templates or Salesforce emails, use Salesforce scheduling buttons, or use the Salesforce Record ID identify Customers during the booking process.
A number of issues may cause problems with the Salesforce integration, such as an API User connection issue or required fields which are not mapped.
You can read more about these issues and how to resolve them in our Salesforce connector troubleshooting article.