Salesforce

How Spara integrates with Salesforce.

Spara support bidirectional data syncs with your Salesforce instance. The Spara platform provides easy-to-use tools to manage field mapping.

For sending data to Salesforce, Spara supports:

• Writing to Lead objects, Contact objects, or both

• Writing entire conversation histories

• Writing structured data, ex. the answer a lead gives to a specific question

Syncing data from Salesforce to Spara streamlines your buyer's sales process by:

• Spara never reasks a question

• Spara's behavior can react to each lead based on where they are in your sales funnel

• Syncs can be triggered at any point in the conversation

Authentication

You must be a Manager-level user to manage third party integrations. You will likely want the individual who manages your Salesforce deployment to complete these instructions.

Navigate to your Integrations page. Click "Authorize" within the Salesforce module. This will lead you through a Salesforce authentication flow. There are no further steps necessary upon completing this flow. You should see that Salesforce is "Enabled" within Spara's Integrations page.

Lead & Contact Field Mapping

Spara's Salesforce Integration page provides easy-to-use tools to map Spara data to Salesforce fields on Lead and/or Contact objects.

When creating a new field mapping, Spara automatically populates all available Spara data and Salesforce fields. Spara's entire conversation history with a given lead is the "Conversation" Spara field.

Additional Object Fields

In addition to syncing Lead and Contact objects, Spara also reads field information from connected Account and Owner Salesforce objects. These facts help provide context around account ownership and sales rep assignments within your CRM. They can be used to configure how Spara engages with and/or routes your leads.

• salesforce_account_id - The unique identifier of the Salesforce Account

• salesforce_account_name - The name of the Salesforce Account, which usually represents the company name

• salesforce_account_owner_email - The email address of the Salesforce Account Owner (i.e. the account's default sales rep)

• salesforce_account_owner_id - The unique identifier of the Salesforce Account Owner

• salesforce_account_owner_name - The first & last names of the Salesforce Account Owner

• salesforce_account_website - The website URL associated with the Salesforce Account

• salesforce_assigned_sales_rep_email - The email address of the lead's assigned sales rep

• salesforce_assigned_sales_rep_id - The unique identifier of the lead's assigned sales rep

• salesforce_assigned_sales_rep_name - The first & last names of the lead's assigned sales representative

FAQs

How does Spara map to a Salesforce Lead or Contact?

Spara maps to Salesforce objects by either a) Salesforce Object ID, or b) email address. In practice, it's usually easiest to map by email address.

Can Spara upload all message history for a lead into Salesforce?

Spara’s Salesforce integration is configured to upload all messages in a single “thread” to Salesforce. This can be synced to any Salesforce object field, controlled by our Salesforce Field Mapping integration.

Can I create/update both Lead and Contact objects?

Of course! You have independent control over how Spara syncs to Leads objects and Contact objects.

Can you sync the answers to important data that leads share to Salesforce?

Yes! Spara can sync any field or data point that is part of your Journeys. For example, if you have a Journey that asks leads "What is your implementation timeline?" you'll have access to a variable implementation_timeline that you can sync to a Salesforce Lead or Contact object field that you specify. This lets you keep all data in your source-of-truth CRM.