> 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/step-by-step/contacto-a-academia.md).

# From lead to Academy student

A family has filled in the Academy form on the website. This is how they become a student with a group and a fee.

## 1. Find the lead

Go to **Leads** and click the **Academy** chip. The number shows how many new leads there are.

![Step 1: the Academy chip](https://310662894-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUtfEXMFEU0mFg84Ri6hx%2Fuploads%2Fgit-blob-cf12230f43e8ba3982c6773813a38a6b3ac5a7e1%2Fleads-academy-chip.png?alt=media)

## 2. Open the lead and call

Click the lead. Check **Everything they sent** (age, level, days that suit them…) and call or message the family with **Call**, **WhatsApp** or **Email**.

![Step 2: the 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)

## 3. Change the status

Once you've spoken to the family, click **Contacted** under **Status**. When they say yes, click **Confirmed**.

![Step 3: the status buttons](https://310662894-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUtfEXMFEU0mFg84Ri6hx%2Fuploads%2Fgit-blob-c4ad6fe2543173cce274aafaa5991e390d738cb9%2Fleads-status.png?alt=media)

{% hint style="info" %}
If they don't sign up in the end, click **Did not enroll** and pick the reason. That data feeds the reports.
{% endhint %}

## 4. Convert them into a student

With the lead confirmed, the **Convert to Academy** button appears. Click it.

![Step 4: Convert to Academy](https://310662894-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUtfEXMFEU0mFg84Ri6hx%2Fuploads%2Fgit-blob-70c504f1ab90175b4fa54d3bacfe58f24623e303%2Fleads-convert.png?alt=media)

## 5. Check the enrolment

**Enrol** opens with the form's details already filled in (family, student, date of birth, level, school…).

1. Check the details and complete anything missing.
2. Choose **How they pay** (**Monthly plan**, **Pays per class** or a class pass) and the hours a week.
3. Choose their group or groups. If a new one is needed, create it with **+ New class**.
4. Click **Enrol**.

![Step 5: the enrolment, already filled in](https://310662894-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUtfEXMFEU0mFg84Ri6hx%2Fuploads%2Fgit-blob-afe12719b3589d67db8e6eb157194e54a119d9a8%2Facademy-enrol-from-booking.png?alt=media)

## 6. What happens next

* The student shows in **Academy › Students** and in their group's sessions in the **Calendar**.
* The family gets an email to accept the Academy terms and complete any missing details. Until then their name shows **Terms not accepted**.
* On the 1st of each month their fee is generated and, if they have no saved card, they get a payment link. See [Payments](/guia/en/crm-erp/pagos.md#monthly-academy-fees).

![Step 6: the student in the Academy list](https://310662894-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUtfEXMFEU0mFg84Ri6hx%2Fuploads%2Fgit-blob-8597f4a423237416445e798a603a82d1c2cf0b2b%2Facademy-students.png?alt=media)

## 7. The first payment

If the family pays in the office right away, open the student in **Academy** and click **Record payment**. Otherwise click **Validate place** to validate the place: the student shows **Validated · unpaid** until they pay.

![Step 7: the student's panel, with Record payment and Validate place](https://310662894-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUtfEXMFEU0mFg84Ri6hx%2Fuploads%2Fgit-blob-cc4845199f33bb379a12689c1a9afce2979c24c7%2Facademy-student.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/step-by-step/contacto-a-academia.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.