Map warm introduction paths into a named target company

Why use this

1. A target account can have many apparently relevant employees, yet an introduction depends on a real relationship and the contact's willingness to help. Connection degree alone does not establish influence, closeness or permission to approach someone.

2. A bounded introduction-path table could make uncertain links visible before outreach. The requester could choose which relationships to verify and avoid asking a mutual contact to support a pitch based on an overstated or outdated connection.

Why an agent / simpler alternative

Useful judgment

Compare role relevance and evidence quality while separating platform connections from confirmed working relationships.

Simpler alternative

Ask a trusted colleague directly when the target and likely introducer are already known.

Unsuitable when

The task requires covert profiling, inferred personal traits or unsolicited contact without an approved purpose.

Proposed inputs

1. Name

   Target account brief

   Owner

   Requester

   Minimum scope

   Company, relevant function and intended business conversation

   Quality check

   Distinguish the desired role from a guessed decision-maker.

2. Name

   Authorized relationship sample

   Owner

   Account holder

   Minimum scope

   Permitted professional records and relationship notes

   Quality check

   Record freshness and avoid importing unrelated contact details.

Access and setup — proposed or unknown

Proposed minimum

1. Read-only, owner-supplied sample and a private candidate table.

Compatibility unknowns

1. Unknown: current runtime, account access, platform automation rules and relationship-data export support.

External actions requiring approval

1. Account access, saving relationship data, introduction requests and outreach to each intended recipient.

Expected deliverable and review checks

Proposed artifact

Candidate path table with role fit, evidence links, relationship uncertainty and verification questions.

Critical checks

1. Ranking explains evidence rather than inventing relationship strength.

2. No path implies a mutual contact has agreed to introduce anyone.

Missing output evidence

No new workflow run or output inspection is performed for this editorial layer. The linked implementation evidence retains the original source-specific outcome and artifact limits.

Failure signals and proposed responses

1. Signal

   A public connection is labelled a close colleague.

   Why it matters

   The recommendation can damage trust through an awkward request.

   Proposed response

   Replace the claim with the observed connection type and ask the owner to verify context.

2. Signal

   The named decision-maker has changed roles.

   Why it matters

   An introduction may target the wrong person.

   Proposed response

   Mark the role stale and pause ranking until dated evidence is supplied.

Effort and cost — unknown

Setup work

1. Define relevant functions and permitted relationship fields.

Ongoing review

1. Verify role freshness and proposed introducer suitability.

Unknowns

1. Unknown: account restrictions, data freshness and human relationship-verification effort.

First check — proposed, unexecuted

Status

proposed_unexecuted

Synthetic fixture

A fictional company has three role candidates and two possible introducers; one role is stale and one connection lacks context.

Acceptance checks

1. Flag stale and uncertain paths.

2. Produce no outreach text implying consent.

Stop conditions

1. Real social accounts, personal contact data or messages are required.

Limits

1. The proposed ranking aids owner review; it does not establish outreach consent, relationship strength or platform compliance.