> For the complete documentation index, see [llms.txt](https://humanic.gitbook.io/humanic/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://humanic.gitbook.io/humanic/what-are-agents/who-to-send.md).

# Who to send?

The Segmentation expert agent works on top of your product usage data to automatically categorize users in a hierarchy - Stages and Milestones

**Stage:** Stage is the top level of the hierarchy represents broad categories, often based on factors like pricing plans, geogrpahic regions or a combination. Ideally, each of these high level groupings should contain users with similar journerys. 

**Milestone:** Milestone represent intermediate steps in a user's successful journey. Think of product milestones as onboarding steps. 

**Cohorts:** The agent generates 2 to 3 user cohorts for each milestone. 

The overall directive given to the segmentation system is to generate user cohorts that are valuable from a marketing standpoint. It aims to capture approximately 80% of the users within each Stage, Milestone.

<figure><img src="/files/9oqBqIoMS8MTtpW9UZKT" alt=""><figcaption></figcaption></figure>


---

# 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://humanic.gitbook.io/humanic/what-are-agents/who-to-send.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.