> 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/using-the-platform/device-details/device-daily-usage.md).

# Daily Usage Statistics

**Daily Usage Statistics** is the fourth of the five sections beneath a device's details. For each of the last seven days it draws a 24-hour strip — the track — with a single bar from the device's first use of the day to its last, alongside the share of the day that span covers and the number of calls that day. To reach it, open a device from the Devices [Inventory](/amie-advanced/using-the-platform/devices-inventory.md) tab and scroll down.

## Why this screen matters

**Daily Usage Statistics** answers "when is this device in service?" — the start and end of its working day, for each of the last seven days — rather than how busy it was in between. Use it to see whether a phone is being used on the shifts it was issued for, whether it sits idle on some days, and how many calls it handles a day. For what happened between first and last use, use [Session Activity](/amie-advanced/using-the-platform/device-details/device-session-activity.md).

## Before you start

The seven days are [calendar days](/amie-advanced/metrics-reference/time-and-time-zones.md) in your browser's time zone, ending with today. It shows data for the device whose page you are on; the [group selector](/amie-advanced/using-the-platform/the-console.md#the-group-selector) in the header has no effect on it.

## Screen layout

![Daily Usage Statistics: seven day rows on a 24-hour track, most recent first.](https://3032864282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxfLF6IpyutR429bMnvvf%2Fuploads%2Fgit-blob-ccc0f86c520504890d935b5c819d1139f9239c86%2Fdevice-daily-usage.png?alt=media)

### Heading

**Daily Usage Statistics** with a calendar icon and a **?**.

### The day rows

A header line marks the track with **00:00**, **06:00**, **12:00**, **18:00** and **24:00**. Below it, one row per day, most recent first — today at the top, then yesterday, and so on to six days ago.

Each row has three parts:

| Part    | What it shows                                                                                                                                                                                                                                                         |
| ------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Date    | The day as month and day — **Sep 21** — with its weekday beside it in smaller text — **Sun**                                                                                                                                                                          |
| Track   | A gray 24-hour strip with faint lines at 06:00, 12:00 and 18:00. A blue bar runs from the time of the device's first use that day to its last use. While you hover over the bar, the two times are printed at its ends. A day with no recorded use has an empty track |
| Figures | **N% utilization** — the share of the 24 hours between first and last use, rounded to a whole number — and **N calls**, the number of scored calls that began that day                                                                                                |

First use and last use come from the device's own reports of when it was in use. For each hour AMIE keeps the earliest and latest report in which the device said it was in use; the bar runs from the earliest such time in the day to the latest, shown to the minute. A day counts as having use if at least one of its hours reported any use. A bar is never drawn narrower than about seven minutes, so a single brief use still shows.

A device with no use and no calls in the week still shows seven rows, each with an empty track, **0% utilization** and **0 calls**.

## Controls

**Daily Usage Statistics** has no controls. There is no date range: the last seven days are fixed, and the rows cannot be sorted.

## Icons and indicators

| Icon or indicator                          | Meaning                                                       | When it appears            |
| ------------------------------------------ | ------------------------------------------------------------- | -------------------------- |
| Calendar icon before the heading           | Marks the section                                             | Always                     |
| **?** beside the heading                   | Hover over it for a short description of the section          | Always                     |
| Blue bar on a track                        | The span from the device's first use to its last use that day | Each day with recorded use |
| Times at the ends of the bar               | First and last use, to the minute                             | While hovering the bar     |
| Faint lines at quarter points of the track | 06:00, 12:00 and 18:00                                        | Every row                  |
| Spinning icon in place of the rows         | The data has not loaded yet                                   | While loading              |

## What to look for

* A bar that starts or ends well outside the shift the phone was issued for. Someone is using it off-shift. The **In use** row on [Session Activity](/amie-advanced/using-the-platform/device-details/device-session-activity.md) shows the same use minute by minute.
* An empty track on a working day. The phone was not used that day; if it should have been, check its **Last Seen** at the top of the page and its **Charging** row on [Session Activity](/amie-advanced/using-the-platform/device-details/device-session-activity.md).
* **50% utilization** on two phones that look very different in use. The bar shows span, not busyness: a device used once at 07:00 and once at 19:00 draws the same 12-hour bar as one used continuously all day. Read [Session Activity](/amie-advanced/using-the-platform/device-details/device-session-activity.md) for how hard it worked in between.
* **N calls** above zero with an empty track. The device made calls without reporting itself in use. Only calls AMIE has scored are counted, on the day they began.
* Today's bar shorter than the rest. It covers only the part of today that has passed.
* Rows that differ from a colleague's. Days are cut at midnight in each person's browser time zone, so the same use can fall into different days. In a week that includes a daylight-saving change, the days before the change begin and end an hour off midnight. See [Time and time zones](/amie-advanced/metrics-reference/time-and-time-zones.md).
* "Utilization" here and on the Devices [Overview](/amie-advanced/using-the-platform/devices-overview.md#in-use) tab. They are different measures: here it is the share of one device's day; there it is the share of devices used each day.

## Metrics on this screen

* [Time and time zones](/amie-advanced/metrics-reference/time-and-time-zones.md) — calendar days in your browser's time zone

## Related

* [Device details](/amie-advanced/using-the-platform/device-details.md) — the details above this section
* [Session Activity](/amie-advanced/using-the-platform/device-details/device-session-activity.md) — the **In use** row, minute by minute
* [Devices overview](/amie-advanced/using-the-platform/devices-overview.md) — the fleet-wide **In-Use** chart


---

# 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/using-the-platform/device-details/device-daily-usage.md?ask=<question>&goal=<user_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.