Contact or Person Object for Recruiting in Salesforce

In this episode, Brad Owens discusses the differences between contacts and person accounts in Salesforce, particularly in the context of recruitment. He explains how contacts are tied to accounts and can support a hierarchy, making them more beneficial for recruiters. Conversely, person accounts are individuals not associated with any company, which can lead to limitations in tracking and reporting. Brad also shares best practices for using contacts effectively, including the use of pool accounts for unemployed candidates.

takeaways
Contacts and person accounts serve different purposes in Salesforce.
Contacts are essential for tracking individuals in a business context.
Person accounts are useful when company affiliation is irrelevant.
Recruiters benefit from using contacts due to their historical association with accounts.
Contacts can support hierarchical relationships, aiding in organizational understanding.
Using the contact object is more future-proof for recruitment systems.
Recruiting firms should avoid creating multiple records for the same individual.
Pool accounts can help manage unemployed candidates effectively.
Asymbl is recommended as a flexible ATS for Salesforce.
Engaging with the audience through questions enhances the content.

Chapters
00:00
Introduction to Salesforce for Recruiters
04:14
Benefits of Using Contacts in Recruiting
06:48
Challenges with Person Accounts
08:29
Best Practices for Managing Contacts