Summary: This article covers Phone fields - an important Dialer setting. This guide will explain what this field does, how to manage it by integration, and answer frequently asked questions.

What is the Phone fields setting?

The Phone Fields setting controls which Phone Fields will be used to dial your prospects (Mobile, Direct Line, HQ, etc.) These Fields are pulled directly out of your CRM, SEP, or Calling List.

You can choose which numbers to call a Prospect on before your Dialing Session or in between Calls as you see fit. Prioritizing Mobile & Direct Line fields is best practice, but ensure all the types of numbers you wish to call are present on this list, arranged in the order you wish to call them.

If there is a problem with the phone number, it will not be dialed and will be viewable in the 'Uncallable Numbers' section. Here's an article that explains different types of uncallable numbers.

How does the Phone fields setting change by integration?

SalesForce

Orum will recognize all the phone fields that exist on the object you are attempting to call against. It does not need to exist on the report you are dialing.

• For example, if you are dialing down a Leads report, you are calling against the Leads object. Orum will look for all phone fields associated with the Leads object.

Orum offers a "number status" feature for SalesForce users. This is unique to Orum and does not exist within SalesForce. You can mark any Number Status Valid, Questionable, or Invalid. This data does not push to SalesForce, but does affect Dialing in Orum:

• Green (Valid) numbers will be prioritized first regardless of your Phone fields order.

• Red (Invalid) numbers will not be dialed, even if they are selected as a Phone field.

SalesForce Best practices:

Many objects in Salesforce have two native phone fields: Phone and Mobile.

Ask what Phone field(s) have the best data for your organization and arrange these at the top of your Phone fields setting to be dialed first.

We recommend creating a third phone field called "HQ Phone" so that you can reserve the two native fields for direct numbers and quality data. This can result in fewer gatekeepers and dial trees when dialing in Orum, ultimately driving higher connect rates.

If you have a HQ Phone selected in Phone fields, make sure it is dialed last. Or unselect it and dial against your list using Phone and Mobile first.

Outreach

Orum will recognize all native and custom phone fields you have created in Outreach.

Orum does not dial numbers marked as invalid (red) in Outreach, even if they are selected as a Phone Field.

If a number is marked valid (green), we will prioritize that number(s) first regardless of your Phone fields order.

Outreach Best practices:

Ask what Phone field(s) have the best data for your organization and arrange these at the top of your Phone fields setting to be dialed first.

Be diligent about marking Number Status Red and Green. You can do so from within Orum and this will post in Outreach.

Do NOT delete prospects or numbers from Outreach or Orum that have invalid numbers. This "kicks the can" down the road, so to speak, and creates create extra work later. Use Number Status instead.

Salesloft

Orum supports the the native Salesloft Phone fields: Mobile, Office, Home.

Orum recognizes custom phone fields as long as they have the word "phone" in the field name.

Orum offers a "number status" feature for Salesloft users. This is unique to Orum and does not exist within SalesLoft. You can mark any Number Status Valid, Questionable, or Invalid. This data does not push to SalesLoft, but does affect Dialing in Orum:

• Green (Valid) numbers will be prioritized first regardless of your Phone fields order.

• Red (Invalid) numbers will not be dialed, even if they are selected as a Phone field.

SalesLoft Best practices:

Ask what Phone field(s) have the best data for your organization and arrange these at the top of your Phone fields setting to be dialed first.

Be diligent about marking Number Status Red and Green. You can do so from within Orum.

Do NOT delete prospects or numbers from SalesLoft or Orum that have invalid numbers. This "kicks the can" down the road, so to speak, and creates create extra work later. Use Number Status instead.

Ensure your prospect's extensions exist in the extension field in SalesLoft. This is required for Orum to dial the extension automatically.

Hubspot

Orum recognizes all native and custom phone fields for Hubspot.

Custom phone fields must have the word "phone" in the api name to be recognized.

Orum offers a "number status" feature for Hubspot users. This is unique to Orum and does not exist within Hubspot. You can mark any Number Status Valid, Questionable, or Invalid. This data does not push to Hubspot, but does affect Dialing in Orum:

• Green (Valid) numbers will be prioritized first regardless of your Phone fields order.

• Red (Invalid) numbers will not be dialed, even if they are selected as a Phone field.

Hubspot Best practices:

Ask what Phone field(s) have the best data for your organization and arrange these at the top of your Phone fields setting to be dialed first.

Be diligent about marking Number Status Red and Green. You can do so from within Orum.

Do NOT delete prospects or numbers from Hubspot or Orum that have invalid numbers. This "kicks the can" down the road, so to speak, and creates create extra work later. Use Number Status instead.

Apollo

Orum recognizes all native and custom phone fields for Apollo.

Custom phone fields must have the word "phone" in the name to be recognized.

Orum offers a "number status" feature for Apollo users. This is unique to Orum and does not exist within Apollo. You can mark any Number Status Valid, Questionable, or Invalid. This data does not push to Apollo, but does affect Dialing in Orum.

• Green (Valid) numbers will be prioritized first regardless of your Phone fields order.

• Red (Invalid) numbers will not be dialed, even if they are selected as a Phone field.

Apollo Best practices:

Ask what Phone field(s) have the best data for your organization and arrange these at the top of your Phone fields setting to be dialed first.

Be diligent about marking Number Status Red and Green. You can do so from within Orum.

Do NOT delete prospects or numbers from Hubspot or Orum that have invalid numbers. This "kicks the can" down the road, so to speak, and creates create extra work later. Use Number Status instead.

CSV (Microsoft & Google)

"Phone" must be in the column header for Orum to recognize that column as phone data when you load your list.

Orum offers a "number status" feature for CSV users. You can mark any Number Status Valid, Questionable, or Invalid.

• Green (Valid) numbers will be prioritized first regardless of your Phone fields order.

• Red (Invalid) numbers will not be dialed, even if they are selected as a Phone field.

CSV Best practices:

Make sure every list you upload has the right Phone fields. Orum will not cross reference other lists for Phone field data.

Ask what Phone field(s) have the best data for your organization and arrange these at the top of your Phone fields setting to be dialed first.

Be diligent about marking Number Status Red and Green. You can do so from within Orum.

Do NOT remove numbers in Orum that are invalid numbers. This "kicks the can" down the road, so to speak, and creates create extra work later. Use Number Status instead.