Contact
A Contact in Salesforce represents an individual person associated with an Account.
Definition
A Contact in Salesforce represents an individual person associated with an Account. Contacts store personal details like name, title, phone, and email, and serve as the primary record for tracking communications and relationships with people at your customer or prospect organizations.
In plain English
“Here's a simple way to think about it: a Contact is how Salesforce remembers the people behind every Account. Where Account is the entity, Contact is the human. Most outbound work is keyed off Contacts - emails, calls, sequences.”
Worked example
Under the "Pinnacle Corp" Account, a sales rep creates Contact records for three key stakeholders: Dana Kim (VP of Engineering), Marcus Lee (Procurement Manager), and Anya Patel (CTO). Each Contact has their direct phone number, email, and preferred communication method. When the rep logs a call, she links it to Dana's Contact record so the team knows exactly who was spoken to.
Why Contacts are how Salesforce remembers the people behind every Account
Companies don't make decisions; people inside companies do. The Contact is how Salesforce models those people - name, title, email, phone, the Account they belong to, the role they play in deals. Where Account is the entity the org sells to, Contact is the human relationship inside that entity. Every Email-to-Salesforce match, every call logged, every meeting captured ultimately ties to one of these records.
The reason data quality on Contacts matters disproportionately is that most outbound work is keyed off them. The marketing email sequence pulls from contact-level fields; the SDR's call list is driven by Contact data; the renewal forecast assumes the right champion is still at the company. Stale Contacts produce wasted outreach; missing Contacts produce gaps in coverage; well-maintained Contacts compound into a CRM that knows who to talk to, and how.
How to create Contact
Contacts represent the individual people you do business with — usually associated with an Account. The platform asks for surprisingly little; the friction comes from your org's page-layout and validation choices.
- Open the Contacts tab
App Launcher → Contacts. You can also create a Contact from an Account's related list (the most common pattern, because it auto-links the Account).
- Click New
Top-right of the list view. From an Account, use the Contacts related list's New button to skip the Account lookup step.
- Enter Last Name
LastName is the only platform-required field. Even single-name people (e.g., "Madonna") need something here — many orgs use a placeholder convention.
- Link an Account
Account is technically optional but virtually always required by org policy. Contacts with no Account become "private" Contacts and are sharing-restricted.
- Fill business fields your layout demands
Title, Email, Phone, Mailing Address — page layouts usually mark these as required even though the platform doesn't. Look for the red bar.
- Save
Save commits the record. Duplicate-management rules fire here against existing Contacts/Leads (typically by Email).
The only platform-required field. FirstName is optional.
- Contacts without an AccountId are "private" — visibility follows the orgwide default for Contact, which is often Controlled by Parent and breaks down without a parent.
- Email is not platform-required, but most orgs make it required via page layout because it's the join key to Marketing Cloud, Pardot, and outbound campaigns.
- Lead-to-Contact conversion creates a Contact with the Lead's data — don't double-create. Search Leads first.
How organizations use Contact
Contact data quality drives outbound campaigns; stale Contacts produce wasted outreach.
Contact role data feeds account-team mapping; deal stakeholder visibility improved.
Trust & references
Straight from the source - Salesforce's reference material on Contact.
- ContactsSalesforce Help
Hands-on resources to go deeper on Contact.
Test your knowledge
Q1. Who would typically configure or interact with Contact?
Q2. What best describes the purpose of Contact in Salesforce?
Q3. What happens when Contact data is not maintained properly in Salesforce?
Discussion
Loading discussion…