> For the complete documentation index, see [llms.txt](https://help.tellius.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tellius.com/tellius-6.2/getting-started/tellius-best-practices/insights-discover.md).

# Insights (Discover)

Insights serve as a vital tool to decode the narratives hidden within your data, helping you make informed, data-driven decisions.

* Understand the granularity of the data as it determines the insights that you will get as a result. Ensure that the data is properly aggregated to understand the key characteristics of certain types of invoices or transactions.
* Utilize the Insights generation feature from **Search** or **Vizpads** that help explore the “why” from ad-hoc questions. Selecting anomalies provides the “**Understand Why**” option, which is a one-click trend insight that uses all features.
* Configuring Insights from the **Discover** tab allows for a more “hypothesis” driven approach to answering questions.
* To accelerate the Insights generation, it is recommended to exclude unnecessary or irrelevant columns (e.g., columns named "user ID", "product number") during the creation of Insights.
* Use the **Edit** option for pre-existing Insights. This allows quick iteration through Insights by including or excluding more columns, changing time periods, or filters from the original Insight rather than reconfiguring from scratch each time.
* Save/move **Insights** to **Projects**, which is an effective way to organize content that can easily be shared with users or user groups.


---

# 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://help.tellius.com/tellius-6.2/getting-started/tellius-best-practices/insights-discover.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.