> ## Documentation Index
> Fetch the complete documentation index at: https://docs.open.cx/llms.txt
> Use this file to discover all available pages before exploring further.

# SLA Analytics

> SLA analytics provide visibility into your organization's SLA compliance, response and resolution times, and breach patterns.

SLA analytics provide visibility into your organization's SLA compliance, response and resolution times, and breach patterns. Use this data to monitor service level performance and identify areas for improvement.

## What are SLAs?

Service Level Agreements (SLAs) define the expected response and resolution times for customer support interactions. The SLA analytics API lets you track:

* **Compliance rates** — How often your team meets SLA targets for first response and resolution
* **Coverage** — What percentage of sessions are covered by an SLA policy
* **Percentiles** — Response and resolution time distributions (p50, p90, p95)
* **Trends** — How compliance changes over time
* **Breach patterns** — When SLA breaches are most likely to occur

## Phone answer time

The phone endpoints grade every wait for an agent against the phone answer-time target of the policy that applies: the team's phone SLA policy, else the workspace default. A wait runs from when the caller starts waiting for an agent to when an agent accepts, counting office hours only. Outcomes are `answered`, `caller_hung_up`, `timed_out`, `no_agents`, and `voicemail`. Rates are fractions from 0 to 1. Agents are judged only on their own rings. See [Phone answer-time SLA](https://docs.open.cx/phone/answer-time-sla.md) for the measurement rules and the policy fields.

## Available Endpoints

> [card] [Overview](https://docs.open.cx/api-reference/sla-analytics/overview.md)
>
> Get SLA compliance rates, coverage, and response/resolution time percentiles

> [card] [Breakdown](https://docs.open.cx/api-reference/sla-analytics/breakdown.md)
>
> Get SLA compliance grouped by policy, team, agent, or channel

> [card] [Trend](https://docs.open.cx/api-reference/sla-analytics/trend.md)
>
> Get SLA compliance rates over time, grouped by day or week

> [card] [Breach Heatmap](https://docs.open.cx/api-reference/sla-analytics/breach-heatmap.md)
>
> Get a heatmap of SLA breaches by hour of day and day of week

> [card] [Phone answer time](https://docs.open.cx/api-reference/sla-analytics/phone-overview.md)
>
> Get answer-time compliance, outcomes, abandon rate, and answer-time percentiles for callers waiting for an agent

> [card] [Phone answer time breakdown](https://docs.open.cx/api-reference/sla-analytics/phone-breakdown.md)
>
> Get phone answer-time compliance grouped by team, policy, day, or hour of day

> [card] [Phone answer time by agent](https://docs.open.cx/api-reference/sla-analytics/phone-agents.md)
>
> Get each agent's rings offered, answered, declined, missed, answer rate, and time to answer

> [card] [Phone handle time](https://docs.open.cx/api-reference/sla-analytics/phone-handle-time.md)
>
> Get average handle time with talk, hold and after-call work, and handles over their target

> [card] [Phone handle time breakdown](https://docs.open.cx/api-reference/sla-analytics/phone-handle-time-breakdown.md)
>
> Get average handle time grouped by team, agent, day, week, or month

> [card] [List phone call handles](https://docs.open.cx/api-reference/sla-analytics/phone-handles.md)
>
> List each time an agent handled a call, with talk, hold and after-call work in seconds

## Historical reports and freshness

All four endpoints support historical date ranges without a fixed maximum span. Recent changes may take a short time to appear. Session counts and duration percentiles use session creation dates; compliance events and breach heatmaps use the time each event occurred. Internal sessions are excluded.

Reports return complete results or an explicit error. A failed report does not mean there were no sessions or breaches. If a request is too large (`400`), add policy, team, channel, or agent filters; for trends, weekly granularity reduces the number of points. If reporting is busy (`429`) or temporarily unavailable (`503`), retry with backoff. Avoid launching many reports simultaneously.

Daily and weekly trend buckets follow the requested timezone. Each request still requires the `sla-analytics:read` scope and only returns data for the authenticated organization.

Agent breakdowns retain names for historical assignees after they leave your organization, including sessions assigned to the AI agent. Unassigned groups represent sessions without an available assignee name.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.