> For the complete documentation index, see [llms.txt](https://themochi-app.gitbook.io/mochi-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://themochi-app.gitbook.io/mochi-docs/feature-and-settings/leads.md).

# Leads

The Leads page is your sales pipeline — every Instagram conversation that's been identified as a potential customer.

## Pipeline Stages

Every lead moves through a funnel:

| Stage           | Meaning                                                   |
| --------------- | --------------------------------------------------------- |
| **New**         | Lead just came in. No team member has responded yet.      |
| **In Contact**  | A team member has engaged with this lead.                 |
| **Qualified**   | Lead meets your criteria and is worth pursuing.           |
| **Unqualified** | Lead doesn't fit. Removed from active pipeline.           |
| **Booked Call** | Lead has a call scheduled (via Calendly or manually set). |
| **No Show**     | Lead missed their booked call.                            |
| **Deposit**     | Lead has made a partial payment.                          |
| **Won**         | Deal closed. Full payment received.                       |
| **Lost**        | Deal didn't close.                                        |

Stages update automatically when certain actions happen (e.g., Calendly booking moves lead to Booked Call), or you can change them manually.

## Lead List

### Viewing Leads

The lead list shows all your leads in a table (desktop) or cards (mobile). Each entry shows:

* Lead name and Instagram username
* Current funnel stage
* Assigned setter and closer
* Tags
* Last activity date
* Payment status

### Filtering

Narrow down your leads using filters:

* **Date range** — When the lead was created
* **Team member** — Filter by assigned setter or closer
* **Funnel stage** — See only leads at a specific stage
* **Tags** — Filter by custom tags
* **Payment type** — Full payment, deposit, etc.
* **Source** — Where the lead came from

### Sorting

Sort by name, date created, last activity, or funnel stage.

## Lead Actions

### Individual Actions

Click on any lead to:

* **Change funnel stage** — Move them through your pipeline
* **Assign setter/closer** — Route the lead to the right team member
* **Add tags** — Apply custom tags for organization
* **Add payment** — Record a payment or deposit
* **Pin/Star** — Mark important leads for quick access
* **View timeline** — See full activity history
* **Add comment** — Leave internal notes for your team
* **Open conversation** — Jump to the DM thread in Inbox

### Bulk Actions

Select multiple leads to:

* **Bulk assign setter** — Assign a setter to multiple leads at once
* **Bulk exclude** — Remove multiple leads from your pipeline
* **Export to CSV** — Download lead data for external analysis

## Payments

Track payments directly on each lead:

* **Full payment** — Record the total deal amount
* **Deposit** — Record partial payment (lead moves to Deposit stage)
* **Installments** — Track multiple payments over time

When a payment is recorded with an amount, commissions are calculated automatically based on team member commission percentages.

## Lead Timeline

Every lead has a timeline showing their full history:

* When they first messaged
* Stage changes (with who changed it)
* Setter/closer assignments
* Payments recorded
* Comments added
* Calendly bookings


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://themochi-app.gitbook.io/mochi-docs/feature-and-settings/leads.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.