Integrating Orum with Salesforce can greatly enhance your sales efforts by streamlining processes and automating tasks. Whether you're an admin or a sales representative, this guide will help you get started with the Salesforce integration in Orum.

If you are an Admin, make sure to first complete our Admin Checklist before moving forward. 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.

📋 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.

☎️ 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.

✅ 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.

✏️ Editable Task Fields

Want reps to update additional fields during a call? Select any custom or standard task fields here, 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.

🛠 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.

Creating Reports for Calling

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.

Here's how you can create Salesforce reports to call from:

Review the 4 supported report types

Click here for an interactive guide

Learn more about creating reports.

Creating Automations to Remove Prospects from Reports

For Admins:

Automating the removal of prospects from reports can help keep your lists up to date and ensure that your sales reps are focusing on active prospects.

Here is a short guide on how to create record-triggered flows that will help automate and remove prospects based on contact status.

Alternatively, after conversations, reps can manually update the field that your Report is filtered on, I.E. "Lead Status". When "Lead Status" no longer matches your Report filter criteria (i.e. it changes from to from "New" to "Disqualified", etc.), the contact will fall off the report.

Map Mobile #s into Salesforce from your Data Provider

This will help maximize your connect rates. To maximize preparedness for calls, also map LinkedIn URLs and any other relevant fields for your reps to have on hand. Support guides for Lusha, ZoomInfo, LeadIQ, Seamless, Apollo.

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.