Contact

A contact is a person or organization stored in a CRM or database, representing a potential or existing relationship with a business.

A contact is an individual person recorded in a CRM system or database, containing identifying and communication information used to manage business relationships. Contacts serve as the foundational unit of customer data in sales, marketing, and support operations.

The concept of a contact evolved from physical address books and Rolodex systems into digital records within CRM platforms such as Salesforce, HubSpot, and Pipedrive. In modern business contexts, a contact typically represents a human individual — as opposed to an account (a company) or a lead (an unqualified prospect). Contacts are used across the entire customer lifecycle: from initial outreach through post-sale support. In B2B environments, a single account may have dozens of associated contacts, each with different roles, decision-making authority, and communication preferences.

How Contacts Are Structured in CRM Systems

A contact record typically stores a standardized set of fields that allow teams to identify, reach, and segment individuals. Core fields include full name, email address, phone number, job title, and company affiliation. Most CRM platforms also support custom fields, enabling businesses to capture industry-specific data such as preferred communication channel, contract renewal date, or NPS score.

Beyond static data, contact records in modern CRMs are dynamic: they log interaction history, track email opens and link clicks, record meeting notes, and display associated deals or support tickets. This activity timeline gives sales and support reps full context before any interaction. For example, a rep opening a contact record in HubSpot can instantly see that the person opened three emails last week, attended a webinar, and has an open support ticket — all without switching tools.

• Core identity fields: name, email, phone, job title, company
• Relationship fields: associated account, owner (assigned rep), contact source
• Behavioral data: email engagement, page visits, form submissions
• Lifecycle stage: subscriber, lead, marketing qualified lead, customer, advocate
• Activity log: calls, meetings, notes, emails, support tickets
• Custom properties: industry-specific fields defined by the business

When and How Contacts Are Used

In a B2B sales workflow, contacts are typically created when a lead is qualified and associated with a specific company account. A sales development rep (SDR) might convert an inbound lead into a contact after a discovery call confirms budget, authority, need, and timeline. From that point, the contact moves through pipeline stages — from 'Meeting Scheduled' to 'Proposal Sent' to 'Closed Won' — with all activity tracked against their record. Enterprise deals often involve 6–10 contacts per account, each representing a different stakeholder: economic buyer, technical evaluator, legal reviewer, and end users.

In marketing, contacts are the target of segmented campaigns. A SaaS company might filter contacts by lifecycle stage and last activity date to build a re-engagement sequence for users who signed up but never activated. In customer support, contacts are linked to help desk tickets so agents can see the full relationship history. HubSpot reports that companies with complete contact records — including job title and company size — achieve 36% higher email open rates compared to those with incomplete data, underscoring the operational value of maintaining clean, enriched contact databases.