> 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/metrics-reference/call-performance.md).

# Call Performance

A single score out of 100 summarizing the voice quality of calls made on your devices.

## How it's calculated

Each call is scored for quality as it happens, using the standard Mean Opinion Score (MOS) scale. **Call Performance** averages those scores across all calls in the period, then converts the average to a figure out of 100, displayed with a percent sign.

A higher number is better. The scale reaches 100 a little below the theoretical maximum of the MOS scale, so excellent call quality reads as 100 rather than something short of it.

## What's included and excluded

* **Included:** every call recorded against the batteries and devices in your selection that ended within the period. Calls are matched to your selection differently from device figures, so a group selection can narrow the two by different amounts.
* **Excluded:** calls with no recorded end time.

## Time window and timezone

The figure appears in two forms, covering **different periods**:

| Where                        | Period                                                                           |
| ---------------------------- | -------------------------------------------------------------------------------- |
| The large figure on the tile | The last 24 hours counted back from now, so it spans today and part of yesterday |
| The **Yest.** figure         | Yesterday                                                                        |
| The trend line               | The seven complete days before today. Today is not shown                         |

{% hint style="warning" %}
The large figure is not the right-hand end of the trend line beneath it. The line stops at yesterday; the large figure includes today. The last point on the line is the **Yest.** figure.
{% endhint %}

Days on the trend line are cut at **your own local midnight**, using the clock on the computer you are viewing from. Two people in different time zones see the same calls divided across days differently.

## Data freshness

Calculated when the screen loads.

## Filters and breakdowns

The group selector in the header narrows the figure, but by a different route from the device figures on the same screen. A group whose calls are not linked through to the reporting system contributes nothing here, even when its devices are counted normally. If **Call Volume** reads zero while devices are plainly in use, that mismatch is the likely cause.

## Edge cases

* **No calls shows as 0.** When there were no calls at all in the period, the figure reads **0** — identical to the display for uniformly terrible call quality. Check **Call Volume** on the same screen to tell the two apart.
* **The change percentage is against the day before yesterday**, not against the large figure.
* **A change from zero shows as +0%.** If the comparison day had no calls, the percentage reads **+0%** in green regardless of how much the figure actually moved.
* **The trend line does not start at zero.** It scales to its own range. The figure above the line is the top of that scale and the figure below and to its left is the bottom. Both are rounded outwards, so neither is necessarily a value from the week.
* **Figures are rounded.** The score is a whole number and the change percentage carries one decimal place.
* **Calls are counted when they end.** A call spanning midnight falls on the day it ended.

## Where you'll see it

* [Dashboard](/amie-advanced/using-the-platform/dashboard.md) — as the **Call Performance** tile
* [Device details](/amie-advanced/using-the-platform/device-details.md) — per-call quality appears as **Quality (MOS)**, banded **Good**, **Fair**, and **Poor**, with a **Poor Quality** count

## Related metrics

* **Call Volume**: how many calls were made in the same period. Use it to judge whether a performance figure is based on enough calls to be meaningful.
* **Call Minutes**: total call time in the same period.
* [Call quality (MOS)](/amie-advanced/metrics-reference/call-quality-mos.md): what the underlying score means, and how it is banded per call.
* [Performance](/amie-advanced/using-the-platform/performance.md): which access points and devices are responsible when this figure drops.


---

# 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/metrics-reference/call-performance.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.