> For the complete documentation index, see [llms.txt](https://doc.appflow.ai/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.appflow.ai/docs/metrics-and-events/users-statuses.md).
# Users' statuses
Appflow\.ai user's statuses info and description
***
In Appflow\.ai we care about the clarity of each feature. We have your users' CRM and we created statuses to let you know what each user is doing right now or his latest action
| User Status | Descriptions |
| ----------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
| New | User just installed your app and didn't do any purchases yet (during the last 30 days) |
| Not active | User didn't open your app for the last 30 days |
| Trial | User is on a trial period |
| Subscribed | User has an active subscription |
| Refund | User made a refund of the subscription (his last action) |
| Cancel | User has cancelled the subscription (his last action) |
| Renewal-off | User is still on a subscription but he switched the renewal of this subscription off, so he won't be charged for the next billing period. |
---
# 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://doc.appflow.ai/docs/metrics-and-events/users-statuses.md?ask=&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.
