Skip to content

Example: helpdesk tickets ​

Goal: prepare an internal comment for an operator when a new ticket arrives. The agent reads context, proposes a solution and drafts a customer reply.

The helpdesk is hypothetical. Paths such as /tickets/{id}/comments, fields body and internal, and Idempotency-Key support form an example contract. Replace them with your product's API.

DecisionAgent publishes directlyHook publishes
Publication tokenAvailable to the agentSupplied to after_run
Agent outputAPI commentMarkdown file
Delivery defined inInstructions and toolPublication code
Useful whenThe agent needs varied helpdesk actionsFormat and delivery timing are fixed

In both cases, a thin connector receives the event, gathers context and creates a session. It does not need to forward the final answer if the agent or hook already published it.

Choose direct API publication or Markdown with after_run. For a new customer message, you can create a new session with the current ticket context. To keep the conversation in one session, set allow_multiple_runs: true at creation and continue it with new context.

Add customer-facing messages or status changes as explicit process rules. This example prepares output for the operator.