Salesforce
Integrate Rep.ai with the #1 CRM platform.
Last updated
Integrate Rep.ai with the #1 CRM platform.
Last updated
Rep.ai integration with Salesforce allows admins to quickly view important information about Salesforce contacts from the dashboard, or create new contacts from visitors within the dashboard.
To link your Salesforce contacts to Rep.ai visitors, go to the Integrations page in your Rep.ai settings, find the Salesforce card, and click the toggle to enable it. You'll be redirected to Salesforce to authorize the integration. The integration requires a Salesforce edition with the Web Services API feature. For more information view the Salesforce comparison page. The connecting account must have admin access to the Salesforce instance.
Once connected, all Salesforce Leads, Contacts, Accounts and Opportunities will be synced to your Rep.ai account. As objects change between the two systems, they will automatically be kept in sync in the background, after a short delay.
Data from Salesforce Leads and Contacts whose email matches contacts in Rep.ai will sync into that contact. When a Rep.ai Contact is associated with both a Salesforce Lead and a Salesforce Contact, changes to that contact will be synced up to both the Lead and the Contact. When a new Rep.ai Contact is created (eg. via an agent asking a visitor for their e-mail address) for which there is no equivalent Lead or Contact in Salesforce, a new Lead (but not a Contact) will be created in Salesforce.
Providing Rep.ai with the email address of the visitor will link it to any Salesforce contacts with the same email. You can provide the widget with their email using the Custom User Identities feature. If a match is found, you'll see information about the contact and a link to Salesforce in the sidebar.
If you either don't have visitor email addresses available on your site, or would like to create Salesforce contacts right from the dashboard, you can click the "Create new contact" button while viewing an active visitor. As soon as you submit the form you will be able to use the link to immediately access Salesforce and add additional information.
When a Rep.ai call is completed a call is logged in Salesforce as a "Call" type task. If the call was recorded a link to the recording will be included.
Rep.ai integrates with Salesforce to synchronize various influence-related properties. These properties capture interactions that a visitor has had with the website or with Rep.ai. The synchronization is fully automated and does not require manual configuration. All properties are automatically created upon connecting Salesforce and Rep.ai. The process ensures that the properties are transmitted to Salesforce within 30 minutes after the visitor finishes their browsing session. The properties collected and transmitted to Salesforce include the following:
ServiceBell Engagement Status
Contact, Account
Interactions the Contact has had with the website or Rep.ai. Possible options include: Detected, Chat, Video Chat, Audio Chat, User Viewed Session, Inbound Call, Outbound Call, Journey Presented, Journey Engaged, Form Filled, Meeting Booked
ServiceBell Web URLs Visited
Contact, Account
A raw capture of all URLs visited by the Contact, including query strings.
ServiceBell High-Intent URLs Visited
Contact, Account
Names of the high-intent urls visited by the Contact based on a list of high-value pages maintained in Rep.ai.
ServiceBell First Detected
Contact, Account
This field reflects the first date the Contact was detected on the website.
ServiceBell Last Detected
Contact, Account
This field reflects the last date the Contact was detected on the website.
ServiceBell First Engaged
Contact, Account
This field reflects the first date the Contact was engaged on the website through Rep.ai.
ServiceBell Last Engaged
Contact, Account
This field reflects the last date the Contact was engaged on the website through Rep.ai.
ServiceBell Utm Source
Contact, Account
Last detected UTM Campaign .
ServiceBell Utm Medium
Contact, Account
Last detected UTM Medium .
ServiceBell Utm Campaign
Contact, Account
Last detected UTM Campaign .
ServiceBell Utm Term
Contact, Account
Last detected UTM Term .
ServiceBell Utm Content
Contact, Account
Last detected UTM Content .
ServiceBell Number of unique visitors
Company
This is the total number of unique website visitors from the account visiting the site, detected by Rep.ai.
Once you've integrated Salesforce in your Rep.ai account, you can immediately start using it with the dialer. The dialer will sync all your Salesforce reports and you can use synced reports to call prospects. To create a new report:
Log into Salesforce.
Navigate to Reports.
Choose a Report Type. The report must include contacts or leads and must contain at least an e-mail address or a phone number for each contact or lead row.
Add any filters you like.
Save the report.
Sync with Rep.ai. Once created, the report will sync with Rep.ai within about 15 minutes. Once synced, you'll be able to find the report in Rep.ai under the name you chose in step 5.
To remove prospects from reports once they've been called:
Log into Salesforce.
Create a new "Record-Triggered" Flow.
Choose "Task" as the Object.
Pick "A record is created or updated" as the trigger.
Choose "Any Condition Is Met (OR)" as the Condition Requirements.
Choose the "CallDisposition" field and set the operator to "Does Not Equal" and the value to "{!$GlobalConstant.EmptyString}".
In the Flow editor, click the plus button.
Pick "Update Records".
Give the Flow node a label name.
Select "Lead" or "Contact" in the "Object" field, depending on what kinds of reports you make.
Select "Id" for the field, "Equals" for the Operator and {!$Record__Prior.WhoId}
for the value.
In the "Set Field Values for the Contact Records" section, select "Contact_Status__c" (or "Lead_Status__c" if using Leads), and set the value to whatever the lead status is that you want the contact to switch to after the call is logged.
Save your flow and activate it.
Update your reports to filter out any leads or contacts that are in the state you selected in step 12.