> For the complete documentation index, see [llms.txt](https://docs.echevarrisports.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.echevarrisports.com/guia/en/crm-erp/contactos.md).

# Leads

Everything people send from the website forms lands here: Academy and camp sign-ups, Mix-in, visit requests and contact messages. You can also add leads by hand.

![The leads list](https://310662894-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUtfEXMFEU0mFg84Ri6hx%2Fuploads%2Fgit-blob-230dba121442b241e7eb32a2f2b01fd4ba45d5b7%2Fleads.png?alt=media)

## Kinds of lead

The chips at the top filter by kind. The number on each chip is the new leads nobody has handled yet.

| Kind           | Where it comes from             |
| -------------- | ------------------------------- |
| **Mix-in**     | Open days                       |
| **Academy**    | Academy sign-up                 |
| **Camp**       | Camp registration               |
| **Camp visit** | Request to visit the facilities |
| **Contact**    | General contact form            |

## Search and filter

* **Search**: by name, email or phone.
* **Status**: the lead's status (see below).
* **Label**: your own labels. Create and edit them with the **Labels** button.
* **Sport**, **Level** and **Age**: filter by the student's details. **Clear filters** removes them.
* **By person / By family**: groups siblings together.
* **⬇**: downloads what you're looking at as a CSV.
* **Metrics**: opens the marketing report (Office and Direction).

You can change the label and status right in each row, without opening the lead. The **Waiting** column says how many days it has been waiting. Rows marked **Possible spam** probably aren't from a real person.

![Labels](https://310662894-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUtfEXMFEU0mFg84Ri6hx%2Fuploads%2Fgit-blob-28e927005465e2c54f941ca02123c844f69de98b%2Fleads-labels.png?alt=media)

## Statuses

| Status                  | What it means                                                                                                                    |
| ----------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
| **New**                 | Just arrived. Nobody has handled it.                                                                                             |
| **Contacted**           | We've spoken to them.                                                                                                            |
| **Confirmed**           | They want to sign up.                                                                                                            |
| **Scheduling required** | They still need a schedule.                                                                                                      |
| **Partially scheduled** | Some of their classes have a schedule.                                                                                           |
| **Fully scheduled**     | All their classes have a schedule.                                                                                               |
| **Completed**           | Done.                                                                                                                            |
| **Cancelled**           | Cancelled.                                                                                                                       |
| **Did not enroll**      | They didn't sign up. The CRM asks why: price, schedule, location, no reply, chose another club, level or age, or another reason. |

{% hint style="info" %}
Recording the **Did not enroll** reason matters: Reports uses it to show why we lose clients.
{% endhint %}

## A lead's panel

Click a row to open its panel:

![A lead's panel](https://310662894-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUtfEXMFEU0mFg84Ri6hx%2Fuploads%2Fgit-blob-bb9cf92f0e96431f2ba8f909c4e55d62f47889fb%2Fleads-drawer.png?alt=media)

* The family's details and the **Call**, **WhatsApp** and **Email** buttons.
* The status history and the buttons to change the **Status**.
* **Everything they sent**: everything they filled in on the form.
* **How they found us**: fill it in if it's missing.
* **Academy terms**: whether they've accepted the terms. **Send terms & details link** sends them the link to accept and complete their details.
* **Classes**: add single classes to the booking (**Add classes**).
* **Payment links**: create and see this booking's payment links.
* **Emails sent** and **Team notes** (the team's internal notes).

Depending on the kind of lead, there are also buttons to:

* **Convert to Academy**: shows once the lead is confirmed. In one step it creates the student, their Academy plan and their group. See [From lead to Academy student](/guia/en/step-by-step/contacto-a-academia.md).
* **Confirm Mix-in place**: if the Mix-in day was full, gives them a place from the waitlist and emails the family.
* **Email payment options (all / deposit)**: for camps, sends the payment options: the full amount or the deposit.

## Adding a lead by hand

For phone calls or people who walk into the office:

1. Click **Add booking**.
2. Choose the kind.
3. Fill in the parent's and the students' details. **Add another student** adds siblings.
4. Depending on the kind, choose the camp weeks, the day of the visit or the days that suit them.
5. Add a note if needed, for example "Called in on Tuesday, wants a call back", and save.

![Adding a lead by hand](https://310662894-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUtfEXMFEU0mFg84Ri6hx%2Fuploads%2Fgit-blob-70c8201586fcee9b368a3349b739118ff88bcde5%2Fleads-add.png?alt=media)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.echevarrisports.com/guia/en/crm-erp/contactos.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.