# Key Features * **Detect trends** on any table with associated conditions, timeframes, thresholds, and cool-down periods. * **AI Intelligence** analyzes trends, offering immediate information on commonalities, root causes, and potential solutions - saving hours of valuable technician time. * **Retain records** of all correlations for analysis and reporting. * **React to trends** by**:** * Generating records on any table using templates or script o * Generating an event * Running a server script * **Trend thresholds** can be static numbers or based upon statistical analysis: o * Above/below average * Highest/lowest ever * Custom * **Use schedules** to only react to trends when they matter * **Intelligently add new matching records** to an existing trend correlation #### Example uses include: * If the Incident quantity for a particular CI is above a 30-day running average, automatically generate a Problem record. Let AI intelligence assess related incidents to provide commonalities, root cause, and potential solutions. * If 10 searches are performed within a day on a specific search term, automatically generate a draft KB article to address the apparent need. Use AI to create potential KB article content. * If high-volume ordering of a particular Service Catalog item is noticed, automatically process a purchase order to procure more of that item. * If less-than-expected records are being created by an integration, automatically send an alert notification to the owner of that integration. --- # Agent Instructions: 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: ``` GET https://docs.yansalabs.com/trendseeker/overview/key-features.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.