> ## Documentation Index
> Fetch the complete documentation index at: https://docs.agnost.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Intents

> See what users are trying to accomplish and inspect the evidence behind each intent

An **intent** describes what the user was trying to accomplish. Agnost AI analyzes
conversation evidence against the intents configured for the workspace and
aggregates the matches over time.

## Work with intents

Open **Intents** in the Agnost AI sidebar to:

* Review intent volume and activity.
* Search and inspect configured intents.
* Open the conversations that support an intent.
* Create, edit, or remove workspace-specific intent definitions.
* Generate suggested intents from the product description and observed traffic.

## Interpret the result

An intent count is a classified match, not proof that the user succeeded. Review
the supporting conversation and pair intent data with violations, outcomes, and
tool activity before prioritizing work.

Use names that describe the user goal, such as “reset a password” or “compare
plans,” rather than internal feature or route names.

## Next steps

* [Conversations](/using-conversations): inspect the evidence behind an intent.
* [Alerts](/using-alerts): monitor important changes in intent volume.
* [Improvements](/using-improvements): turn recurring user needs into product changes.