> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getintrod.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Introductions

> Prepare and track human-reviewed warm introduction requests without confusing workflow state with message delivery.

Use **Introductions** to store the target, connector, request context, and current workflow state for a warm introduction.

<Card title="Open Introductions" icon="arrow-up-right" href="https://app.getintrod.ai/introductions">
  Sign-in is required. The page shows introduction records available to your workspace.
</Card>

## Two separate responsibilities

| Introd records                            | A person remains responsible for                              |
| ----------------------------------------- | ------------------------------------------------------------- |
| Target and connector context              | Confirming the identities and relationship                    |
| Draft subject and message                 | Reviewing every claim and edit                                |
| Pending, active, or closed workflow state | Contacting the connector through an approved channel          |
| Stored progress and scheduled date        | Confirming whether an external message was actually delivered |

<Warning>
  Creating, submitting, scheduling, or moving an introduction record does not deliver an email or LinkedIn message. Introd tracks the workflow; external outreach remains a human action.
</Warning>

## Core workflow

<Steps>
  <Step title="Review the path">
    Confirm the target, connector, and evidence in [View and verify paths](/people/view-paths).
  </Step>

  <Step title="Prepare the request">
    Edit the subject and message, remove unverified claims, and save a draft when it needs more work.
  </Step>

  <Step title="Create the tracked request">
    When ready, move the record into the pending workflow. Complete any external outreach yourself.
  </Step>

  <Step title="Maintain the status">
    Use the pipeline or list to keep the stored state aligned with what actually happened.
  </Step>
</Steps>

<Columns cols={2}>
  <Card title="Prepare a request" icon="edit-3" href="/introductions/create-request">
    Review composer fields and the difference between save, submit, and schedule.
  </Card>

  <Card title="Track requests" icon="list-checks" href="/introductions/track-requests">
    Search, filter, sort, move, and archive introduction records.
  </Card>
</Columns>