Talk

Choose Talk when the agent needs to adapt over several turns, such as answering questions, understanding an issue, or qualifying a caller. It stays active until an exit condition is met and can collect values along the way. Choose Collect for the more focused task of gathering a defined set of fields.

​

Start the block

Configure the block directly, or expand the Generate with AI strip at the top of the panel, describe what you want, and start a focused Ask AI task for this block alone. For example:

Answer the caller’s questions using the knowledge base. If an answer is unavailable, offer to collect their contact details for follow-up.

In Review mode, inspect the proposal on the canvas and apply it. In Auto apply mode, the requested edit is written directly to the draft. Check the result and test the affected path before publishing; see Choose how flow changes are applied. The instruction is not saved onto the block, so the box starts empty each time and the request lives in the Ask AI conversation. Generation is offered only on an editable draft, not in version previews, comparisons, or to viewers. Type @ in the instruction to add a workflow variable. The selected variable appears as a chip and passes to Ask AI as a variable reference rather than plain text.

​

Configure the conversation

​

Prompt

The Prompt tells the agent how to handle the conversation while Talk is active. Write directions rather than a script. Include the objective, relevant context or boundaries, and what the agent should do when it cannot complete the task. Type @ and select an available variable or knowledge base source when the prompt needs that information. Adding its name as plain text does not insert the source.

​

Exit Conditions

Each Exit Condition describes a conversational result that ends the Talk block and creates a source handle. Match the condition to its numbered port along the bottom of the block and connect that port to the block that should run next. Write conditions as completed, observable outcomes. For example:

• The caller's question has been answered and they have no more questions
• The caller wants to leave their contact details
• The caller asks to speak with a person

A Talk block requires at least one exit condition and supports up to ten. Conditions must be non-empty and unique. Each exit lists the variables it must capture before the call can leave through it, shown as chips on the condition and on the exit rows on the canvas. See Require variables per exit. When several conditions lead to the same block, combine them into one outcome-focused condition for clearer routing. Exits leading to the same block are suggested for combining only when their variable requirements also match.

​

Variables

Add a variable when the Talk block should extract information from the conversation for later blocks. Each variable’s card can require it on every exit at once. Requiring whether a value must be captured, confirmed, or spelled back is set per exit condition, not on the variable itself. See Require variables per exit. Collected values appear in Available Variables for later blocks on that route. See Variables for types, availability, and troubleshooting.

​

Require variables per exit

A Talk variable is required per exit condition, so one route can demand a value while another does not. For example, an exit such as “the caller refuses to give their name” does not have to wait for the name, while the normal completion exit does. On each exit condition, add the variables it needs as chips and choose how far to take each one: To apply the same requirement everywhere, open the variable’s card and require it on all exits at once; its chips still live on each exit, so you can adjust an individual exit afterward. Existing blocks keep their earlier behavior: each previously Required variable becomes a requirement on every exit.

​

Example: Answer business questions

• Prompt: Use the knowledge base to answer questions about the business. Keep answers concise. If the answer is unavailable, explain that a team member can follow up and offer to collect the caller’s details.
• Exit conditions:
  • The caller’s questions have been answered and they have no more questions
  • The caller wants to leave their information for follow-up
• Variable: unanswered_question — the caller’s unanswered question

Connect the answered route to End Call and the follow-up route to Collect. This keeps the completed and follow-up paths explicit on the canvas.

​

Test Talk

Test the expected outcome and each meaningful alternative. Confirm that Talk:

• remains active while its conversational objective is incomplete;
• handles different phrasing for the same intent consistently;
• selects the intended exit condition and route for each outcome; and
• stores and confirms variables as configured.

Use Web Call when voice behavior matters, such as pacing and interruptions. For an unexpected result, open Call Details, select Blocks, and expand Talk to review its conversation turns, selected route, and stored variables.

​

Troubleshooting