A Prospect Introduces a Colleague: Preserve the Warm Handoff

After a prospect explicitly introduces an identified colleague, preserve the introduction, assign one conversation owner, and continue within the context the prospect actually shared. Do not enroll both people as new cold leads, infer purchase authority from the introduction, or describe it as an endorsement stronger than the original message supports.

This workflow starts after identity and the explicit introduction are established. A reply from an unfamiliar address or a vague suggestion to contact someone requires an earlier identity and context check. Here, the task is to preserve a warm handoff without duplicating outreach or losing the reason for the conversation.

Confirm the introduction and its boundaries

Read the original thread in full. Identify the introducing person, the colleague, who is included, and the stated reason for bringing the colleague into the conversation. Preserve the original message reference rather than relying only on a referral tag or an automated summary.

Unify's sequence replies documentation explains how to review responses, inspect classifications, and reply with the engagement history available. A Referral classification indicates suggested contact context; it does not by itself prove an explicit introduction, verified identity, or the colleague's willingness to meet.

If the identity is still uncertain, use the different-address reply guide before proceeding. Do not resolve uncertainty by treating every person copied on a thread as the intended buyer.

Record any limit the introducing prospect expressed. They may be directing a narrow question, changing the owner of the discussion, or asking to step out. Preserve that instruction without expanding it into a general referral campaign.

Carry forward only the context that belongs in the handoff

The colleague needs enough context to understand why the conversation reached them. That usually means the actual topic, the introduction's stated purpose, and the question or action currently open. It does not require forwarding every private note or internal assessment associated with the account.

Separate three kinds of information: what the introducer said in the shared thread, what your team knows from approved account research, and what remains an inference. Do not merge them into one confident narrative that attributes all of the context to the prospect.

Use record inspection to review the account and person information already available. The find-and-enrich account contacts use case can support current-role research when needed. Enriched information should not overwrite the introduction's meaning or establish authority that nobody confirmed.

Before sharing additional material, check whether it is appropriate for the introduced colleague. A document approved for one recipient is not automatically approved for every person later added to a thread. Keep the permitted audience and any confidentiality boundary visible to the conversation owner.

Assign one owner for the continuation

Choose the person responsible for the next response, related tasks, and any internal handoff. Account ownership, the original sending mailbox, and conversation ownership may not be the same thing. Resolve those differences before multiple reps act.

Use task management and task creation to make the next action explicit. The task should identify the thread, introduced person, stated reason, context boundary, and intended continuation. A generic “follow up on referral” task leaves too much interpretation to the next owner.

The task overview helps distinguish work types, while task settings explain queue behavior. Check assignment and permissions when the conversation moves between teammates; do not assume a tag alone transfers responsibility.

If an account policy restricts who can engage, inspect the applicable engagement policy. The introduction is useful context, not a reason to bypass ownership controls or silently reassign the account.

Review existing outreach to both people

Inspect the introducer's enrollment and any existing activity involving the colleague. The colleague may already have a relationship with another rep, a separate conversation, or a restriction that changes the next action. Do not create a new cold enrollment simply because a new email address appeared in the thread.

The sequence enrollment documentation explains current status, simultaneous-enrollment rules, re-enrollment, removal, and version behavior. Sequence rulesets and exclusions provide further controls. Inspect the effective state rather than assuming the introduction reconciles it automatically.

A reply can end an active enrollment according to its configured ending conditions. That does not establish that all other outreach to everyone on the thread has stopped. Review pending tasks and messages for both people where you have the appropriate access.

Also inspect the consequence of changing a task. Under task completion behavior, completing or skipping a sequence task can advance the enrollment. Removing an obsolete task is not enough if the next email still treats the conversation as unanswered cold outreach.

Prepare a continuation that accurately acknowledges the introduction

The next message should orient the colleague without making them reconstruct the whole sales pitch. Acknowledge the introduction, state the topic within its actual scope, and ask or propose the next step supported by the thread. Review the sender and recipient list before sending.

Do not say the introducer recommended a purchase, approved a project, or identified the colleague as the decision-maker unless that was actually established. An introduction can indicate relevance while leaving responsibility, budget, and interest unknown.

If the colleague has not replied, avoid treating their presence on the thread as an affirmative commitment. If they do respond, use their words to update the next action. The introducer's earlier context should not override the colleague's own clarification or restriction.

Chat can help prepare a draft when given the appropriate context and explicit scope. Ask for a reviewable draft if that is the intended step. Inspect any generated account claim, recipient choice, and proposed action before execution; a polished response can still exaggerate what the introduction means.

The research-to-outreach use case is useful for adding relevant, supported context. Research should improve the question, not replace the human introduction with a new automated pitch.

Keep the original prospect's role explicit

Decide whether the original prospect should remain included based on the thread and their expressed preference. Do not assume they want to receive every subsequent message, and do not remove them in a way that obscures the introduction or contradicts an agreed collaboration.

If the appropriate recipient list is unclear, resolve it in the conversation or with the account owner. Avoid blanket reply-all behavior when the thread contains people who no longer need the material. Equally, avoid a separate cold email that discards the introduction and makes the colleague wonder how their address was obtained.

Preserve the original prospect's own follow-up state. An introduction does not necessarily mean their work is finished, nor does it mean they should continue receiving the old cadence. Record whether the next action belongs to the colleague, the introducer, both in a shared conversation, or no one until more context arrives.

If the handoff involves a requested resource, use a distinct fulfillment task with the asset and access boundary recorded. Do not mark the entire introduction handled merely because a document was prepared.

Use a warm-introduction handoff card

The following blank card keeps the introduction, identity, ownership, and next action together. It is an operating template, not a fabricated conversation or an observed customer result.

Keep the observation fields empty until evidence exists. Do not fill “agreed next action” with a rep's preferred meeting date when the colleague has not agreed. Record a proposed action as proposed.

If ownership changes internally, the receiving owner should acknowledge the handoff and review the thread before responding. The card should reduce reconstruction work without replacing the original conversation as the source of truth.

Preserve continuity in the CRM without inventing association

Where CRM activity is part of the process, review sequence CRM sync and the integration settings used by your workspace. Confirm the relevant record relationships and the activity that actually appears.

Do not assume an introduction automatically creates, merges, or associates the colleague with an account in the exact way your team expects. A thread can include an external adviser, partner, or another organization. The presence of two people in one email conversation is not enough evidence to assign them the same employer.

If a new person record is appropriate, use the approved identity and data-maintenance process. Preserve the introduction reference so later users understand the relationship. Avoid copying the same interaction into several records in a way that falsely inflates unique outreach or conversation counts.

The reply-classification guide covers classification work upstream. Classification and CRM storage are useful aids, but neither replaces the conversation owner's review of the actual handoff.

Handle silence or a changed role without resetting to cold outreach

If the colleague does not respond, inspect what was actually sent and whether a follow-up is appropriate under the relationship and stated context. There is no automatic entitlement to a long new cadence because an introduction occurred.

A follow-up should preserve the relevant question and the introduction's scope. Do not imply that the colleague already accepted responsibility or that the introducer is waiting on a decision unless that is supported. If the colleague redirects the conversation, record the new instruction and reassess ownership before sending again.

If the role or company information conflicts with the thread, resolve it rather than overriding the person's own statement with enrichment data. Keep uncertain facts visible and correct any pending message that relies on the wrong role.

The next-step planning use case supports explicit, owned follow-through. The relevant next step may be clarification, a resource, a meeting, or no further action; it should come from the conversation rather than an assumed funnel progression.

Check that the handoff stayed intact

A reviewer should be able to find the original introduction, identify the colleague, explain the stated reason, locate the current owner, and see what was actually done next. Confirm that duplicate or contradictory outreach has been reviewed and that any unresolved issue has an owner.

For a team-level quality check, define a snapshot of explicit introductions under review. Count introductions with evidence-backed identity, preserved context, assigned ownership, and a documented next-action decision as the numerator; use all in-scope introductions in that snapshot as the denominator. Report unresolved identity, access, and ownership separately. With no introductions in scope, report not applicable. This evaluates handoff completeness, not meeting conversion or automatic product performance.

The workflow does not establish native automatic introduction detection or colleague association in Unify. It describes how reps can use reviewed replies, contact context, and tasks to preserve the meaning of a real introduction.

Frequently asked questions

Does an introduction prove that the colleague is the decision-maker?

No. Preserve the stated reason for the introduction and verify the colleague's role separately. Relevance, purchasing authority, budget, and willingness to meet are different facts.

Should both people enter a new cold sequence?

No automatic enrollment is warranted. Review existing conversations, enrollments, ownership, and restrictions, then choose an appropriate continuation for the actual handoff.

Does Unify automatically detect and associate every colleague introduction?

The documentation inspected for this workflow does not establish automatic introduction handling or account association. Review the original thread, identities, record relationships, and next action explicitly.

Who should own the next response?

Assign one conversation owner who can inspect the thread and coordinate with the account owner. Make any internal handoff explicit so multiple reps do not send competing continuations.