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

# Lists

> The pipeline in the sidebar. Stages To contact, Contacted, Responded, Passed.

**Lists** is the dashboard page (`/dash/explore/lists`). It is the recruiting pipeline — not the same thing as a [Target](/guides/targets). A Target finds and monitors people. A List is where you stage outreach.

Stages in the app (API slugs in backticks):

| Dashboard  | API          | When to use it           |
| ---------- | ------------ | ------------------------ |
| To contact | `to-contact` | Sourced, not reached yet |
| Contacted  | `contacted`  | Sequence or InMail sent  |
| Responded  | `responded`  | They replied             |
| Passed     | `passed`     | Out of process           |

`:id` on API routes is the list uuid **or** the name (`hot`).

## Add people

Person ids are LinkedIn slugs. You can also pass profile URLs — the slug is taken from `/in/…`.

Dashboard: Search or a person profile → **Add to list**. The Lists page does not accept pasted URLs — REST and MCP do.

REST: [POST /lists/:id/members](/api-reference/lists/add-members) with `slugs` or `urls`. Delete a list with [DELETE /lists/:id](/api-reference/lists/delete).

MCP: tool `collect` with `action=add` and `slugs`.

## Lists and Monitoring

People on a List show up in [Monitoring](/guides/monitoring) even if they are not **Monitored** on a Target. That is how a pipeline you already work stays live.

## Mapping to an ATS

Keep FreshTalent stages as sourcing state. When someone is a real candidate, create/update the ATS record from the LinkedIn URL, then set Contacted / Responded here so the two systems do not fight. Recipe: [ATS & CRM](/connect/ats-crm).