Settings
Eight sub-tabs covering everything about the agent that isn't its knowledge or its conversations.
General
The agent's name and ID, its real storage size, and a credits limit — a monthly OpenAI token cap covering chat, tool-calling, and AI drafts combined, with a usage bar that turns red once you hit it. The danger zone here is real and irreversible: deleting all conversations wipes conversation history only (sources, actions, and settings are untouched), while deleting the agent removes everything — sources, conversations, actions, tickets, settings — and requires typing the agent's exact name to confirm.
The inbound webhook URL your email provider's parse hook should point at, plus a working curl example of the exact request shape it expects. This is the plumbing behind the Email channel — see Channels for the user-facing side.
Helpdesk
Turns inbound emails (and other channels' escalations) into real support tickets, and can trigger AI draft replies your team reviews before sending rather than the agent replying to a ticket unsupervised. This is also what the Actions tab's Escalate action creates tickets into.
Security
A rate limit — N messages per M seconds, per device — applied to the widget and chat bubble only (not the Playground, so you can test freely), with a configurable message shown once a visitor hits it. Below that, Allowed domains restricts which sites can embed the chat bubble at all: leave it empty to allow any domain, or list specific ones — this is enforced on the real embed script itself, so copying the snippet onto an unlisted domain genuinely refuses to load rather than just being a cosmetic setting.
Custom domains
Serve the widget from your own domain (chat.yourcompany.com) instead of this app's. Ownership is verified for real, via an actual DNS TXT record lookup against the record name and token shown per domain — there's no way to skip verification. Verifying proves you own the domain; to have your chat served on it, contact [email protected] once it's verified.
Webhooks
Real, HMAC-signed HTTP POSTs fired on real events you pick per webhook. The signing secret is shown exactly once, right after creation — copy it then, since it isn't shown again in full afterward. Each webhook shows its recent delivery history as a strip of success/failure dots, and has a Send test button that fires a real request immediately so you can confirm your endpoint is wired up correctly. This is also the honest way to connect Zapier or Make today: paste the URL from Zapier's "Webhooks by Zapier" → Catch Hook trigger (or Make's Custom Webhook module) as the endpoint.
Notifications
A Slack Incoming Webhook URL that gets a real notification whenever a new Helpdesk ticket comes in. Toggle it on/off independently of whether a URL is saved, and use Send test to confirm the webhook actually posts before relying on it. This is the same webhook the Actions tab's Slack template posts through, so configuring it here wires up both notification and action use at once.
Custom fields
Reusable field definitions (key, label, description, type) shared across every action that needs the same kind of input — an order number, a subject line — instead of redefining the same parameter shape on each one. Built-in fields like Subject and Description are shown read-only alongside the ones you create, since those are used internally by the ticketing flow regardless.