Export sales conversations and push Otter insights to Salesforce at any time. Send meeting notes, transcripts, and key insights directly to the right Salesforce record to keep workflows efficient and deals moving forward. Learn more about Otter's integration with Salesforce.
Otter can automatically push insights to Salesforce. If you prefer not to enable automatic syncing and would rather manually export conversations, follow the steps below.
Manually export a conversation to Salesforce
In addition to automatic exports, you can manually export Otter conversations to Salesforce to associate meeting notes, transcripts, and insights with your Salesforce Contacts and Opportunities. Once Salesforce is connected to Otter, you can export individual conversations to Salesforce records.
-
Open the conversation you want to export in Otter. Click the three-dot menu (⋯) in the upper-right corner of the conversation and select Export to Salesforce.
-
In the export window, select the Salesforce record type you want to export the conversation to.
-
Use the search field to find and select the Contact/Lead or Opportunity.
-
Click Export to complete the process.
-
Once the export is complete, the conversation will be associated with the selected Contact/Lead or Opportunity in Salesforce.
View an exported conversation in Salesforce
After exporting a conversation to Salesforce, click View in the export confirmation to open the associated Contact/Lead and Opportunity record in Salesforce.
Update an exported conversation in Salesforce.
If you make changes to an Otter conversation after exporting it to Salesforce, you can update the associated Salesforce records to reflect those changes. This includes updates to the conversation summary, templates, action items, and more.
Follow these steps to update an exported conversation in Salesforce:
-
Open the conversation in Otter and make any necessary changes to the meeting notes, summary, templates, or action items. Click Update under Exported to Salesforce.
-
Keep the existing associated Contact/Lead and Opportunity, or update to a new record. Click Update to save your changes and push the updated conversation notes to the selected Salesforce records.
- Click View to see the updated changes in Salesforce.
Only allow manual exports to Salesforce
By default, Otter can automatically export conversation notes and insights to Salesforce based on your workspace's integration settings. If you prefer to control which conversations are shared with Salesforce, you can disable automatic exports and switch to manual exports only for the workspace.
When manual exports are enabled, conversations will only be exported to Salesforce when a user manually initiates an export. You can still manually export conversations at any time, regardless of your workspace's automatic export settings.
- Make sure you have set up Salesforce.
-
Go to Integrations → Salesforce.
-
Click Connect for all to authenticate Salesforce for all workspace members. Individual members can continue to step 4.
-
Next to Exports to Salesforce, click the dropdown menu and select Manual.
-
Click Confirm to apply your changes.
- Going forward, conversations will only be exported to Salesforce when manually initiated.
FAQs
Can I disable automatic Salesforce exports and only export conversations manually?
Yes. Workspace admins can disable automatic exports by navigating to Integrations → Salesforce and changing Exports to Salesforce to Manual.
When this setting is enabled, conversations will only be exported when a user manually initiates an export. You can manually export conversations regardless of whether automatic exports are enabled or disabled.
Will disabling automatic exports remove previously exported conversations from Salesforce?
No. Switching from automatic to manual exports does not delete or remove conversations that were previously exported to Salesforce.
The setting only affects future automatic exports. Previously exported conversation notes will remain in their associated Salesforce records.
Do I need to be a workspace admin to export conversations to Salesforce?
No. Workspace admins are responsible for configuring and managing the Salesforce integration, including connecting Salesforce and setting automatic or manual export preferences.
Once Salesforce is connected, users can manually export their conversations to Salesforce Contact/Lead and Opportunities.
Can I export conversations to Salesforce from the Otter mobile app?
No. Manually exporting conversations to Salesforce is currently only supported on Otter Web and the Otter Desktop app. To manually export a conversation, open Otter in a web browser or use the desktop app.
Why do workspace admins and members see different Salesforce integration settings?
Salesforce integration settings vary depending on your role in the Otter workspace and whether Salesforce has been connected for the entire workspace. Workspace admins have access to additional settings for managing the Salesforce integration across the workspace, while workspace members can manage their individual Salesforce connection and available export preferences.
Salesforce connected for the entire workspace
When a workspace admin connects Salesforce for the entire workspace, the integration settings are managed at the workspace level.
- Admin view: Admins can manage workspace-wide Salesforce settings, including export preferences, meeting creation, mapping, and AI Chat.
- Member view: Members can view the available Salesforce settings but cannot modify workspace-wide configurations managed by their admin.
Salesforce not connected for the entire workspace
If a workspace admin has not connected Salesforce for the entire workspace, members can connect their own Salesforce accounts and manage their individual integration settings.
- Admin view: Admins can connect Salesforce for the entire workspace using Connect for all, or manage their own individual connection.
- Member view: Members can connect Salesforce individually and configure their own automatic or manual export preferences, AI Chat, and Salesforce Meeting creation settings.
Feedback
0 comments
Article is closed for comments.