For all sales, the typical high-level custom journey is as follows:
1. ### Discover/Entice
1. Users find out about a token sale but don't know the exact terms.
2. Users must pass KYC/Proof of address at this point to progress
2. ### Decide
1. Users access deal terms and specific details about a particular token sale
2. They can set a reminder if the sale has not yet started
3. ### Participate
1. The user applies and deposits their desired amount (typically USDC)
2. Depending on the sale, they may need to wait to have their desired allocation accepted
4. ### Monitor
1. They are notified about the outcome of the sale and can continue to check the sale details even after being accepted
2. We typically connect all the new investors at this point so they can start to form community.
5. ### Claim
1. When the vesting period ends or TGE starts, each purchaser can begin to claim their tokens (either partially or fully)
6. ### Trade
1. The users can then trade their newly purchased tokens
---
# Agent Instructions: 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:
```
GET https://legion-1.gitbook.io/legion/general/high-level-sale-customer-journey.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.