Why the Application's conversations escalated over an optional window (defaults to the last 30 days).
Dead-ended escalation attempts by cause (summing to the rollup's `degraded`) with each cause's latest conversation, and the window's escalations grouped by the reason the agent gave — names and identifiers redacted (`redactionHits` counts them), grouped only when identical after that; groups holding a dead-end first, then most recent first — with how each group ended and the latest one's conversation, channel and agent. The operator queue keeps the reasons as written. Repeated attempts at one escalation count once; the queue's by-design requests and notifications, and lab rehearsals, are not escalations. `from`/`to` are Unix ms (half-open); all time is `from=0`. A window holding more escalation ledger rows than one read keeps is narrowed to its newest ones, and the response's `window` starts where they do.
Authorization
Bearer JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.
In: header
Path Parameters
The Application (Network) id.
uuidThe tenant identifier
Query Parameters
Window start, Unix ms inclusive. Defaults to 30 days before to; 0 for all time.
int64Window end, Unix ms exclusive. Defaults to now.
int64Response Body
curl -X GET "https://api.fruxon.com/v1/tenants/string/networks/497f6eca-6276-4993-bfeb-53cbbbba6f08/supportKpis/escalations"{
"networkId": "00000000-0000-0000-0000-000000000000",
"window": {
"fromMs": 0,
"toMs": 0
},
"escalations": 0,
"deadEndsByCause": [
{
"cause": "NO_OPERATOR_CONFIGURED",
"count": 0,
"lastAt": 0,
"latest": {
"agentId": "string",
"topicId": null,
"participantId": null
}
}
],
"reasons": [
{
"reason": "string",
"escalations": 0,
"handedToPerson": 0,
"deadEnded": 0,
"lastAt": 0,
"latest": {
"agentId": "string",
"topicId": null,
"participantId": null
},
"channel": {
"provider": "string",
"integrationConfigId": null,
"displayName": "string"
},
"agentDisplayName": "string"
}
],
"reasonCount": 0,
"redactionHits": 0
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}Support KPI rollup for the Application over an optional window (defaults to the last 30 days).
Containment / escalation / degrade / override rates, time-to-human percentiles, live operator load, cost per resolved conversation, and the currently-awaiting-a-human gauge. Rates are null when their denominator is zero. `from`/`to` are Unix ms (half-open); `origin` filters spend only. All time is `from=0`: a window reaching back before the Application existed is counted from the day it was created.
The support KPIs bucketed over time — the trend behind the operational-detail sparklines.
One point per UTC day (or per week when bucket is `Week`). Only the additive counters are bucketed — volume, resolution, containment, escalation, degrade, cost — with rates recomputed per bucket (null when the denominator is zero). The point-in-time gauges (operator load, awaiting) and time-to-human live on the rollup endpoint. `from`/`to` are Unix ms (half-open), defaulting to the last 30 days; `origin` filters spend only.