Skip to main content
In Salesforge, leads and contacts represent the same operational entity. Internally, the domain model is called a lead. In public-facing workflows and API language, the same record may be described as a contact. For documentation purposes, the important concept is that both names refer to the same person or company-level record used in outreach workflows.

​
Identity model

A lead or contact is primarily identified through one of two outreach identities:
  • Email: the email identity used for email-first workflows.
  • LinkedIn identity: the LinkedIn profile identity used for LinkedIn-first or multichannel workflows.
In practice, a record may be centered on email, LinkedIn, or both. Supporting fields such as first name, last name, and company add context, but email and LinkedIn identity are the primary fields that anchor the record in sequence and conversation workflows.

​
Role in outreach workflows

Leads or contacts are the records that sequences enroll, threads attach to, and sender actions target. They are not just profile records. They are the operational unit that moves through sequencing, receives messages, replies in threads, and accumulates status or workflow outcomes over time. For a concrete multichannel example, see Create a multichannel sequence, which creates email-only, LinkedIn-only, and mixed-channel lead records before enrollment.

​
Practical usage patterns

  1. Model leads and contacts as one concept in your integration layer to avoid unnecessary duplication.
  2. Treat email and LinkedIn identity as the primary outreach anchors for the record.
  3. Assign leads or contacts to sequence workflows only after sender and sequence setup is ready.