Response Channel
The Response Channel is an optional per-tool toggle that surfaces a human operator’s reply back to the end user, for tools where firing an action (an email to support, a webhook to a ticketing system) is only the first half of the conversation.
Enabling it
On the tool’s editor screen, turn on Enable operator response channel for this tool. When on, every successful firing of the tool creates a queue entry on the dashboard’s pending-response list. Once an operator types a reply there, the next time the user starts a chat their greeting mentions it, and they can also look it up reactively by their reference code (the tool’s Tracking ID).
Enabling the response channel auto-seeds two built-in tools into the project:
| Built-in tool | What it’s for |
|---|---|
Complaint/Request Status Lookup (qafka_response_status) | When a user mentions a tracking/reference code, the AI fires this to surface the operator’s latest reply. |
Append User Follow-Up (qafka_add_followup) | When a user wants to add information to a previously filed request, the AI fires this; the note becomes visible to the operator. |
These two tools appear locked in the tool list — their URL, parameters, and mode aren’t editable, since they’re managed automatically as part of the response-channel infrastructure. You can see their AI-facing description in read-only form, but not change it.
The operator side
Operators reply to these threads from the Action Logs page — each thread shows as Awaiting reply / Replied / Closed, with an Append Reply action, a Close Thread action, and a “seen by user” indicator once the user has read the reply. See the Action Logs page for the full operator workflow.