> For the complete documentation index, see [llms.txt](https://docs.spectralink.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spectralink.net/amie-advanced/charts-reference/trend-sparklines.md). # Trend sparklines The small trend lines on the Dashboard's call tiles, showing how a figure has moved over the past week. ## What it shows One line per tile, plotting a single value across the **seven complete days before today**. Today is never plotted. Three tiles use this chart: **Call Performance**, **Call Volume**, and **Call Minutes**. Each plots its own value; **Call Performance** is drawn in percent. The chart has no gridlines and no vertical axis. Instead: * The number **above** the line is the top of its scale: the week's highest value rounded up to a whole number. * The number **below and to the left** is the bottom of the scale: the lowest value rounded down. * Along the bottom, each point is labeled with an abbreviated weekday name, in your own language and region. Because both are rounded outwards, neither is necessarily a value that actually occurred. ## How to read it {% hint style="info" %} Screenshot needed: the three Dashboard call tiles, on a fleet with a week of varied call activity, highlighting the scale figures above and below the line and the weekday labels {% endhint %} **The line does not start at zero.** It is scaled to fit its own highest and lowest values, so the full height of the chart always represents the range covered that week, however small. A line that climbs steeply may be showing a change of one or two units. Always read the high and low figures before judging the shape. Where a value has not changed at all across the week, the line is flat. It sits at the bottom of the chart when the value is a whole number, and partway up when it is not — its height in that case carries no meaning. ## Interactions None. The line cannot be hovered for values, clicked through, zoomed, or exported. The only figures available are the high, the low, and the weekday labels. ## What it doesn't show * **Today.** The line ends at yesterday, while the large figure above it covers a more recent period, so the two do not line up. See [Call Performance](/amie-advanced/metrics-reference/call-performance.md) for exactly which period each covers. * **Most individual values.** Only the two scale figures are labeled, plus yesterday's own value, which the tile shows separately as **Yest.**. The other six days can only be read from the shape. * **Whether a zero means anything.** A point at zero may be a genuine zero or an absence of data; the chart draws them identically. * **Where the days begin.** Days are cut at your own local midnight, so the same calls can fall on different days for colleagues in other time zones. ## Where you'll see it * [Dashboard](/amie-advanced/using-the-platform/dashboard.md) — on the **Call Performance**, **Call Volume**, and **Call Minutes** tiles ## Related * [Call Performance](/amie-advanced/metrics-reference/call-performance.md) --- # 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://docs.spectralink.net/amie-advanced/charts-reference/trend-sparklines.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.