> 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-5.6/getting-started/faqs/insights-faqs.md). # Insights FAQs Explore Insights FAQs to understand Discovery, Key Driver, Trend, and Comparison Insights, and learn how to create and interpret them. #### **What happens when a refresh is set up for an Insight?** The Insight will refresh/re-run at the scheduled time, irrespective of data refresh, and you will receive a notification. If the data remains unchanged, the resulting insight will be the same. #### **Why does comparison insight show me the number of rows?** It could be useful in some cases to assess the frequency comparison between cohorts. #### **How do you know when to use discovery insights vs. autoML?** Tellius Insights is still a descriptive output, although it uses predictive modeling on the back end. Use Insights to uncover and quantify relationships between metrics and dimensions in order to explain a particular scenario in the data. ML is used when a certain outcome needs to be predicted (example: predict if a loan is going to be charged off, predict sales for 30 days into the future) #### **Can you use a custom model for Discovery Insights?** No, Insights is a fine-tuned framework that produces four types of output at the moment: discovery, segment driver, comparison, and trend. --- # 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://help.tellius.com/tellius-5.6/getting-started/faqs/insights-faqs.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.