FruxonDocs
ApiAgent escalation policy

Replaces the agent's escalation operator ladder.

Full replace. Operators must be existing participants of kind person/group; an unknown or AI-agent operator yields `400 Bad Request`. An empty ladder clears the policy (the agent keeps the conversation and degrades gracefully when it escalates).

PUT
/v1/tenants/{tenant}/agents/{agent}/escalationPolicy
AuthorizationBearer <token>

JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.

In: header

Path Parameters

agent*string

The agent identifier.

tenant*string

The tenant identifier

The escalation ladder to set.

tiers?|null

The ordered escalation ladder; null/empty clears the policy (no operator configured).

defaultReason?string|null

Optional fallback reason used when the agent escalates without giving one.

checkBackEnabled?boolean

Opt-in to the post-hand-back agent check-back (§11.8). Off by default; when on, a released-but-unresolved takeover gets one proactive verification turn and an auto-close backstop if the customer stays silent.

[key: string]?never

Response Body

curl -X PUT "https://api.fruxon.com/v1/tenants/string/agents/string/escalationPolicy" \  -H "Content-Type: application/json" \  -d '{}'
{
  "agentId": "string",
  "tiers": [
    {
      "operatorParticipantIds": [
        "00000000-0000-0000-0000-000000000000"
      ],
      "strategy": "FIRST_AVAILABLE"
    }
  ],
  "defaultReason": "string",
  "checkBackEnabled": false,
  "createdAt": 0,
  "modifiedAt": 0
}
{
  "type": "string",
  "title": "string",
  "status": 0,
  "detail": "string",
  "instance": "string",
  "property1": null,
  "property2": null
}
Empty
Empty
{
  "type": "string",
  "title": "string",
  "status": 0,
  "detail": "string",
  "instance": "string",
  "property1": null,
  "property2": null
}