---
name: zendesk-sla-breaches
description: "Every business hour: Zendesk tickets that breached or will soon breach an SLA target, plus escalated tickets, and who takes each one. Use when the user asks for this, or when it runs on a schedule."
---

# Zendesk SLA breaches and escalations

Every business hour: Zendesk tickets that breached or will soon breach an SLA target, plus escalated tickets, and who takes each one.

Zendesk shows an SLA badge on each ticket, but a view sorted by next breach only helps if someone is looking at it at the right moment. Support leads find out about a breach in the weekly report, after the customer has already noticed.

Every hour during the working day the agent lists the tickets whose SLA target has passed or will pass within the hour, adds the escalated tickets, and asks who takes the unassigned ones. When everything is on time, the card says so and stays quiet.

## Two ways to get the data

Use the API or MCP route when you have an MCP server, a CLI or an API token for the app. Otherwise, if you can drive a browser the user is signed in to (Claude in Chrome, a Playwright or Chrome DevTools MCP server), use the browser route. Say which one you used.

## Route A: API or MCP server

### What you need

- A Zendesk agent account with an API token (`ZENDESK_EMAIL`, `ZENDESK_API_TOKEN` and your subdomain), or a Zendesk MCP server or connector with ticket read and update access.
- SLA policies set up in Zendesk, and how your team marks an escalation (tag, group or priority).

If something is missing, say what and stop; do not invent numbers.

### Steps

1. **Search open tickets with their SLAs** (Zendesk): Call `GET /api/v2/search.json?query=type:ticket status<solved&include=tickets(slas)`, following `next_page`. Each ticket's `slas.policy_metrics` lists its targets with `metric` (such as `first_reply_time` or `next_reply_time`), `stage` and `breach_at`.
2. **Sort breached from at risk**: A target with `stage` `active` and `breach_at` in the past is breached; one with `breach_at` within the next 60 minutes is at risk. Paused and achieved targets are left out. Sort by `breach_at`, oldest first.
3. **Add the escalations** (Zendesk): Run a second search, `type:ticket status<solved tags:escalated` (or the group, tag or `priority:urgent` your team uses), and keep the ones not already on the list, with how long each has waited.
4. **Ask, then assign** (Zendesk): Post the list as an ask when anything is breached, at risk or escalated without an owner. On an answer, set `assignee_id` with `PUT /api/v2/tickets/{id}` (or `update_many` for several). When nothing is at risk, post an all-clear instead.

## Route B: the browser

### What you need

- Signed in to Zendesk Support as an agent who can see the SLA views and change the assignee on tickets in those groups; the Next SLA breach column only appears on accounts with SLA policies.

If something is missing, say what and stop; do not invent numbers.

### Steps

Start at https://www.zendesk.com/login/. The user is signed in already; never type passwords or codes, and ask if a sign-in page appears.

1. **Open your agent workspace**: Enter your subdomain on the login page; sign-in is already done, so it opens `https://<subdomain>.zendesk.com/agent/`. Click **Views** in the left sidebar.
2. **Sort unsolved tickets by SLA**: Open a view of unsolved tickets (the default **All unsolved tickets**, or one your team uses) and click the **Next SLA breach** column header to sort by it. If the column is missing, an admin adds it under the view's **Formatting options**.
3. **Read breached and at-risk tickets**: Tickets whose SLA badge is red have breached; read the ticket number, subject, which target it is (first reply, next reply, or another) and how long ago. Then read the ones whose next breach is within 60 minutes, with the time left and the assignee.
4. **Add the escalations**: In the search box at the top, run `type:ticket status<solved tags:escalated` (or your team's group or `priority:urgent`), and note the escalated tickets not already on the list with how long each has waited.
5. **Assign only after an answer**: Report the list and ask who takes the unassigned tickets. After the answer, open each ticket, set **Assignee** in the left panel and click **Submit**. If nothing is breached, at risk or escalated without an owner, report an all-clear.

Note: Views show at most 30 tickets per page and the SLA badge rounds to minutes, so check the ticket itself when a breach is close. Paused targets (for example on pending tickets) show no badge and are left out, the same as in the API route.

## The report

- **Breached** tickets, with the SLA target and how long ago it passed.
- **At risk**: tickets that breach within the hour.
- **Escalated** tickets and how long they have waited.
- The ask: who takes the unassigned ones, or an all-clear when there are none.

## Post it to Briefkin

When `BRIEFKIN_TOKEN` is set, or `~/.config/briefkin/env` exists (the installer from https://briefkin.dev/docs writes it), also send the result to the user's Briefkin board as one card. Keep the `item_key` the same on every run so the card updates in place, use a new `event_id` per run, and put today's real numbers in place of the example ones. If the request fails, say so once and carry on.

```bash
[ -n "${BRIEFKIN_TOKEN:-}" ] || . ~/.config/briefkin/env
curl -sS -X POST "${BRIEFKIN_URL:-https://briefkin.dev}/v1/events" \
  -H "authorization: Bearer $BRIEFKIN_TOKEN" \
  -H "content-type: application/json" \
  -d @- <<'JSON'
{
  "v": 1,
  "event_id": "zendesk-sla-breaches/<date of this run, e.g. 2026-10-16>",
  "item_key": "zendesk-sla-breaches",
  "project": "Acme Support",
  "source": "Zendesk SLA breaches and escalations skill",
  "kind": "action",
  "title": "3 tickets breached SLA, 5 more within the hour",
  "summary": "**3 tickets** have breached their SLA and **5** will within 60 minutes. **2 escalated** tickets are also waiting, one of them unassigned.",
  "action": {
    "request": "Who takes the 4 unassigned tickets?",
    "options": [
      "Assign to the on-call agent",
      "Split across Tier 2",
      "I will take them",
      "Leave as is"
    ]
  },
  "widget": [
    {
      "type": "Table",
      "props": {
        "columns": [
          "Ticket",
          "Subject",
          "Target",
          "Breach",
          "Assignee"
        ],
        "align": [
          "left",
          "left",
          "left",
          "left",
          "left"
        ],
        "rows": [
          [
            "#48213",
            "Cannot export invoices",
            "First reply",
            "42 min ago",
            "Unassigned"
          ],
          [
            "#48198",
            "SSO login loop",
            "Next reply",
            "18 min ago",
            "Ana"
          ],
          [
            "#48230",
            "Charged twice",
            "First reply",
            "5 min ago",
            "Unassigned"
          ],
          [
            "#48241",
            "API returns 500 errors",
            "First reply",
            "In 12 min",
            "Unassigned"
          ],
          [
            "#48176",
            "Data import stuck",
            "Next reply",
            "In 25 min",
            "Ben"
          ],
          [
            "#48244",
            "Change billing email",
            "First reply",
            "In 31 min",
            "Ben"
          ],
          [
            "#48239",
            "Webhook not firing",
            "Next reply",
            "In 44 min",
            "Ana"
          ],
          [
            "#48250",
            "Add seats to plan",
            "First reply",
            "In 55 min",
            "Chris"
          ],
          [
            "#48102",
            "Outage credit request",
            "Escalated",
            "Waiting 3 h",
            "Unassigned"
          ],
          [
            "#48155",
            "Contract terms question",
            "Escalated",
            "Waiting 1 h",
            "Dana"
          ]
        ]
      }
    }
  ]
}
JSON
```

Widgets come from the Briefkin catalog (https://briefkin.dev/v1/catalog). Without a token, just give the user the report.

## Run it on a schedule

Suggested: Weekdays, hourly 9:00 to 18:00 (`0 9-18 * * 1-5`). From cron, with the agent signed in on that machine:

```bash
0 9-18 * * 1-5 claude -p "Run the zendesk-sla-breaches skill"
# Codex: codex exec, Gemini CLI: gemini -p, Copilot CLI: copilot -p, OpenCode: opencode run
```

Or use the agent's own scheduler (Claude Code routines, Codex automations, Claude or ChatGPT scheduled tasks): https://briefkin.dev/skills/zendesk-sla-breaches#schedule

Source: https://briefkin.dev/skills/zendesk-sla-breaches
