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

# Intro Requests

> Track the ask, from request to answer

An intro request is the tracked ask on a path: you, asking a connector to
introduce you to someone at an account. It moves through four states.

## States

| Status      | Meaning                                                       |
| ----------- | ------------------------------------------------------------- |
| `requested` | You've asked. The drafted message is ready for the connector. |
| `sent`      | The connector has forwarded it.                               |
| `accepted`  | The prospect said yes.                                        |
| `declined`  | The prospect said no.                                         |

A path holds at most one open request at a time.

## Requesting an intro

From a path's drawer, draft the message and send the request. This marks the
path `requested` and stores your message. The People table's **Intro** column
shows the current state as a pill; click it to move the request along to Sent,
Accepted, or Declined as you hear back.

## Why this exists

Every other action in Clustr — a status, a tag, a push to your CRM — happens
inside your systems. An intro request is the one action only Clustr can drive
end to end, because it's the one that runs through a person, not a database.
Tracking it turns "did that intro ever happen" from a question you'd have to
ask your connector into a column you can filter, sort, and build a
[Workflow](/workflows) on: *"path requested seven days ago with no answer: remind me."*

## Filtering and building on it

Intro status is a column like any other, so it's a filter, so it's a [saved
view](/saved-views), so it can drive a Workflow. The People table's Intro column
is hidden until your workspace has at least one request, then shows itself
automatically.