> ## 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.

# Introduction Statuses

> Interpret the introduction pipeline as a workspace tracker, not proof of external activity.

The **Introductions** pipeline groups stored records into workflow stages.

| Displayed stage | Use it for                                           |
| --------------- | ---------------------------------------------------- |
| Requested       | A request recorded as pending                        |
| Approved        | A request recorded as approved by the workflow       |
| Introduced      | A request marked as in progress or introduced        |
| Replied         | A stored state indicating a reply                    |
| Meeting         | A stored state indicating a meeting                  |
| Closed          | A completed, declined, cancelled, or archived record |

Stage labels reflect stored status. They do not independently confirm that a connector approved, a message was delivered, a target replied, or a meeting occurred.

## Keep status grounded in evidence

Update a record only after you have confirmed the corresponding event in the channel where it happened. Add enough context to distinguish a genuine reply or meeting from a planned next step.

Dragging a card to another column updates the Introd workflow state. It does not contact anyone.

<Warning>
  Several displayed stages can map to broader stored states. Use the selected record's details and your external communication history as the source of truth.
</Warning>