Skip to main content

Conversation Nodes

Conversation nodes form the step chain — the ordered sequence of actions your agent takes during a call. They connect left-to-right via control handles.

Start

The entry point of every conversation. The Framework node connects to Start, and Start connects to the first step.
ParameterTypeDescription
commandtextThe agent’s opening message
isLiteralbooleanIf true, speaks the command verbatim instead of using it as an instruction
Connections: Framework output → Start framework_in → next step in

Burst

A fixed number of back-and-forth exchanges on a topic. Use it for structured Q&A, data collection, or focused discussions.
ParameterTypeDescription
roundsstepper (1–10)Number of user/agent exchanges. Default: 1
commandtextTopic instruction for the LLM

Open Talk

Unlimited free-form conversation on a topic. Use it when you don’t know how many turns the user needs.
ParameterTypeDescription
commandtextTopic instruction for the LLM
Open Talk continues until the StepWatcher decides to advance — typically after the user signals they are done. Connect an If/Else or Categorize node after Open Talk to decide where to go next.

Timer

Conversation on a topic for a fixed duration. Advances automatically when the timer expires.
ParameterTypeDescription
durationstepper (30–1800s)Duration in seconds. Default: 30
commandtextTopic instruction for the LLM

If/Else

Binary branch based on an LLM-evaluated condition. Requires its own LLM node connected to llm_in.
ParameterTypeDescription
conditionTexttextCondition to evaluate (e.g., “Is the user interested in upgrading?”)
Outputs: true handle and false handle — connect each to a different next step. Allowed sources: Timer, Burst, Open Talk only (not Start).

Categorize

Multi-way branch by semantic classification. Requires its own LLM node connected to llm_in. Dynamically generates one output handle per category.
ParameterTypeDescription
commandtextClassification instruction
categoriescategories arrayCategory names (e.g., ["Sales", "Support", "Billing"]). Default: ["Sales", "Support"]
Outputs: One control handle per category — connect each to a different next step.

End

Terminates the conversation. The agent speaks its closing message and disconnects.
ParameterTypeDescription
commandtextClosing message
isLiteralbooleanIf true, speaks the command verbatim
Note: End nodes can also connect to Webhook nodes to fire an HTTP POST before disconnecting.

Transfer

Hands off to another agent or phone number. Connects to transfer_in on the Framework node.
ParameterTypeDescription
commandtextSpoken message before the transfer
isLiteralbooleanIf true, speaks the command verbatim

Summarize

Summarizes the conversation so far before moving to the next step. (Coming soon)
ParameterTypeDescription
styleenumbullet, paragraph, or brief
prompttextCustom summarization instruction

Typical flow patterns

Simple linear:
Start → Burst → End
With branching:
Start → Open Talk → If/Else → [true] Burst → End
                             → [false] End
With triage:
Start → Burst → Categorize → [Sales] Burst → End
                            → [Support] Open Talk → End
                            → [Billing] Transfer