AgentBehaviorDto
August 7, 2026 · View on GitHub
Fields
| Field | Type | Required | Description |
|---|---|---|---|
acknowledgeOnReceived | Optional<Boolean> | :heavy_minus_sign: | Acknowledge incoming messages. On platforms that support a native typing indicator (e.g. Slack, WhatsApp, Microsoft Teams, Telegram), shows a "Typing…" indicator while the agent processes the message. On platforms that do not (e.g. Email), reacts with an "eyes" emoji to the first inbound message in a thread. Default: true |
reactionOnResolved | JsonNullable<ReactionOnResolved> | :heavy_minus_sign: | Cross-platform emoji name for resolved conversations (e.g. "check", "star"). Set to null to disable. Default: "check" |
subscriberAccess | Optional<SubscriberAccess> | :heavy_minus_sign: | Controls whether the agent accepts inbound messages from senders not yet linked to a subscriber, across all channels. "open" on managed agents auto-creates a lightweight subscriber so the agent can reply; on custom-code / self-hosted agents, the turn is forwarded to the bridge with a null subscriber. "restricted" rejects unknown senders with a managed denial reply (any runtime). Optional on update (partial PATCH). Persisted agents always have a value — managed create defaults to "open"; self-hosted create defaults to "restricted". |