FruxonDocs
Agent NetworkGraph

Replaces the Network's escalation operator ladder.

Full replace. Every operator must be an active operator of the Network (enroll them via the operators directory first); an unknown or non-operator participant yields `400 Bad Request` — a customer can never be an operator. An empty ladder clears the pool (members keep the conversation and degrade gracefully when they escalate). Applies immediately.

PUT
/v1/tenants/{tenant}/networks/{network}/escalationPolicy
AuthorizationBearer <token>

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

In: header

Path Parameters

network*string

The owning Network id.

Formatuuid
tenant*string

The tenant identifier

The escalation ladder to set.

tiers?

The ordered escalation ladder. Every operator must be an active operator of the network.

defaultReason?string|null

Optional fallback reason used when a member escalates without giving one.

mode?string

How a chosen operator receives the conversation: Fruxon.Model.ConversationBridges.DeliveryMode.Bridge (Fruxon relays; operator can be on any channel) or Fruxon.Model.ConversationBridges.DeliveryMode.NativeHandoff (page the operator and step back; the source console owns the live conversation). Omitted → Fruxon.Model.ConversationBridges.DeliveryMode.Bridge, the long-standing behaviour.

Value in"UNSPECIFIED" | "BRIDGE" | "NATIVE_HANDOFF"
consoleMuteTrigger?string

Console-routed only: when the agent steps back once the conversation is queued to the console — Fruxon.Model.AgentNetwork.ConsoleMuteTrigger.OnQueued (immediately; default) or Fruxon.Model.AgentNetwork.ConsoleMuteTrigger.OnAssigned (keep helping until a human takes the chat). Omitted → Fruxon.Model.AgentNetwork.ConsoleMuteTrigger.OnQueued. No effect under Fruxon.Model.ConversationBridges.DeliveryMode.Bridge.

Value in"UNSPECIFIED" | "ON_QUEUED" | "ON_ASSIGNED"
checkBackEnabled?boolean

Whether post-hand-back verification and its auto-close backstop are enabled.

stalledTakeoverUnmuteEnabled?boolean

Whether a console takeover a person has left unanswered past the watchdog's threshold is handed back to the assistant, replaying the customer's withheld messages into its next turn (design §11.9). Omitted → false, which is the fail-safe direction: an unset field silences the reclaim rather than enabling it. The alerting half is deliberately not settable here — it defaults on, and a plain bool would let any save that omits the field switch it off.

[key: string]?never

Response Body

curl -X PUT "https://api.fruxon.com/v1/tenants/string/networks/497f6eca-6276-4993-bfeb-53cbbbba6f08/escalationPolicy" \  -H "Content-Type: application/json" \  -d '{}'
{
  "networkId": "00000000-0000-0000-0000-000000000000",
  "tiers": [
    {
      "operatorParticipantIds": [
        "00000000-0000-0000-0000-000000000000"
      ],
      "strategy": "FIRST_AVAILABLE"
    }
  ],
  "defaultReason": "string",
  "mode": "BRIDGE",
  "consoleMuteTrigger": "ON_QUEUED",
  "checkBackEnabled": false,
  "stalledTakeoverUnmuteEnabled": false,
  "doorways": [
    {
      "provider": "string",
      "supportsNativeHandoff": 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
}