Introductions help a sender find a possible route to a person or company through someone else. Distill can show relationship paths, save a selected connector, and prepare an introduction-request campaign.
This is useful when a known intermediary could provide a more relevant route than contacting the target directly. Networks explains the underlying relationship data and searchable audiences.
The people involved#
| Role or record | Meaning |
|---|---|
| Sender | The person whose outreach asks for the introduction. |
| Target | The person the sender ultimately wants to meet. |
| Connector or intermediary | The person asked to help make that introduction. |
| Introduction path | A possible route from the sender to the target through available relationships. |
| Selected connector | A connector chosen for a target; selection is separate from sending a request. |
A path records a possible route. It does not establish that the connector agrees, endorses the sender, or has completed an introduction.
Explore introduction paths#
Introduction views can show possible routes to a person or company. Available paths may involve your own relationships, shared Distill connections, or organization members, depending on the view and access.
The starting person is significant. A normal profile view can use the viewer's network. A campaign context can use the campaign sender's network, and supported project views can use a selected project member. Being able to see a target's profile is not the same as evaluating a path from the correct sender.
Introduction views can include an organization's wider network only when the person whose network is being viewed is an administrator of that organization. A person may still appear through a direct or shared relationship when that organization's wider network is restricted. This introduction-view rule is separate from the search scopes described in Networks. Selecting another person's network in a project also requires project access and an active project membership for that source person.
Path data may need time to become ready. A loading state can mean that the sender's connection import is unfinished or that mutual-connection data is being refreshed. Other views can use relationship data already available.
A blank result can therefore have several explanations: no recorded path in that scope, missing data, an unfinished refresh, or viewing a different person's network. It is not proof that the target has no real-world connection to the sender.
Save the connector for a target#
A list's Intro Paths column can retain selected paths for individual targets. The app supports discovered paths and manually supplied connectors. A manual connector can be a known person or a person identified by name and email.
A search prepared from a connector list can also fill Intro Paths automatically after it saves targets. This happens in the background and preserves paths already selected on a row. The first available qualifying connector in list order supplies the saved path; up to two additional possibilities can appear as Also via. This is not a ranking of relationship strength or proof that anyone has agreed to help.
For this workflow, paths start from the network owner named on the first available connector list, falling back to the search owner when none is named. Once the network owner's own LinkedIn import has completed, connectors not recorded as their first-degree connections are excluded from the automatic fill. The Networks guide explains team-assisted setup and data limits.
Manual selection is useful when you know about a relationship that the available data does not capture. It records the route you want to use. It does not turn that route into an independently verified relationship.
The target and connector remain separate people. A connector cannot be the same person as the target for an intermediary request. The saved path needs to belong to the target row it is attached to.
Showing Also via alternatives is different from saving several separate paths. The list can retain several paths, but an Intro Path campaign does not automatically choose one best connector. Each distinct first connector saved for a target can create a separate outreach entry. If Alex and Sam are both selected for Jordan, both can become recipients of requests about Jordan, subject to the campaign's checks and sending controls. Repeated paths through the same first connector count as one outreach entry for that target within the campaign.
Choosing a connector therefore matters before the list is used for outreach. Connection records alone do not establish relationship strength, recent introduction requests, or willingness to help. Saving paths alone does not send messages; a connected campaign can subsequently use those selections.
See Lists for list context, sharing, exports, and campaign connections.
Direct outreach and introduction requests#
Direct outreach contacts the target. An Intro Path campaign contacts the selected intermediary about the target.
For example, Maya wants to meet Jordan, a partnerships leader. Alex is a plausible connector. In direct outreach, Jordan receives Maya's message. In an introduction request, Alex receives the request about Jordan. A personalized introduction request needs context about why Maya wants to meet Jordan, while keeping Alex's role clear.
Distill can prepare introduction-request messaging and coordinate its configured campaign steps. A selected path, a generated message, a sent request, a positive reply, and a completed introduction are different outcomes. Sending the request does not establish that Alex agreed or that Jordan received an introduction.
On Agent, outreach usage is charged against the target person, not separately for every intermediary. The same target counts once per organization within the six-month window described in Plans and usage. This billing rule does not limit how many connectors can receive a request.
A campaign still depends on its sender, source lists, available recipient details, channels, message configuration, and outreach controls. Adding or changing selected paths in a list used by a campaign can affect the candidates available for outreach. These changes affect the account, not just the notes shown on a list. See Campaigns and personalization.
What an assistant can access#
A connected assistant can create a supported Intro Path campaign from an eligible targeting group and its lists. Previously selected paths can affect the campaign’s recipients.
The current connector does not expose a general tool for listing every introduction path or editing structured Intro Paths column values. The app’s path-discovery and selection features are broader. A supported campaign action therefore does not mean the assistant can complete every path-selection step directly.
Available tools and their guidance determine which steps can be handled through the assistant and which remain in Distill. Using an assistant explains access and tool availability.
Common questions#
Does having many mutual connections mean an introduction will work?#
No. Connection counts describe overlap, but do not measure willingness, trust, or how recently people spoke. A specific, supported relationship and the sender’s own knowledge can be more useful than a large count.
Can I choose someone I know to ask for an introduction?#
Yes. The app can save that person manually in an Intro Paths column, including a connector identified by name and email. This records the route you selected; it differs from Distill independently discovering evidence for that relationship.
If I choose two connectors for one person, who gets the request?#
Each distinct first connector can produce an outreach entry for that target in an Intro Path campaign. Distill does not automatically select a single best connector from those saved choices. Repeated paths through the same first connector count as one entry for that target within the campaign. Sending checks still apply.
Why do I see different paths when I change the sender?#
Paths depend on whose network is being viewed. A normal profile view can use the viewer, while a campaign uses its sender and supported project views can use a selected member. Organization-network access also depends on that source person’s permissions.
Does an empty introduction result mean we have no way to reach someone?#
No. There may be no recorded path in that scope, or the data may be missing, still loading, or coming from a different sender’s network. Customer knowledge can supply a manual route when the recorded data does not capture it.
Who receives the message in an introduction campaign?#
The selected connector receives a request about the target. Direct outreach goes to the target instead. A sent request or positive reply is not itself a completed introduction.
Can an assistant send an introduction as soon as it sees a path?#
A path is research, not permission to send. Sending requires an authorized campaign action and a ready campaign. The current connector also does not expose every path-selection step available in the app.