Skip to main content
Build a voice experience as a connected workflow whose nodes describe what happens before, during, and after a conversation.

​
Prerequisites

  • A Klatt Console workspace.
  • A defined conversation outcome and the information the agent must collect.

​
Build the first graph

  1. Create a workflow from the Console.
  2. Keep one Start Call node as the entry point.
  3. Add Agent nodes for focused conversational steps and connect them with transition conditions.
  4. Finish each path with an End Call node.
  5. Add optional Global, API Trigger, or integration nodes only when the workflow needs them.

​
Create with Copilot

Describe the conversation outcome, information to collect, and when the call should finish. Select the workflow language before generating. Copilot uses Qwen3.8 27B to create conversational nodes and checks the graph before saving. Review the generated greetings, prompts, and transitions before using the workflow. Generation and any repair attempts share a one-minute budget. The Console waits up to 90 seconds after preparing the request to allow for generation and saving. The waiting indicator shows elapsed waiting time, not model completion progress. Your description stays in the form if generation fails. If the Console stops waiting, check your workflow list before retrying: the server may have saved it. Copilot’s generated conversation does not itself execute a booking, perform an external lookup, or transfer a call. Configure the appropriate tools separately before promising those actions to callers. To receive business alerts for requested callbacks, enter the team’s email address in the optional callback email field. Copilot adds a callback collection step and a disconnected Callback Notification node. The caller must confirm the details before the normal callback closing step. Email runs after the call and goes only to the configured business inbox. Leaving the field blank disables email notifications.

​
Constraints and failure states

An inbound phone assignment is shown as a Llamada entrante trigger card and is stored with the phone-number configuration, not in workflow JSON. Keep it separate from the First message node. HTTP call triggers start a workflow; an outbound HTTP Request is an action after the call has started. New workflows can use Say, Transfer to human, Topic Router, and Hang up nodes. Transfer branches expose a stable unavailable output, and normal closing paths should reach a Say node before Hang up. Tools and MCP functions attached to a conversational node are visible on the canvas as read-only cards; the node’s UUID references remain authoritative. Start and API Trigger nodes cannot have incoming edges. Agent and End Call nodes require an incoming path, and End Call is terminal. A workflow with disconnected or missing required nodes will not be ready to publish. Existing legacy End Call workflows remain editable and runnable without migration. Memory in this phase is call-local. Durable or cross-call memory is not available through the workflow editor.

​
Protect your data

Write prompts for the minimum information needed to complete the use case. Do not use real phone numbers, names, or account identifiers in examples.