Salesforce

This guide will walk you through how to set up your Salesforce integration with Signals.

First, log in to your Signals account.

Click on your name in the bottom-left corner.

Navigate to "Integrations."

Scroll down to "CRM" and select "Salesforce."

First, click the drop-down under the “Criteria” setting to set up the minimum requirements that web visitors must meet for the integration to send them to Salesforce. This specifies the minimum lead score a chat visitor needs to have the integration send the web visitor to Salesforce as a lead.

For more information on setting lead scores, see our HelpDocs video on setting lead scores.

You can find these options in the "Criteria" dropdown. "All" will send each chat visitor to Salesforce as a lead.

• "One Star" will send contacts who have at least one star as a Lead Score to Salesforce through the integration.

• "Two Stars" will send contacts who have at least two stars.

• "Three Stars" will send every contact to Salesforce who has a lead score of at least three stars.

Scroll down. In the Campaign Management section, select which campaign you would like new leads to be a part of. This part is optional.

Note: Only web visitors that are sent as new Leads will be assigned to the campaign you choose; if a record is updated in Salesforce based on the web visitor’s information, that record will not be added to the campaign.

Note: You can only select one campaign here. Any web visitor who qualifies you meets the minimum criteria will be sent to the campaign you choose.

In the next drop-down, select the Synchronization Delay, which is the amount of time that passes from when the web visitor becomes qualified as a lead and when the web visitor is actually sent to Salesforce as a lead.

In the Event Settings section, select which Signals activities you would also like to send to Salesforce with the integration. This part is optional.

If you select one of these event options, the integration will connect the activity to the Salesforce record as a Salesforce task.

Configure the Lead Owner section. This section determines who the integration will assign as the Lead Owner in Salesforce when the integration creates a new Lead in Salesforce.

You have three options in this section:

• User who scheduled a meeting: The new Lead owner will be the user whose calendar the web visitor booked a meeting.

• User who was last routed: The new Lead owner will be the user who was last routed into the conversation with the web visitor.

• User who closed the conversation: The new Lead owner will be the user who closed the conversation with the web visitor. The integration will assign the new Lead owner based on any option you select here, with the higher-ranking selection taking priority when deciding the Lead Owner. For example, suppose you had all three of these options selected in this menu. If a web visitor scheduled a meeting on Sally’s calendar; Bob was the agent last routed into the conversation, and Jill was the chat agent who closed the conversation, then the integration will assign Sally as the new Lead owner in Salesforce.

Scroll back up, and select the "Leads" option.

Configure the Field Mapping sections. Mapping these fields will determine which fields in Signals will populate your desired Salesforce fields for the record. For example, in the screenshot here, we’ve configured the Signals “First Name” contact field to populate the Salesforce “First Name” field for the record that the integration sends to Salesforce.

You also have the option to overwrite any field that the integration sends to Salesforce. Selecting "Overwrite" affects when a web visitor meets the minimum criteria for the integration and their email address is already saved in Salesforce as a Lead. If a web visitor inputs an email address that is already saved as the email field for one of your Salesforce Leads, the integration will update the fields in Salesforce that you have set to overwrite with the information provided from Signals.

Note: This option only updates information for Leads. For example, if a Salesforce Contact has an email address that one of your web visitors inputs, the integration will not update this Salesforce Contact.

Note: This option only looks at the Email for Salesforce Leads when deciding whether or not to overwrite fields. For example, if you have a Salesforce Lead named “John Doe”, if another web visitor named “John Doe” qualifies for the integration, they will be sent as a new Lead in Salesforce if they have input a different email field. You can remove any mappings you've created by pressing the "x" next to the field in the mapping.

You can also add a new mapping field by selecting the "Add Field" option at the bottom of the page.

Once you have selected the “Add Field” option, simply select which Signals field will map to which Salesforce field by selecting the corresponding drop-down menus. Don't forget to click "Save" at the top of your screen!

Scroll back up again, and navigate to the "Users" tab.

User mapping is similar to field mapping. Click "Add User" to map Signals users to their corresponding Salesforce users.

Now, click on the "Ownership" tab. This tab allows you to manage your account ownership rules for Salesforce and HubSpot, and can designate different owners from your CRM account by looking up accounts in the specified segment and mapping the CRM user field to the account owner.

To create a new account ownership rule, select "Add Segment Rule," and pick a segment from the drop-down menu. If you don't have company segments created, you will need to create those first. Be sure to check out our HelpDocs video on creating a company segment if you have any questions!

You can have up to two fields here. Click "Add another field" and select a "then by" owner. This will work as a fallback in the case that there is no match for the first designated field.

Select a Fallback Routing rule. This will be a specific Signals user who will be assigned as the Account Owner in the case that the Account Owner in your CRM is not a Signals user. Lastly, select Fallback criteria in the case that a company does not match the specified segments that you set up in step 2.

When you’re ready to turn your Salesforce integration on, simply select the “Integration On” switch at the top of the page so that the switch is toggled on.

You also have the option to manually connect a web visitor’s information to Salesforce. This is helpful when your bot is not configured to capture the web visitor as a Lead but when reviewing their chat transcript, you see that they are a good lead you want to capture in Salesforce. To do this, click "Chat" in the first sidebar.

Find the chat with the web visitor information you want to connect to Salesforce.

Under "Conversation Details," under the "Contact Info" card, click the Salesforce icon to sync. Selecting this option will transfer the information from the web visitor in this chat to Salesforce according to the settings you established in the Integrations menu.

Note: Manually syncing a web visitor like this will not create Salesforce Tasks with the chat transcript or meetings booked.

Note: Manually syncing a web visitor like this ignores any minimum criteria you have set in the Integrations menu.

If you're struggling to find the "Contact Info card, click on "Edit Cards" next to "Conversation Details" and make sure "Contact Info" is pinned.

Other Troubleshooting Tips: If your Salesforce integration did not send a web visitor’s information to Salesforce, check the following in your troubleshooting:

• Conversation Closed: Ensure that the conversation is closed. The automated Salesforce integration will not send a web visitor’s information to Salesforce until the conversation closes.

• Minimum Criteria Met: Ensure that the web visitor meets the minimum criteria in terms of their Lead Score. The automated Salesforce integration will not send a web visitor’s information to Salesforce if they do not have the required Lead Score.

• Synchronization Delay: Ensure that the amount of time specified in your Synchronization Delay settings has passed after the conversation was closed.

• Integration On: Ensure that your Salesforce integration is turned on if you are expecting the integration to send web visitors’ information to Salesforce.