/ /
Getting Started with Salesforce
Updated last month

Integrating Orum with Salesforce can enhance your sales efforts by streamlining processes and automating tasks. This guide will help you get started with the Salesforce integration in Orum.

Approve Orum as a 'Connected App' in Salesforce

  • For OAuth orgs, please ensure you have Orum allowed in the 'Connected Apps OAuth Usage' shown below.

    • This may require a user to make an attempt to log into Orum using Salesforce prior to the admin being able to see Orum appear.

    • Be sure to check that the action column does not indicate the application is "Blocked". If blocked, users will not be able to authenticate when attempting to add Salesforce integration to Orum.

Screenshot 2025-10-16 at 1.21.12 PM.png

Network Recommendations

Recommendations will need to be fulfilled across all users and office locations. Reach out to Orum's support team with any questions. 

  • Whitelisting - Orum recommends these to be applied across all networks, firewalls, VPNs, and security apps

  • Technical Specs - Orum also has provided these recommendations to ensure reps are able to smoothly use the app

How to Set Up Salesforce for Orum

To get the most out of your Orum and Salesforce integration, proper setup is key. Here are some essential steps to ensure your team has the right information and can track their activities effectively.


1. Build Your Reports

One of the key aspects of using Orum effectively in Salesforce is to create reports that you can call from. Reports help you segment your prospects and target them with specific campaigns.

Orum works with specific report types in Salesforce. To ensure that your reports are compatible and provide the data you need, confirm that you are using a supported report type when building your call lists.

Click here for an interactive guide

Learn more about creating reports.


2. Filter Reports by Lead Status

Filtering your reports by fields like Lead Status allows reps to focus on the most relevant prospects. It's crucial that reps consistently update this status after calls (possible directly in Orum), or even better, automate the process using a Salesforce flow. This practice keeps your data clean and ensures reps are always working with accurate information.


3. Map Key Fields from Your Data Provider

For maximum efficiency and preparedness, ensure that key fields from your data providers are mapped correctly into Salesforce. This includes information like Mobile #s and LinkedIn URLs. Having this information readily available helps reps maximize their connect rates and prepare for calls more effectively.

Orum provides support guides for integrating with popular data providers such as LushaZoomInfoLeadIQSeamlessApollo

How to Connect Orum with Salesforce

If you are an Admin, make sure to complete our Admin Checklist to connect the two systems. Once you've connected your Salesforce instance to Orum, you can customize how information is logged using the settings on the Account Settings page. Here's a breakdown of each configurable option:

🔗 Recording Field

To save the call recording link to Salesforce, select the SFDC task field where you'd like the recording URL to be stored.

Tip: This is usually a custom field like Call_Recording. Make sure it's a Text or URL field on the Task object.

image.png


📋 List Name Field

If you're dialing from a specific list in Orum, we can log the list name to a Salesforce task field of your choosing. This helps you track which campaigns are generating calls.

Example: You might use a custom field called Campaign_Name.

image.png


☎️ Phone Label Field

When a rep connects to a number, we log the phone number type (e.g., “Mobile,” “Office,” etc.). You can choose which Salesforce task field this label gets saved to.

Useful for understanding which contact methods are yielding results.

image.png


Disposition Field

Choose the SFDC task field where you'd like call outcomes (dispositions) to be stored. These are selected by reps after a connect, and might include options like “No Answer,” “Interested,” “Meeting Bookedr,” etc.

This is commonly mapped to a picklist field on the Task object.

image.png


✏️ Editable Task Fields

Want reps to update additional fields during a call? Select any custom or standard task fields here (created on the Activity/Task object in Salesforce), and Orum will surface them on the connect screen for editing. These values are then written back to the corresponding Salesforce task.

This is perfect for collecting data like meeting booked, competitor mentioned, or product interest.

image.png


🛠 Tips for Success

  • All mapped fields should exist on the Task object in Salesforce.

  • Make sure reps have permission to edit these fields.

  • Use consistent field naming conventions across teams to simplify reporting.

How Orum Data appears in Salesforce

Calls placed in Orum will be logged as a completed Task, associated with the Lead/Contact in Salesforce, like so:

image.png

Once you've completed these steps, you're ready to start dialing! 

How to Track Orum Activity in Salesforce

Create a Task and Events report with the following Columns and Filters to see Total Calls made.

Adjust the filters as needed to show a different date or User. This can be used as the source reports for a dashboard.

Every call made in Orum will have [Orum] in the subject line which can be used to separate Orum calls from calls made on other systems.

Task and Events Report

Columns

Filters



To show Connected Calls use the filters below, very similar to above we just add a Filter for “Call Result” to include all of your Answered or Connected dispositions. These should be where reps spoke to the intended prospect (Not GK, Dial Trees, or VMs).


To show Conversations (1+ min) with prospects add Call Duration (seconds) as a filter and set it to Greater or equal to 60.



Was this article helpful?