How to Track Warm Introductions in Your CRM: A Practical Setup Guide

Most CRM source fields are designed for marketing attribution, not sales channel tracking. The default options ("inbound," "paid search," "organic," "event," "referral," "outbound") do not distinguish a warm introduction (a specific trusted third party actively vouching for the connection) from a referral program (a formal incentive scheme) from a cold outreach reply. When a warm introduction is logged as "referral" or, more commonly, not logged at all because none of the options fit, the channel becomes invisible. The fix is not to redesign the entire source taxonomy. It is to add one value, "warm introduction", with a definition the team understands and applies consistently. Every introduction sourced from an employee, a customer, or a partner gets this value. Everything else stays in its existing category. That single addition is what makes the channel measurable.

Warm introductions have a dimension that no other demand channel has: the specific person who made the introduction. That person’s identity determines the quality of the trust transfer, drives the conversion rate, and should determine how you invest in relationship maintenance. In most CRM setups, the connector is recorded nowhere or, at best, in a free-text notes field buried in the contact record, where it cannot be searched, aggregated, or sorted. Without a connector field, there is no way to answer the basic question of which connectors in your network are generating the most valuable introductions. You cannot calculate per-connector conversion rates, identify which relationships are overdrawn, or decide which people deserve your reciprocal investment. The absence of a connector field is what turns a set of individual introductions into an invisible, unmanaged channel.

Introduction-to-meeting conversion rate is the most important metric for understanding how your warm introduction channel performs, but it requires knowing when the introduction was made, not just when the contact was created. A warm introduction often precedes a first meeting by days or weeks. If the only date in the CRM is the contact-created date or the deal-open date, the time between introduction and meeting cannot be calculated. The introduction cycle, from introduction made to first conversation to deal close, becomes invisible. Logging an introduction date as a distinct field, separate from contact creation and deal creation, is the change that makes cycle-time analysis possible.

A warm introduction can have one of four outcomes: the recipient agreed to meet (converted), the recipient declined, the introduction was sent but went unanswered (no response), or the introduction was agreed to by the connector but never actually sent. Most CRMs capture deal outcomes at the opportunity level (won or lost) but do not capture what happened at the introduction level. Without introduction-level outcome data, you cannot calculate conversion rates accurately (a non-response is different from a decline), identify which connectors produce the most accepted introductions, or understand where in the introduction pipeline you are losing the most opportunities.

Add "Warm Introduction" as a value in the existing source field on the Contact record. The definition the team should apply consistently: a message delivered by a named third party who has a pre-existing relationship with the recipient and explicitly vouched for the value of the connection. A LinkedIn connection request mentioning a mutual contact is not a warm introduction by this definition. A forwarded email in which a trusted contact says "I think you two should talk and here is why" is. The value should be set when the introduction is made, not at contact creation, not when the deal opens. If your CRM does not have a source field on the Contact record (only on the Lead or the Deal), add one, or document that the Source field on the Deal is what to populate for introduction-sourced contacts.

Add a "Connector Name" custom field (a single-line text field or a lookup to an existing contact) on the Contact or Deal record. This field captures who made the introduction. The convention the team should follow: use "First Last" format, consistent with how the person appears in the CRM or in your contacts list, so you can later sort and aggregate by connector without deduplication work. If the connector is already in your CRM (as a customer, a partner contact, or a former employee), a lookup field that references their existing record is better than a free-text field: it enables direct relationship analytics between connector and introduced contact. If the connector is outside the CRM, a text field is sufficient. The field should be required when Source is set to "Warm Introduction" to enforce completeness.

Add an "Introduction Date" date field on the Contact or Deal record. Populate it when the introduction is actually made: when the connector sends the email, the Slack message, or the LinkedIn message connecting the two parties. This is the timestamp from which all introduction-pipeline cycle times are calculated: introduction-to-meeting speed, introduction-to-deal duration, and the warmth half-life (the research-backed observation that a warm introduction that does not result in a meeting within 48 hours is significantly less likely to convert). The field is distinct from the Contact Created date (which captures when the record was added to the CRM, often later than the introduction) and the Deal Created date (which captures when the opportunity was opened, often after an introductory meeting).

Add an "Introduction Outcome" dropdown field with four values: Accepted (the recipient agreed to meet), Declined (the recipient explicitly declined), No Response (the introduction was sent but went unanswered after the follow-up window), and Not Sent (the connector agreed to introduce but the introduction was never made). Populate this field when the outcome is known, typically within two weeks of the introduction date. This field is what distinguishes a tracked introduction channel from an untracked one: it captures the denominator for conversion rate calculations. Without knowing how many introductions were attempted and what happened to each, conversion rates cannot be calculated and the channel cannot be improved. The "Not Sent" outcome is particularly valuable. It reveals introductions that were agreed to but not executed, which is a loss in the connector workflow rather than the sales process.

When you ask a connector to make an introduction on your behalf, create the Contact record in your CRM immediately. Do not wait for the introduction to be sent. Set the Source to "Warm Introduction," the Connector Name to the person you asked, the Introduction Date to today’s date (as a placeholder that will be updated when the introduction is actually sent), and the Introduction Outcome to "Not Sent." This stage prevents introductions that fall through from disappearing from your tracking. If the connector never sends the introduction, the record stays in the CRM with an outcome of "Not Sent", which is data. It tells you that your ask rate is higher than your send rate, that a specific connector agreed to introduce but did not follow through, and where in the workflow you are losing potential introductions.

When the introduction is sent, meaning the connector’s email or message goes to the recipient, update the Introduction Date field to the actual send date. The CRM owner assigned to the contact should also receive a task or notification to follow up within 24–48 hours of the introduction date, per the warmth half-life research. At this stage, the Introduction Outcome remains "Not Sent" until the recipient responds. The 48-hour follow-up window is the most important action in the introduction workflow: a BCC protocol response that moves the connector to BCC, thanks the connector specifically, and proposes concrete time slots to the recipient. Missing this window is the single largest driver of introduction non-conversion.

When the outcome is known (a meeting is booked, a decline is received, or two weeks have passed without a response), update the Introduction Outcome field. If the introduction resulted in a meeting, log the meeting and proceed with the normal sales workflow. If the outcome is Declined or No Response, note the reason in the contact record if known (the connector’s relationship with the recipient was weaker than assumed; the timing was wrong; the recipient’s company was already evaluating a competitor). The outcome data feeds directly into per-connector conversion rates: which connectors produce introductions that are accepted, and which produce introductions that go unanswered? That question drives relationship investment decisions. After logging the outcome, close the loop with the connector: a brief message on what happened. This is the step that sustains the connector relationship and makes future introductions more likely.

In HubSpot, source tracking lives on the Contact record as the "Original Source" property, which is set automatically by HubSpot based on how the contact first entered the system, and cannot be edited to "Warm Introduction" directly. The workaround is to create a custom Contact property called "Acquisition Channel" (single-line dropdown) and add "Warm Introduction" as a value alongside any existing values your team uses. Set this property as a required field in the Contact creation form so it is never left blank. For the connector name, add a "Connector Name" custom Contact property (single-line text or a Contact-type association). For the introduction date, use a "Introduction Date" custom property (date picker). For the introduction outcome, add "Introduction Outcome" (dropdown: Accepted / Declined / No Response / Not Sent). Create a Contact list view filtered on Acquisition Channel = "Warm Introduction" so the introduction pipeline is visible in one place. A HubSpot deal board filtered on deals where the associated contact has Acquisition Channel = "Warm Introduction" gives you introduction-sourced pipeline at a glance.

In Salesforce, the standard Lead Source picklist can be extended with "Warm Introduction" as a value, with no custom field required. Go to Setup → Object Manager → Lead (or Contact) → Fields & Relationships → Lead Source → Values and add "Warm Introduction." For the connector name, add a custom text field on the Lead and Contact objects (e.g., "Connector_Name__c"). For the introduction date, add a custom date field ("Introduction_Date__c"). For the introduction outcome, add a custom picklist ("Introduction_Outcome__c") with the four values. A validation rule that requires Connector_Name__c and Introduction_Date__c when Lead Source = "Warm Introduction" enforces data completeness without relying on rep discipline. Build a Salesforce report on Contacts and Opportunities where Lead Source = "Warm Introduction," grouped by Connector_Name__c, to surface per-connector conversion rates. A dashboard component from that report gives sales leadership a live view of the introduction channel.

If your CRM does not support custom fields, if the team lacks the administrator access to add them, or if you want to validate the tracking discipline before investing in CRM configuration, a shared spreadsheet works for teams generating fewer than ten introductions per month. The minimum viable columns are: Contact Name, Company, Connector Name, Introduction Date, Introduction Outcome (dropdown via data validation), Notes, and CRM Link (a direct link to the contact record so the spreadsheet supplements rather than replaces the CRM). The spreadsheet captures the four fields that most CRMs do not have natively and produces enough data to calculate conversion rates, identify per-connector patterns, and make the case for a proper CRM implementation. Treat it as a 90-day pilot, not a permanent solution. The goal is to establish the tracking habit and demonstrate the value of the data before investing in the configuration work.

Log the introduction on the Contact record, then link the deal to the contact as normal. This preserves the introduction data even if the deal is lost or abandoned: the contact still exists and the introduction history is retained. If your CRM makes it easier to log custom fields on the Deal record, that works too, but be aware that if you ever lose the deal record (through a merge, a deletion, or a data migration), the introduction attribution goes with it. On the Contact record, the data persists independently of the deal outcome.

Log each introduction separately in the notes, but attribute the Contact record to the first introduction that led to a meaningful conversation. Subsequent introductions from different connectors are worth noting (they tell you that the contact has multiple warm paths in your network), but for conversion-rate calculations, the first successful introduction is what counts. If the contact is already in your CRM from a prior cold outreach attempt, update the Source field to "Warm Introduction" when the first warm introduction converts, so the pipeline attribution reflects how the contact actually became an opportunity.

Log these with the same four fields and mark the source as "Warm Introduction." The distinction between a proactive outbound ask and an unsolicited referral matters for understanding your connector program but not for measuring the channel. Both are warm introductions and both should be tracked identically. In the Notes field, you can add "unsolicited referral" to distinguish the acquisition type if your team wants to segment that way later, but the core four fields are the same regardless.

The most effective enforcement is making the required fields appear at the moment of contact creation, not as an afterthought. In HubSpot, add the Introduction Channel and Connector Name fields to the required-field list on the Create Contact modal. In Salesforce, use a validation rule that blocks saving a contact with Lead Source = "Warm Introduction" without a Connector Name and Introduction Date. When the fields are required at creation, the habit is built into the workflow rather than relying on retrospective data entry. Start with just two required fields (Source and Connector Name) rather than requiring all four simultaneously. Adoption is higher when the additional data collection is minimal.

The most actionable use is per-connector conversion rate: of all the introductions each connector has made, what percentage resulted in an accepted meeting? This identifies which connectors have strong relationships with the types of prospects you are targeting and which connectors’ social capital with that audience is weaker than their willingness to introduce. Segment by introduction-to-meeting conversion rate and focus your relationship maintenance investment (the loop-closes, the reciprocal value, the genuine relationship upkeep) on the connectors whose introductions convert at the highest rate. A connector with a 70 percent acceptance rate is worth far more investment than a connector with a 15 percent rate, regardless of how many introductions either one makes.

LetsBridge uses a structured double opt-in workflow: the connector agrees to make the introduction, the recipient agrees to be introduced, and only then does the introduction happen. That structure generates a timestamped record of every introduction automatically: who requested it, who made it, when it was sent, and whether the recipient accepted. The four fields described in this article are logged by the platform as a side-effect of how the introduction works, rather than requiring rep discipline to populate them after the fact. For teams where the core problem is that introductions happen informally and never make it into the CRM, the structured workflow approach eliminates the attribution gap at the source.