AI Deployment Authority
Back to Library

Function: Referral systems

AI Workflow for Warm Introduction Tracking

Deployment Brief

Use this workflow when introductions come through email, texts, calls, or partners and need to be handled with care.

Difficulty

Low

Revenue impact

Medium

Operational impact

Medium

Risk level

Medium

When it runs

A partner, customer, advisor, or contact offers or sends a warm introduction.

Evidence in

introducer namerecipient and companypermission or consent contextreason for introductionsource relationshipintro messageownernext action and thank-you rules

What AI prepares

  • warm introduction record
  • context summary
  • owner follow-up task
  • thank-you reminder
  • outcome status
  • measurement event for referral pipeline

Decision rules

  1. Confirm permission before outreach.
  2. Preserve why the intro was made.
  3. Assign one owner quickly.
  4. Close the loop with the introducer.
  5. Do not automate relationship-sensitive messages without review.

Human approval point

Sales or relationship owner reviews consent, context, message, timing, and thank-you follow-up before outreach.

What stays human

  • Do not automate relationship-sensitive outreach, repeated follow-ups, thank-you messages, or referral asks without owner review.

Quality and stop gates

  • Source evidence is attached
  • Consent or relationship context is reviewed
  • Human owner is assigned
  • Stop rules are visible
  • Measurement event is logged

How it is measured

  • Track intros received, follow-up time, meetings booked, outcomes, thank-you completion, referral source quality, and dropped intros.

Systems involved

CRM or customer systemEmail or messaging platformCustomer notesOwner review checklist

Workflow Dataset Record

Deployment evidence and duplicate boundary

This section is generated from the enriched workflow dataset. It is designed for pilot planning, not as validated outcome evidence.

Buyer Problem

Warm introductions happen across inboxes and relationships without a tracked ask, introduction owner, follow-up status, or reciprocity context.

Economic Logic

The workflow protects relationship capital by making warm intros intentional, permissioned, and followed through.

Baseline Metric

warm_intro_followthrough_rate

Share of warm introduction requests with target, introducer, permission basis, intro status, follow-up owner, and outcome logged.

Source system: CRM, email, relationship notes, referral tracker

Minimum Viable Pilot

Duration
45 days
Sample
All warm introduction requests from one team
Owner
Founder, sales leader, or revenue operations
Threshold
90% of requested introductions have permission basis, status, owner follow-up, and outcome logged.

Unique Workflow Test

Review warm intro requests for target, introducer, permission basis, ask specificity, intro sent, owner follow-up, outcome, and thank-you loop.

Duplicate Guard

Keep separate from referral tracking. Warm introduction tracking is relationship-capital management; referral tracking is source attribution management.

Not Ready If

  • Relationship owner is unknown.
  • CRM cannot track introduction status.
  • Team will not log follow-up outcomes.

Claim level: Directional. Sources support workflow mechanics and pilot design unless field evidence is attached.

HubSpot Sales Automation Guide

Sales automation should start with repetitive revenue work, clean CRM data, routing, sequences, baseline metrics, and regular audit.

Salesforce Lead Management Documentation

Lead records, statuses, owners, conversion, and source tracking are CRM operating objects that can be measured.

NIST AI Risk Management Framework

AI workflows should include risk mapping, measurement, governance, and accountable human oversight.

Keep moving

Where this workflow connects next

A useful AI build rarely lives on one page. Check the surrounding workflow, the decision rule, and the deployment path before you commit budget.

Workflow library

Browse revenue workflows

Find adjacent workflows before choosing the first place to deploy AI.

Open

Decision tool

Automate vs. keep manual

Check which parts should stay human before this workflow touches customers or records.

Open

Industry fit

Browse industries

See how this workflow changes by revenue model, buyer urgency, delivery risk, and customer handoff.

Open

Service path

AI Deployment Services

Compare the practical ways ADA can help turn one workflow into a working deployment.

Open

Revenue review

Request a workflow review

Bring this workflow and the business number it should move.

Open

Adjacent workflows

Referral TrackingPartner Referral ManagementReferral Request TimingCustomer Advocate Identification

TL;DR

A warm intro is borrowed trust. Tracking should protect the relationship, not just create a lead.

What is warm introduction tracking?

Warm introduction tracking is the process of recording the context, consent, owner, follow-up, outcome, and thank-you loop for introductions made through existing relationships.

Who is this workflow for?

  • Consultants, agencies, service businesses, founders, advisors, and partner-led sales teams.
  • Companies where referrals and introductions drive meaningful revenue.
  • Owners who want to avoid dropped or awkward follow-ups.

What breaks in the manual process?

The manual process fails when intros live in inboxes and memory. Follow-up gets delayed, context disappears, and the introducer never hears what happened.

How does the AI-enabled process work?

The workflow extracts intro context, names, consent, relationship notes, owner, and next action. It prepares follow-up tasks and thank-you reminders for review.

What does this look like in practice?

Example scenario: A client introduces a founder to another operator by email. The workflow records who introduced whom, why, what permission was given, drafts a short response for the owner, and schedules a thank-you note after the first meeting.

What decision rules should govern this workflow?

  • Confirm permission before outreach.
  • Preserve why the intro was made.
  • Assign one owner quickly.
  • Close the loop with the introducer.
  • Do not automate relationship-sensitive messages without review.

What are the implementation steps?

  1. Trigger: A warm introduction is offered or received.
  2. Inputs collected: The workflow collects introducer, recipient, consent, context, relationship, message, owner, and next-action rules.
  3. AI/system action: AI prepares an intro record, context summary, follow-up task, and thank-you reminder.
  4. Human review point: Relationship owner reviews context, consent, message, and timing.
  5. Output delivered: Approved follow-up is sent or queued.
  6. Measurement logged: Response, meeting status, outcome, source, and thank-you completion are logged.

Required inputs

  • introducer name
  • recipient and company
  • permission or consent context
  • reason for introduction
  • source relationship
  • intro message
  • owner
  • next action and thank-you rules

Expected outputs

  • warm introduction record
  • context summary
  • owner follow-up task
  • thank-you reminder
  • outcome status
  • measurement event for referral pipeline

Human review point

Sales or relationship owner reviews consent, context, message, timing, and thank-you follow-up before outreach.

Risks and stop rules

  • intro is followed up without consent
  • context is lost
  • introducer is not thanked
  • relationship-sensitive message is automated too aggressively

Stop the workflow when consent is missing, customer context conflicts, unresolved issues exist, timing is poor, or the next action would create a customer-visible offer, expansion ask, or relationship-sensitive message without owner approval.

Best first version

Track each warm intro with source, recipient, context, permission, owner, next action, and thank-you status.

Advanced version

Add referral-source reporting, partner attribution, intro quality scoring, and follow-up SLA reminders.

Related workflows

Measurement plan

Track intros received, follow-up time, meetings booked, outcomes, thank-you completion, referral source quality, and dropped intros.

What not to automate

Do not automate relationship-sensitive outreach, repeated follow-ups, thank-you messages, or referral asks without owner review.

FAQ

What is warm introduction tracking?

It is the process of tracking introductions, context, consent, follow-up, outcome, and thank-you loops.

What can AI prepare?

AI can prepare intro records, context summaries, follow-up tasks, and thank-you reminders.

What should stay under human review?

Consent, message tone, relationship context, timing, and thank-you language should stay under owner review.

What is the simplest first version?

Track source, recipient, context, permission, owner, next action, and thank-you status.

How should this workflow be measured?

Measure intro follow-up time, meetings booked, outcomes, thank-you completion, and dropped intros.

Further Reading

Speed-to-lead AI workflow

A field report on faster lead response without losing evidence, routing, consent, or owner review.

Read Report