FLOW (structured execution steps)

The FLOW: section adds structured execution steps to any agent. It defines a step-by-step execution graph where each step declares actions (collect information, call tools, respond, branch) and transitions to other steps. Agents operate in reasoning mode by default, where the LLM autonomously decides actions based on the goal. Adding a FLOW: section gives an agent a structured step graph, with each step declaring whether it uses LLM reasoning or deterministic execution via the REASONING: toggle.

Flow structure

Basic syntax

FLOW:
  entry_point: start

  steps:
    - start
    - collect_info
    - process
    - complete

  start:
    REASONING: false
    SET:
      status = "pending"
    RESPOND: "Welcome! Let me help you get started."
    THEN: collect_info

  collect_info:
    REASONING: false
    GATHER:
      - name: required
        prompt: "What is your name?"
    THEN: process

  process:
    REASONING: false
    CALL: process_request
      WITH:
        name: name
      AS: result
    RESPOND: "Done! Your request has been processed."
    THEN: complete

  complete:
    REASONING: false
    RESPOND: "Thank you for using our service. Goodbye!"

Entry point

The entry_point: property declares which step the flow begins at:

FLOW:
  entry_point: greeting

Property	Type	Required	Default	Description
`entry_point`	`string`	No	First step in the `steps` list	The step name where execution begins

If omitted, execution starts at the first step listed in the steps array.

Step list

The steps: array declares the ordered list of step names. While steps can transition to any other step (not just the next in order), the list establishes the canonical ordering:

FLOW:
  steps:
    - greeting
    - collect_account
    - verify
    - process
    - complete

Step definitions

Each step is defined as a named block under FLOW: with its properties indented:

FLOW:
  greeting:
    REASONING: false
    RESPOND: "Hello! How can I help you today?"
    THEN: collect_account

Per-step REASONING toggle

Every step in a FLOW: section must declare REASONING: true or REASONING: false. This controls whether the step uses LLM reasoning or deterministic execution.

FLOW:
  analyze_request:
    REASONING: true
    GOAL: "Analyze the customer's request and determine the best course of action"
    AVAILABLE_TOOLS: [search_knowledge, classify_intent]
    EXIT_WHEN: intent_classified == true
    MAX_TURNS: 5
    THEN: route_request

  route_request:
    REASONING: false
    CHECK: intent == "billing"
    ON_FAIL: general_support
    THEN: billing_flow

Property	Type	Required	Default	Description
`REASONING`	`boolean`	Yes	—	`true` for LLM-driven reasoning, `false` for deterministic execution

Reasoning step properties

When REASONING: true, the following additional properties are available:

Property	Type	Required	Default	Description
`GOAL`	`string`	No	Agent-level `GOAL:`	Step-specific goal (overrides the agent’s goal for this step)
`AVAILABLE_TOOLS`	`string[]`	No	All agent tools	Subset of agent tools available in this step
`EXIT_WHEN`	`string`	No	none	Condition that ends the reasoning loop
`MAX_TURNS`	`number`	No	`10`	Maximum reasoning turns before forced exit
`STEP_CONSTRAINTS`	`string[]`	No	none	Constraints specific to this reasoning zone

Validation rules:

A step with REASONING: true must have either a step-level GOAL or an agent-level GOAL: defined.
A step with REASONING: false should not have a GOAL (it has no effect on deterministic steps).
A step with REASONING: false should not have AVAILABLE_TOOLS (use CALL to invoke tools deterministically).

Entry guards

The WHEN: property on a step defines a condition that must be true for the step to execute. If the condition is false, the step is skipped:

FLOW:
  international_details:
    REASONING: false
    WHEN: "transfer_type == 'international'"
    GATHER:
      - swift_code: required
        prompt: "What is the SWIFT/BIC code?"
    THEN: validate_details

Property	Type	Required	Default	Description
`WHEN`	`string`	No	none	Condition expression that must be true for the step to execute

Attempt limiting

Steps can limit the number of times they execute (useful for retry loops):

FLOW:
  collect_pin:
    REASONING: false
    MAX_ATTEMPTS: 3
    ON_EXHAUSTED: lockout
    GATHER:
      - pin: required
        prompt: "Enter your PIN."
    THEN: verify_pin

Property	Type	Required	Default	Description
`MAX_ATTEMPTS`	`number`	No	none	Maximum number of times this step can execute
`ON_EXHAUSTED`	`string`	No	none	Step to transition to after max attempts exhausted

Step actions

SAY / RESPOND

The RESPOND: action sends a message to the user. It supports template interpolation with {{variable}} syntax:

FLOW:
  greeting:
    REASONING: false
    RESPOND: "Hello, {{customer_name}}! Your balance is {{balance}}."
    THEN: next_step

Multi-line responses use pipe block syntax:

FLOW:
  summary:
    REASONING: false
    RESPOND: |
      Here is your transfer summary:
      From: {{source_account}}
      To: {{beneficiary_name}}
      Amount: {{amount}} {{currency}}
    THEN: confirm

MODEL_CONTEXT on a response

An optional MODEL_CONTEXT sits beside a FLOW step’s RESPOND (or a COMPLETE condition’s RESPOND) and replaces that response only in future model context — it never changes what’s actually sent to the user, the stored transcript, or session values:

FLOW:
  show_products:
    REASONING: false
    RESPOND: "{{products_widget}}"
    MODEL_CONTEXT: "Displayed products {{product_ids}}."
    THEN: next_step

This is useful when the delivered response carries a large presentation payload (a widget, a card, a big table) that would otherwise bloat every later model call for no benefit — MODEL_CONTEXT lets the model keep a short textual summary of what the customer saw instead. MODEL_CONTEXT is a text scalar; a non-text value fails validation (MODEL_CONTEXT_INVALID). An explicitly empty value omits the response from later model requests entirely. Omit the property to keep the historical full-response behavior. See also MODEL_CONTEXT on a tool result for the equivalent policy on a tool’s own result.

PRESENT

The PRESENT: action displays a formatted presentation before collection. It is used alongside GATHER: to show the user what has been collected so far:

FLOW:
  review:
    REASONING: false
    PRESENT: |
      Beneficiary: {{beneficiary_name}}
      Account: {{MASK(beneficiary_account, "last4")}}
      Bank: {{beneficiary_bank_name}}
    GATHER:
      - confirmation: required
    THEN: process

GATHER in flow steps

Within a flow step, GATHER: uses a list syntax different from the top-level GATHER: section:

FLOW:
  collect_details:
    REASONING: false
    GATHER:
      - source_account: required
        prompt: "Your account number?"
    THEN: next_step

Multi-field collection

Collect multiple fields in a single step using the FIELDS: sub-block:

FLOW:
  collect_beneficiary:
    REASONING: false
    GATHER:
      FIELDS:
        - beneficiary_name: required
          prompt: "Full legal name on the account."
        - beneficiary_account: required
          prompt: "Account number or IBAN."
        - beneficiary_bank: required
          prompt: "Name of the bank."
        - country: required
          prompt: "Country of the bank."
          default: "US"
          infer: true
      STRATEGY: llm
    CORRECTIONS: true
    COMPLETE_WHEN: beneficiary_name AND beneficiary_account AND beneficiary_bank AND country
    THEN: validate

Flow gather field properties

Each field in a flow GATHER: supports these properties:

Property	Type	Required	Default	Description
`required` / optional value after name	`boolean`	No	`true`	Whether the field must be collected
`prompt`	`string`	No	none	Question shown to the user
`type`	`string`	No	`"string"`	Data type
`default`	`any`	No	none	Default value
`validation`	`string`	No	none	Validation expression
`infer`	`boolean`	No	`false`	Allow LLM inference
`infer_confidence`	`number`	No	`0.8`	Minimum inference confidence
`infer_confirm`	`boolean`	No	`true`	Confirm inferred values
`extraction_hints`	`string[]`	No	none	LLM extraction guidance
`range`	`boolean`	No	`false`	Collect as range
`list`	`boolean`	No	`false`	Collect as array
`activation`	`string` , `{when: string}`	No	none	Activation mode
`depends_on`	`string[]`	No	none	Field dependencies
`prompt_mode`	`"ask"` , `"extract_only"`	No	`"ask"`	Prompt usage mode

Flow gather fields also accept the same additional properties as top-level GATHER fields: entity_ref, options, message_key, satisfied_by, validation_process, retry_prompt, max_retries, preferences, sensitive, sensitive_display, mask_config, pii_type, transient, extraction_pattern, extraction_group, and semantics. In addition, a flow gather field may carry rich_content format variants for its prompt. Note that flow gather uses validation: where the top-level section uses validate:.

GATHER block properties

Alongside FIELDS:, a flow GATHER: block accepts these block-level properties:

Property	Type	Description
`STRATEGY`	`"auto"` , `"ml"` , `"llm"` , `"hybrid"` , `"pattern"`	Collection approach (see below). Also settable per field.
`PROMPT`	`string`	A single prompt used to collect the whole block.
`MESSAGE_KEY`	`string`	Locale catalog key for the block prompt.

The STRATEGY: value controls the collection approach:

Value	Description
`auto`	Let the platform choose the best available strategy
`ml`	Use the ML/NLU entity model
`llm`	Use LLM to extract values from natural conversation
`pattern`	Use pattern matching and extraction rules
`hybrid`	Combine ML and LLM extraction

CORRECTIONS

When CORRECTIONS: true, the user can naturally correct previously collected values without restarting the step:

FLOW:
  collect_info:
    REASONING: false
    GATHER:
      - name: required
      - email: required
    CORRECTIONS: true
    THEN: next_step

COMPLETE_WHEN

The COMPLETE_WHEN: condition specifies when the gather step is considered complete:

FLOW:
  collect_all:
    REASONING: false
    GATHER:
      FIELDS:
        - field_a: required
        - field_b: required
        - field_c: optional
    COMPLETE_WHEN: field_a AND field_b
    THEN: process

CALL…WITH…AS

The CALL: action invokes a tool. Use WITH: to pass parameters and AS: to bind the result to a variable:

FLOW:
  verify_step:
    REASONING: false
    CALL: verify_account
      WITH:
        account_id: source_account
      AS: acctResult
    RESPOND: "Account verified: {{acctResult.owner_name}}"
    THEN: next_step

Property	Type	Required	Default	Description
`CALL`	`string`	—	—	Tool name to invoke
`WITH`	`Record<string, string>`	No	none	Key-value parameter mapping
`AS`	`string`	No	none	Variable name to bind the tool result

WITH parameters

The WITH: block maps tool parameter names to values or variable references:

CALL: calculate_fees
  WITH:
    transfer_type: transfer_type
    amount: amount
    currency: currency
    destination_country: beneficiary_country
  AS: feeResult

Values can be:

Variable references: amount (resolves the session variable amount)
Literal strings: "domestic"
Expressions: COALESCE(reference, "")
Nested objects — a key with no inline value followed by an indented sub-block becomes a nested object argument, for tools whose schema requires object parameters:

CALL: ivr_digit_input
  WITH:
    prompt: "Enter your account number"
    noInputConfig:
      timeoutMs: 5000
      maxRetries: 2
    noMatchConfig:
      message: "That didn't match. Please try again."
  AS: digitResult

Nesting is preserved by indentation. Scalar leaves keep their raw form and are coerced at runtime ("30" → 30, "[15, 16]" → [15, 16]).

Localized WITH arguments

A WITH value can take its text from the project’s locale files (locales/<locale>/<agent>.json or locales/<locale>/_shared.json) with "{{locale.KEY}}", or a bare locale.KEY. The text is chosen for the caller’s current interaction locale (with the same fallback chain as MESSAGE_KEY — for example hi-IN, then hi), and {{…}} placeholders inside the locale text are rendered too:

FLOW:
  collect_card_number:
    REASONING: false
    CALL: ivr_digit_input
      WITH:
        prompt: "{{locale.CARD_PROMPT}}"
        maxDigits: 19
        endingKeyPress: "#"
        noInputConfig:
          timeout: 30
          maxRetries: 2
          message: "{{locale.CARD_NO_INPUT}}"
      AS: cardNumberResult
    ON_RESULT:
      - IF: cardNumberResult.success == false
        THEN: payment_input_failed
      - ELSE:
          THEN: validate_card_number

If a referenced key isn’t defined for the caller’s locale (and no less-specific locale in the chain provides it), the tool is not called — the CALL result is success: false with error.code: "LOCALE_KEY_MISSING", so the step’s failure branch runs and raw {{locale.KEY}} text never reaches the tool or the caller. Only authored text is treated as a locale reference; a session value that happens to contain {{locale.…}} passes through as plain data. Supported forms are "{{locale.KEY}}" (optionally with filters, like "{{locale.KEY | upper}}", and mixed with other text) and a bare locale.KEY; an expression such as locale["KEY"] or locale.KEY + "!" is not supported and the CALL is not run.

SET

The SET: action assigns values to session variables:

FLOW:
  init:
    REASONING: false
    SET:
      status = "pending"
      retry_count = 0
      sanctions_clear = false
    THEN: next_step

Each assignment uses variable = expression syntax. The expression is resolved at execution time and can reference:

Literal values: "pending", 0, true, false
Variable references: acctResult.balance
Function calls: FORMAT_CURRENCY(amount, "USD"), COALESCE(value, "default"), ADD(a, b), SUB(a, b), ROUND(n, decimals)
Unique ID generation: UNIQUE_ID(12)
Current timestamp: NOW()

An unquoted JSON array or object literal is stored as a structured value. A JSON string’s string-typed leaves may contain {{variable}} templates — the collection is parsed first, then its string values are rendered, so substituted data is never reinterpreted as JSON:

SET:
  filters = [{"field":"customer","operator":"in","value":["Public", "{{employer_name}}"]}]

This stores an array of objects correctly even when employer_name contains quotes or backslashes. Prefer a direct variable reference when constructing a computed collection instead of interpolating one into JSON-shaped text:

SET:
  filters = [{"field":"customer","operator":"in","value":["Public", employer_name]}]

Surround the whole value with quotes when JSON-shaped text is intentional — SET: payload_text = '[{"customer":"{{employer_name}}"}]' stores a string, not a structured value. A session TYPE declaration alone doesn’t validate every SET write; validate structured arguments at the tool boundary (pass the variable to a typed parameter, such as filters: object[], through WITH).

CHECK

The CHECK: action evaluates a condition. If the condition is false, execution transitions to the ON_FAIL: step:

FLOW:
  check_limits:
    REASONING: false
    CHECK: amount <= available_balance AND ADD(daily_used, amount) <= daily_limit
    ON_FAIL: over_limit
    THEN: proceed

Property	Type	Required	Default	Description
`CHECK`	`string`	—	—	Condition expression to evaluate
`ON_FAIL`	`string`	No	none	Step to go to if the condition is false

CLEAR

The CLEAR: action removes variables from the session context:

FLOW:
  reset_beneficiary:
    REASONING: false
    CLEAR: [beneficiary_name, beneficiary_account, beneficiary_id]
    THEN: collect_beneficiary

TRANSFORM

The TRANSFORM: action filters, maps, sorts, and limits an array from the session context:

FLOW:
  filter_results:
    REASONING: false
    TRANSFORM:
      SOURCE: search_results
      AS: hotel
      INTO: filtered_hotels
      FILTER: "hotel.rating >= 4"
      MAP:
        name: hotel.name
        price: hotel.price_per_night
        rating: hotel.rating
      SORT_BY: price asc
      LIMIT: 5
    THEN: show_results

Property	Type	Required	Default	Description
`SOURCE`	`string`	Yes	—	Dot-path to the source array
`AS`	`string`	Yes	—	Loop variable name
`INTO`	`string`	Yes	—	Output variable name
`FILTER`	`string`	No	none	Condition expression using the loop variable
`MAP`	`Record<string, string>`	No	none	Field mapping expressions
`SORT_BY`	`string`	No	none	Sort field and direction (`asc` or `desc`)
`LIMIT`	`number`	No	none	Maximum number of items in the output

LOG

The LOG: action emits a trace-only diagnostic (not shown to the user). Use the inline or block form:

FLOW:
  audit:
    REASONING: false
    LOG: "Entering audit step"
    # or, with a level:
    # LOG:
    #   MESSAGE: "Balance below threshold"
    #   LEVEL: warn          # debug | info | warn | error
    THEN: next_step

AWAIT_ATTACHMENT

The AWAIT_ATTACHMENT: action pauses the step until the user uploads a file.

FLOW:
  collect_id_doc:
    REASONING: false
    AWAIT_ATTACHMENT:
      NAME: id_document
      PROMPT: "Please upload a photo of your ID."
      CATEGORY: image        # image | document | audio | video
      REQUIRED: true
      TIMEOUT: 120
      ON_TIMEOUT: manual_review
    THEN: verify_id

Property	Type	Description
`NAME`	`string`	Variable the uploaded attachment is stored under.
`PROMPT`	`string`	Message asking the user to upload.
`CATEGORY`	`string`	`image`, `document`, `audio`, or `video`.
`REQUIRED`	`boolean`	Whether the upload is mandatory.
`TIMEOUT`	`number`	Seconds to wait for the upload.
`ON_TIMEOUT`	`string`	Step to transition to if the upload times out.

SECURE_INPUT

The SECURE_INPUT: action pauses the step to collect one or more sensitive values — a card number, CVV, or similar — via DTMF and/or speech, and delivers them directly to one tool, without the raw values ever passing through the LLM, transcript, session state, logs, or traces. It’s the PCI-safe alternative to GATHER for data that must never reach the model.

SECURE_INPUT is currently authored only in the legacy .agent.abl (line-based) format. The .agent.yaml parser does not yet accept this action.

FLOW:
  collect_card:
    REASONING: false
    SECURE_INPUT:
      MODE: [dtmf]                          # dtmf | speech, one or both
      FIELDS:
        - card_number:
            PROMPT: { en: "Please enter your 16-digit card number." }
            COLLECT: { digits: 13..19, finishOnKey: "#" }
            VALIDATE: [ luhn ]
        - cvv:
            PROMPT: { en: "And the 3-digit security code." }
            COLLECT: { digits: 3..4 }
      MAX_ATTEMPTS: 3
      CANCEL: { dtmf_key: "*" }
      CALL charge_card WITH: { pan: "{{secure.card_number}}", cvv: "{{secure.cvv}}" }
      ON_SUCCESS: confirm
      ON_TIMEOUT: retry_by_agent
      ON_CANCEL: retry_by_agent
      ON_FAIL: human_agent
    THEN: confirm

Property	Type	Description
`MODE`	`("dtmf" \| "speech")[]`	Which collection channel(s) are accepted. Required; at least one.
`FIELDS`	list	One or more fields to collect, in order. Each is a `- <name>:` entry with `PROMPT`, `COLLECT`, and optional `VALIDATE`.
`MAX_ATTEMPTS`	`number`	Failed collection attempts allowed before `ON_FAIL`.
`CANCEL`	`object`	Cancellation trigger: `dtmf_key` and/or `keywords`.
`CALL <tool> WITH: {...}`	—	The deliver spec — the single tool invoked with the collected values. Only the inline-object `WITH:` form is supported. Reference a collected field as a whole-value placeholder `{{secure.<name>}}`.
`ON_SUCCESS`	`string`	Step to transition to after successful collection and delivery.
`ON_TIMEOUT`	`string`	Step to transition to if collection times out.
`ON_CANCEL`	`string`	Step to transition to if the caller cancels.
`ON_FAIL`	`string`	Step to transition to if delivery or validation ultimately fails.

Field properties

Property	Type	Description
`PROMPT`	`{ <locale>: string }` or `{ template: string }`	Locale-keyed prompt text, or a reference to a named template. At least one non-empty entry is required.
`COLLECT`	`object`	`digits: N..M` (min/max digit count), `finishOnKey`, `interDigitTimeoutMs`, `asrTimeoutMs` (spoken-path silence window).
`VALIDATE`	list	Validation rules: a bare rule name (`luhn`), an inline object (`{ length: 4..4 }`, `{ date_mmYY: "not_past" }`), or a delegated `CALL <tool> WITH: {...}` rule.

References inside deliver’s WITH: block must be a whole-value placeholder — pan: "{{secure.card_number}}" is valid; embedding it in a larger string (pan: "card:{{secure.card_number}}") or referencing an undeclared field is a compile error.

Every collected value lives only in a local secure buffer for the duration of the gate and is zeroized on every exit path (success, timeout, cancel, or failure) — it is never written to session state, so it cannot be referenced by {{ }} outside the deliver block, and it never appears in a trace, span, or log.

Diagnostic	Fires when
`SECURE_INPUT_INVALID_MODE`	`MODE` is missing, empty, or contains a value other than `dtmf`/`speech`.
`SECURE_INPUT_MISSING_DELIVER_TOOL`	The `CALL ... WITH:` deliver spec has no tool name.
`SECURE_INPUT_MISSING_PROMPT`	No `FIELDS` are declared, or a field’s `PROMPT` has neither a locale entry nor a `template` reference.
`SECURE_UNKNOWN_FIELD`	A `deliver` `WITH:` value references `{{secure.<name>}}` for a field that isn’t declared in `FIELDS`.
`SECURE_EMBEDDED_PLACEHOLDER`	A `deliver` `WITH:` value embeds `{{secure.*}}` inside a larger string instead of using it as the whole value.

MESSAGE_KEY and BEHAVIOR

Two additional step-level properties:

MESSAGE_KEY: — a locale catalog key used to localize the step’s RESPOND: message.
BEHAVIOR: — free-form guidance text appended to the step’s reasoning goal (a convenience alias that folds into GOAL).

RESOLVE_SIP_DESTINATION

RESOLVE_SIP_DESTINATION: is a step action that computes a dynamic SIP transfer authority (VDN/host/port) before a call_transfer step runs. It runs a feeder — a workflow tool or a session memory key — matches the candidate against the approved_authorities allow-list declared on the call_transfer tool’s sipTransferId parameter, and commits the approved authority to a trusted server-side routing channel that the transfer then reads. The model never sees or sets the destination.

FLOW:
  resolve_destination:
    REASONING: false
    RESOLVE_SIP_DESTINATION:
      FROM_WORKFLOW: "lookup_vdn_by_region_language"   # or: FROM_MEMORY: routing_decision
      TIMEOUT_MS: 1500
    THEN: transfer_step

  transfer_step:
    REASONING: false
    CALL: call_transfer(callTransferType: "sip")
    THEN: COMPLETE

Sub-key	Type	Description
`FROM_WORKFLOW`	`string`	Name of a workflow tool invoked as the destination feeder.
`FROM_MEMORY`	`string`	Session memory key to read as the feeder (use instead of `FROM_WORKFLOW`).
`TIMEOUT_MS`	`number`	Hard timeout for the feeder, in milliseconds.

The feeder’s result supplies the {{route.vdn}} / {{route.ip}} / {{route.port}} values for the sipTransferId template. The two-zone template and the approved_authorities allow-list are declared on the tool parameter — see Dynamic destinations in the tools reference.

Branching and control flow

THEN / ON_FAIL

The most basic branching: THEN: specifies the next step on success, and ON_FAIL: specifies the step on failure:

FLOW:
  check_status:
    REASONING: false
    CHECK: account_status == "active"
    ON_FAIL: inactive_account
    THEN: proceed

ON_FAIL: also accepts a structured block for recovery flows — COLLECT: (fields to re-collect), GOTO: (step), RETRY: true, RESPOND:, and THEN::

FLOW:
  validate_details:
    REASONING: false
    CHECK: routing_number_valid == true
    ON_FAIL:
      RESPOND: "That routing number looks off — let's try again."
      COLLECT: [routing_number]
      GOTO: collect_routing

ON_RESULT

ON_RESULT: provides multi-way branching based on the result of a CALL: action. Each branch has an IF: condition, optional actions, and a THEN: transition:

FLOW:
  verify_step:
    REASONING: false
    CALL: verify_account
      WITH:
        account_id: source_account
      AS: acctResult
    ON_RESULT:
      - IF: acctResult.status == "active"
        SET:
          customer_name = acctResult.owner_name
          balance = acctResult.available_balance
        RESPOND: "Account verified. Hello, {{customer_name}}."
        THEN: next_step
      - IF: acctResult.status == "frozen"
        RESPOND: "Your account is frozen. Please contact your branch."
        THEN: end
      - ELSE:
        RESPOND: "Account not found. Please check the number."
        THEN: collect_account

ON_RESULT branch properties

Property	Type	Required	Default	Description
`IF`	`string`	No	—	Condition expression. Omit for `ELSE` branch.
`RESPOND`	`string`	No	none	Message to display
`SET`	`Record<string, string>`	No	none	Variable assignments
`CALL`	`string`	No	none	Optional nested tool call
`THEN`	`string`	Yes	—	Next step

The ELSE branch (a branch with no IF condition) matches when no other condition is true.

ON_SUCCESS / ON_FAIL

An alternative to ON_RESULT: for simpler success/failure branching:

FLOW:
  call_api:
    REASONING: false
    CALL: submit_request
      WITH:
        data: request_data
      AS: result
    ON_SUCCESS:
      RESPOND: "Request submitted: {{result.id}}"
      THEN: done
    ON_FAIL:
      RESPOND: "Request failed. Please try again."
      THEN: retry_step

Both ON_SUCCESS: and ON_FAIL: support conditional branches:

FLOW:
  process:
    REASONING: false
    CALL: process_order
      AS: orderResult
    ON_SUCCESS:
      - IF: orderResult.express == true
        RESPOND: "Express order confirmed!"
        THEN: express_fulfillment
      - ELSE:
        RESPOND: "Order confirmed."
        THEN: standard_fulfillment
    ON_FAIL:
      - IF: orderResult.error == "out_of_stock"
        RESPOND: "Item is out of stock."
        THEN: suggest_alternatives
      - ELSE:
        RESPOND: "An error occurred."
        THEN: error_handling

ON_INPUT

ON_INPUT: provides branching based on user input, typically used after a GATHER: action:

FLOW:
  confirm:
    REASONING: false
    GATHER:
      - confirmation: required
    ON_INPUT:
      - IF: input.contains("yes") OR input.contains("confirm")
        THEN: execute
      - IF: input.contains("no") OR input.contains("cancel")
        RESPOND: "Cancelled."
        THEN: cleanup
      - ELSE:
        RESPOND: "Please type 'yes' to confirm or 'no' to cancel."
        THEN: confirm

A step that has only ON_INPUT branches — no RESPOND/prompt and no default (ELSE) branch — traps any unmatched input on the same step forever. The compiler warns (FLOW_PROMPTLESS_ON_INPUT_UNMATCHED_TRAP): add a default ELSE route or an authored prompt unless the wait is intentional.

Digressions

Digressions are intent-based escapes that can interrupt the current step. They match user intent patterns and respond accordingly:

FLOW:
  collect_details:
    REASONING: false
    GATHER:
      - account: required

    DIGRESSIONS:
      - INTENT: "what is swift"
        RESPOND: "A SWIFT code is an 8 or 11 character code identifying a bank internationally."
        RESUME: true
      - INTENT: "cancel"
        RESPOND: "Transaction cancelled."
        GOTO: cleanup
      - INTENT: "speak to agent"
        RESPOND: "Connecting you with a specialist."
        DELEGATE: Live_Agent

Digression properties

Property	Type	Required	Default	Description
`INTENT`	`string`	Yes	—	Intent pattern to match
`KEYWORDS`	`string[]`	No	none	Explicit keywords for matching
`CONDITION`	`string`	No	none	Additional condition to check
`RESPOND`	`string`	No	none	Response message
`MESSAGE_KEY`	`string`	No	none	Locale catalog key for the response
`SET`	`Record<string,string>`	No	none	Variable assignments (within the `DO:` block)
`RESUME`	`boolean`	No	`false`	Return to the current step after handling
`GOTO`	`string`	No	none	Transition to a specific step
`HANDOFF`	`string`	No	none	Hand off to another agent (supports `RETURN:` / `ON_RETURN:`)
`DELEGATE`	`string`	No	none	Delegate to another agent (requires `RETURN: true`)
`CALL`	`string`	No	none	Tool to invoke
`CLEAR`	`string[]`	No	none	Variables to clear

When RESUME: true, the user returns to the interrupted step after the digression response. When GOTO: is specified, the flow transitions to that step instead. RESUME, GOTO, and HANDOFF are terminal.

For multiple ordered actions, use the canonical DO: block instead of flat keys. Each list item is an action (RESPOND, SET, CLEAR, CALL, HANDOFF, DELEGATE, GOTO, RESUME), and HANDOFF/DELEGATE may carry RETURN: and ON_RETURN: (with MAP:). Mixing flat keys with a DO: block is discouraged.

DIGRESSIONS:
  - INTENT: "check balance"
    DO:
      - RESPOND: "Let me pull that up."
      - HANDOFF: Account_Info
        RETURN: true
      - RESUME: true

Global digressions

Digressions declared at the flow level (under global_digressions:) are available at every step:

FLOW:
  global_digressions:
    - INTENT: "cancel"
      RESPOND: "Transaction cancelled."
      GOTO: cleanup

    - INTENT: "help"
      RESPOND: "I can help with account inquiries, transfers, and balance checks."
      RESUME: true

    - INTENT: "speak to agent"
      RESPOND: "Connecting you with a live agent."
      DELEGATE: Live_Agent_Transfer

Sub-intents

Sub-intents are scoped intents valid only within a specific step. They handle step-specific user requests like corrections or clarifications:

FLOW:
  collect_beneficiary:
    REASONING: false
    GATHER:
      FIELDS:
        - name: required
        - account: required
        - bank: required

    SUB_INTENTS:
      - INTENT: "change name"
        CLEAR: [name]
        RESPOND: "What is the correct name?"
      - INTENT: "change account"
        CLEAR: [account]
        RESPOND: "What is the correct account number?"
      - INTENT: "change bank"
        CLEAR: [bank, routing_code]
        RESPOND: "What is the correct bank name?"

Sub-intent properties

Property	Type	Required	Default	Description
`INTENT`	`string`	Yes	—	Intent pattern to match
`RESPOND`	`string`	No	none	Response message
`MESSAGE_KEY`	`string`	No	none	Locale catalog key for the response
`CLEAR`	`string[]`	No	none	Variables to clear (triggers re-collection)
`SET`	`Record<string, string>`	No	none	Variables to set
`CALL`	`string`	No	none	Tool to invoke
`RESUME`	`boolean`	No	`true`	Stay in the current step

Interactive actions

Flow steps can present interactive UI elements (buttons, selects, inputs) to the user. These are attached to RESPOND: messages and handled with ON_ACTION: callbacks.

Action elements

Interactive actions are defined in an ACTIONS: block within a step:

FLOW:
  choose_option:
    REASONING: false
    RESPOND: "How would you like to proceed?"
    ACTIONS:
      - id: "option_transfer"
        type: button
        label: "Wire Transfer"
        value: "wire"
      - id: "option_ach"
        type: button
        label: "ACH Transfer"
        value: "ach"
      - id: "option_check"
        type: button
        label: "Send a Check"
        value: "check"
    ON_ACTION:
      - ACTION: "option_transfer"
        SET:
          transfer_method = "wire"
        THEN: wire_flow
      - ACTION: "option_ach"
        SET:
          transfer_method = "ach"
        THEN: ach_flow
      - ACTION: "option_check"
        SET:
          transfer_method = "check"
        THEN: check_flow

Element types

Buttons

ACTIONS:
  - id: "confirm_btn"
    type: button
    label: "Confirm"
    value: "confirmed"

ACTIONS:
  - id: "currency_select"
    type: select
    label: "Select currency"
    options:
      - id: "usd"
        label: "US Dollar"
        description: "United States Dollar"
      - id: "eur"
        label: "Euro"
        description: "European Union Euro"
      - id: "gbp"
        label: "British Pound"

Input fields

ACTIONS:
  - id: "amount_input"
    type: input
    label: "Enter amount"
    inputType: number
    placeholder: "0.00"
    required: true

Action element properties

Property	Type	Required	Default	Description
`id`	`string`	Yes	—	Unique identifier for the action element
`type`	`"button"` , `"select"` , `"input"`	Yes	—	Element type
`label`	`string`	Yes	—	Display label
`value`	`string`	No	none	Hidden value sent when the element is interacted with
`description`	`string`	No	none	Subtitle or helper text
`options`	`{id, label, description?}[]`	No	none	Options for `select` type
`inputType`	`"text"` , `"number"` , `"date"` , `"time"` , `"email"`	No	`"text"`	Input field type (for `input` type)
`placeholder`	`string`	No	none	Placeholder text (for `input` type)
`required`	`boolean`	No	`false`	Whether the input is required (for `input` type)

Form submission

When a step contains input type elements, you can configure a form submission button:

ACTIONS:
  - id: "name_input"
    type: input
    label: "Your name"
    inputType: text
    required: true
  - id: "email_input"
    type: input
    label: "Your email"
    inputType: email
    required: true
  SUBMIT_LABEL: "Submit"
  SUBMIT_ID: "form_submit"

The ACTIONS: block also accepts an optional RENDER_ID: to give the whole action set a stable identifier for rendering/telemetry.

ON_ACTION callbacks

The ON_ACTION: block defines handlers for user interactions with action elements:

ON_ACTION:
  - ACTION: "confirm_btn"
    RESPOND: "Confirmed! Processing your request."
    SET:
      confirmed = true
    THEN: process_step
  - ACTION: "cancel_btn"
    RESPOND: "Cancelled."
    THEN: cleanup

ON_ACTION handler properties

Property	Type	Required	Default	Description
`ACTION`	`string`	Yes	—	The `id` of the action element that triggered this handler
`CONDITION`	`string`	No	none	Optional value-based condition
`RESPOND`	`string`	No	none	Response message
`SET`	`Record<string, string>`	No	none	Variable assignments
`CLEAR`	`string[]`	No	none	Variables to clear
`CALL`	`string`	No	none	Tool to invoke (requires `AS`)
`LOG`	`string`	No	none	Trace-only diagnostic
`HANDOFF`	`string`	No	none	Hand off to another agent
`DELEGATE`	`string`	No	none	Delegate to another agent (`RETURN:`/`ON_RETURN:` supported)
`COMPLETE`	`boolean`	No	none	Terminal — mark the flow complete
`THEN` / `GOTO` / `TRANSITION`	`string`	No	none	Step to transition to (three interchangeable keywords)

For multiple ordered actions in one handler, use a canonical DO: block whose list items are actions (SET, CLEAR, LOG, RESPOND, CALL, GOTO/TRANSITION/THEN, HANDOFF, DELEGATE, COMPLETE).

Rich content

Steps can include rich content in multiple formats alongside RESPOND: messages. The runtime selects the appropriate format based on the channel. The block keyword is RICH_CONTENT: (canonical) or FORMATS: (original spelling, still accepted); the .agent.yaml format accepts rich_content or formats the same way.

FLOW:
  show_summary:
    REASONING: false
    RESPOND: "Here is your transfer summary."
    FORMATS:
      MARKDOWN: |
        ## Wire Transfer Summary
        | Field | Value |
        |-------|-------|
        | From | {{source_account}} |
        | To | {{beneficiary_name}} |
        | Amount | {{amount}} {{currency}} |
      ADAPTIVE_CARD: |
        {"type": "AdaptiveCard", "body": [...]}

Rich content format properties

The runtime recognizes these format keys. In addition to the messaging formats, several structured template types are available (see Rich content for their schemas):

Format	Description
`MARKDOWN`	Formatted markdown text
`ADAPTIVE_CARD`	Microsoft Adaptive Cards JSON
`HTML`	HTML content
`SLACK`	Slack Block Kit JSON
`AG_UI`	AG-UI / CopilotKit event JSON
`WHATSAPP`	WhatsApp interactive message JSON
`CAROUSEL`	Scrollable cards (title/subtitle/image/buttons); can also be authored as a standalone block after `RESPOND:`
`QUICK_REPLIES`	Quick-reply chips
`LIST`	Vertical list of items
`IMAGE`	Image with caption/alt
`VIDEO`	Video with caption/alt
`AUDIO`	Audio with caption/alt
`FILE`	File attachment
`KPI`	KPI metric tile
`TABLE`	Columns + rows
`CHART`	Bar/line/pie chart
`FORM`	Form fields + submit
`PROGRESS`	Progress bar/circle
`FEEDBACK`	Thumbs/stars/scale feedback

Voice configuration

Steps can include voice-specific overrides for text-to-speech engines:

FLOW:
  greeting:
    REASONING: false
    RESPOND: "Welcome to wire transfer services."
    VOICE:
      SSML: |
        <speak>
          Welcome to <emphasis>wire transfer</emphasis> services.
        </speak>
      INSTRUCTIONS: "Speak in a warm, professional tone."
      PLAIN_TEXT: "Welcome to wire transfer services."

Property	Type	Description
`SSML`	`string`	W3C SSML markup for TTS engines
`INSTRUCTIONS`	`string`	Natural language voice style instructions
`PLAIN_TEXT`	`string`	Voice-optimized plaintext (fallback for all engines)
`BARGE_IN`	`"allow"` \| `"disallow"`	Whether the caller may interrupt (barge in on) this spoken output.
`STREAMING`	`boolean`	TTS delivery mode for this spoken output. Omitted defaults to `true` (streaming).
`END_OF_SPEECH_TURN_TYPE`	`string`	Expected shape of the caller’s next answer, used to pick an end-of-speech (pause) timeout. See Per-turn endpointing.
`END_OF_SPEECH_TIMEOUT_MS`	`number`	Explicit end-of-speech timeout in milliseconds, overriding the preset.

Per-turn endpointing

END_OF_SPEECH_TURN_TYPE is a small, deliberately-closed vocabulary describing what kind of answer the caller is expected to give next — the runtime resolves it to a concrete end-of-speech (silence/pause) timeout for the active speech recognizer, so authors don’t have to guess a millisecond value per turn:

Value	Use for
`simple_confirmation`	A yes/no or short acknowledgement.
`structured_value`	A structured value like an account number or date.
`open_ended_question`	An open-ended question expecting a longer, free-form answer.
`complex_explanation`	A caller explanation that may take a while to finish.
`anything_else`	Anything not covered above.

It can be set at any VOICE scope — agent-wide under EXECUTION.voice, on a behavior profile, on a flow step, or per RESPOND — with the narrowest scope winning, same as BARGE_IN/STREAMING:

FLOW:
  collect_value:
    REASONING: false
    VOICE:
      END_OF_SPEECH_TURN_TYPE: structured_value
      END_OF_SPEECH_TIMEOUT_MS: 900
    RESPOND: "Please provide the value."
      VOICE:
        END_OF_SPEECH_TURN_TYPE: open_ended_question   # per-RESPOND override
        END_OF_SPEECH_TIMEOUT_MS: 1400

END_OF_SPEECH_TIMEOUT_MS overrides the preset’s timeout with an explicit millisecond value when set alongside (or instead of) END_OF_SPEECH_TURN_TYPE.

Per-turn endpointing applies to the platform’s own speech-recognition pipeline. It does not affect TTS streaming, and is ignored on native realtime/speech-to-speech voice models where the provider owns turn detection. Omit it to fall back to the agent’s conversation-level pause configuration.

Scoped barge-in

barge_in (values allow / disallow) sets whether the caller can interrupt a specific spoken output — for example, forcing a compliance disclosure to finish. It may be authored at three scopes, from broadest to narrowest, with the narrower winning:

FLOW:
  notice:
    REASONING: false
    BARGE_IN: disallow            # step-wide: applies to this step's outputs
    RESPOND: "This required notice must play in full."
      VOICE:
        BARGE_IN: allow           # per-RESPOND override for this output

It can also be set on a named template’s VOICE: block. Placing barge_in on the agent-wide EXECUTION.voice block, or on branch/handler voice blocks, is rejected (VOICE_BARGE_IN_ILLEGAL_PLACEMENT); an invalid value is VOICE_INVALID_BARGE_IN.

This scoped, per-output policy is distinct from the agent-wide barge-in behavior authored under CONVERSATION → listening. Use scoped barge_in to protect (or open up) individual utterances.

Scoped streaming

streaming (true / false) sets the TTS delivery mode for a specific spoken output — whether audio starts playing as soon as the first tokens are ready (streaming, the default) or the runtime waits for the complete response before speaking it (non-streaming). It follows the same authoring scopes as barge_in: step-wide, per-RESPOND, or on a named template’s VOICE: block, with the narrower scope winning.

FLOW:
  read_confirmation_code:
    REASONING: false
    STREAMING: false               # step-wide: wait for the full utterance before speaking it
    RESPOND: "Your confirmation code is {{confirmation_code}}."
      VOICE:
        STREAMING: false           # equivalent per-RESPOND override

Omitting streaming defaults to true (streaming) at every scope.

Step-level no-input (caller silence)

A FLOW step can carry its own caller-silence policy in its own VOICE: block, as ON_NO_INPUT. It takes the same keys as CONVERSATION.listening.on_no_input (agent/project-wide) and applies on KoreVG pipeline voice while that step is the one waiting on the caller:

CONVERSATION:
  listening:
    on_no_input:
      enabled: true
      mode: static
      timeout_ms: 5000
      max_retries: 3
      messages:
        - text: "Are you still there?"
        - text: "Hello?"

FLOW:
  ask_account:
    REASONING: false
    RESPOND: "What's your account number?"
    GATHER:
      - account_number: required
    VOICE:
      ON_NO_INPUT:
        timeout_ms: 10000
        messages:
          - text: "Could you tell me your account number, {{memo_name}}?"
    THEN: complete

Owner. When the silence timer starts, the step currently waiting owns the window. The block applies only to that step; after COMPLETE/ESCALATE, or on a step with no block, the agent/project policy applies as usual.
Merging. Fields merge one at a time over the project and agent policy — a step can override just timeout_ms and inherit everything else. max_retries, relaxed_interval_ms, on_exhausted, and exhausted_message all follow the same rule, and enabled: true on a step turns silence handling on for that step even when the agent has it off.
Messages. Step messages don’t replace the agent-level list — each silence plays agent message N followed by step message N as one utterance (“Are you still there? Could you tell me your account number, Sam?”). Once the step’s own list is used up, the agent message plays alone (or the platform default, if the agent has none), so a step block never ends the call sooner than the agent alone would.
Retry count. Restarts when the caller speaks, and when a different step (or the same step entered again) takes ownership of the window.
Variables. {{var}} placeholders render in agent messages, step messages, and exhausted_message. A step message with a missing variable is skipped; an agent or exhausted message with a missing variable falls back to the platform default text.

ON_NO_INPUT is only legal directly in a FLOW step’s own VOICE: block. Placed under a GATHER field, RESPOND, a branch, a handler, or a response format, it’s a compile error (VOICE_NO_INPUT_ILLEGAL_PLACEMENT). The YAML format uses a step-level on_no_input: key.

Step-level error handling

Steps can define local error handlers that override agent-level ON_ERROR: handlers:

FLOW:
  call_external:
    REASONING: false
    CALL: external_api
      WITH:
        query: user_query
      AS: apiResult
    ON_ERROR:
      tool_error:
        RESPOND: "The service is responding slowly. Retrying..."
        SUBTYPE: tool_timeout
        RETRY: 2
        RETRY_DELAY: 1000
        RETRY_BACKOFF: exponential
        RETRY_MAX_DELAY: 8000
        THEN: CONTINUE
      validation_error:
        RESPOND: "An error occurred. Let me try a different approach."
        THEN: RETRY_STEP

The error type (the handler’s key) is matched against a fixed, canonical set — default, llm_error, tool_error, routing_error, validation_error, timeout_error, and unknown_error. A key outside this set (for example the older tool_timeout, invalid_input, or api_error) is flagged at compile time (ON_ERROR_HANDLER_TYPE_DRIFT) and never matches at runtime — see Error types for the full table and the deprecated-name mapping. Narrow tool_error with SUBTYPE/SUBTYPES (known values: rate_limit, auth_failure, network_error, tool_timeout).

Step ON_ERROR handler properties

Property	Type	Description
`SUBTYPE`	`string`	Narrow the handler to a specific error subtype.
`RESPOND`	`string`	Message to show when the error fires.
`RETRY`	`number`	Retry attempts before giving up.
`RETRY_DELAY`	`number`	Delay (ms) between retries.
`RETRY_BACKOFF`	`string`	Backoff strategy: `fixed`, `exponential`, or `linear`.
`RETRY_MAX_DELAY`	`number`	Maximum delay (ms) between retries.
`BACKTRACK_TO`	`string`	Step to backtrack to (used with `THEN: BACKTRACK`).
`HANDOFF_TARGET`	`string`	Target agent (used with `THEN: HANDOFF`).
`THEN`	`string`	Next action: `CONTINUE`, `COMPLETE`, `ESCALATE`, `BACKTRACK`, `RETRY_STEP`, or `HANDOFF`. A step name is not a valid value here — a flow step’s own `THEN:` navigates to a step, but an `ON_ERROR` handler’s `THEN:` takes only one of these six actions.

Complete example

AGENT: Simple_Order
VERSION: "1.0.0"

GOAL: "Help customers place orders."

PERSONA: "Friendly order assistant."

TOOLS:
  check_inventory(product_id: string) -> {available: boolean, quantity: number}
    description: "Check product availability"
    type: http
    endpoint: "/api/inventory/check"
    method: GET

  place_order(product_id: string, quantity: number) -> {order_id: string, total: number}
    description: "Place an order"
    type: http
    endpoint: "/api/orders"
    method: POST

FLOW:
  entry_point: welcome

  steps:
    - welcome
    - collect_product
    - check_stock
    - out_of_stock
    - collect_quantity
    - confirm
    - place
    - done

  global_digressions:
    - INTENT: "cancel"
      RESPOND: "Order cancelled."
      GOTO: done

  welcome:
    REASONING: false
    RESPOND: "Welcome! What product are you looking for?"
    THEN: collect_product

  collect_product:
    REASONING: false
    GATHER:
      - product_id: required
        prompt: "What is the product ID?"
    THEN: check_stock

  check_stock:
    REASONING: false
    CALL: check_inventory
      WITH:
        product_id: product_id
      AS: stockResult
    ON_RESULT:
      - IF: stockResult.available == true
        SET:
          stock_quantity = stockResult.quantity
        RESPOND: "Great news! We have {{stock_quantity}} in stock."
        THEN: collect_quantity
      - ELSE:
        THEN: out_of_stock

  out_of_stock:
    REASONING: false
    RESPOND: "Sorry, that product is currently out of stock."
    THEN: done

  collect_quantity:
    REASONING: false
    GATHER:
      - quantity: required
        type: number
        prompt: "How many would you like to order?"
    CHECK: quantity <= stock_quantity
    ON_FAIL: collect_quantity
    THEN: confirm

  confirm:
    REASONING: false
    RESPOND: "You'd like to order {{quantity}} of {{product_id}}. Confirm?"
    ACTIONS:
      - id: "yes"
        type: button
        label: "Confirm"
      - id: "no"
        type: button
        label: "Cancel"
    ON_ACTION:
      - ACTION: "yes"
        THEN: place
      - ACTION: "no"
        RESPOND: "Order cancelled."
        THEN: done

  place:
    REASONING: false
    CALL: place_order
      WITH:
        product_id: product_id
        quantity: quantity
      AS: orderResult
    ON_SUCCESS:
      RESPOND: "Order placed! Order ID: {{orderResult.order_id}}, Total: {{orderResult.total}}"
      THEN: done
    ON_FAIL:
      RESPOND: "Failed to place order. Please try again later."
      THEN: done

  done:
    REASONING: false
    RESPOND: "Thank you for using our service!"

Related articles:

Language overview — syntax rules and auto-detection
Tools — tool definitions used by CALL actions
GATHER — top-level gather field definitions
Agent declaration — GOAL used by REASONING: true steps, max_flow_iterations and model settings

​Flow structure

​Basic syntax

​Entry point

​Step list

​Step definitions

​Per-step REASONING toggle

​Reasoning step properties

​Entry guards

​Attempt limiting

​Step actions

​SAY / RESPOND

​MODEL_CONTEXT on a response

​PRESENT

​GATHER in flow steps

​Multi-field collection

​Flow gather field properties

​GATHER block properties

​CORRECTIONS

​COMPLETE_WHEN

​CALL…WITH…AS

​WITH parameters

​Localized WITH arguments

​SET

​CHECK

​CLEAR

​TRANSFORM

​LOG

​AWAIT_ATTACHMENT

​SECURE_INPUT

​Field properties

​MESSAGE_KEY and BEHAVIOR

​RESOLVE_SIP_DESTINATION

​Branching and control flow

​THEN / ON_FAIL

​ON_RESULT

​ON_RESULT branch properties

​ON_SUCCESS / ON_FAIL

​ON_INPUT

​Digressions

​Digression properties

​Global digressions

​Sub-intents

​Sub-intent properties

​Interactive actions

​Action elements

​Element types

​Buttons

​Select (dropdown)

​Input fields

​Action element properties

​Form submission

​ON_ACTION callbacks

​ON_ACTION handler properties

​Rich content

​Rich content format properties

​Voice configuration

​Per-turn endpointing

​Scoped barge-in

​Scoped streaming

​Step-level no-input (caller silence)

​Step-level error handling

​Step ON_ERROR handler properties

​Complete example

Flow structure

Basic syntax

Entry point

Step list

Step definitions

Per-step REASONING toggle

Reasoning step properties

Entry guards

Attempt limiting

Step actions

SAY / RESPOND

MODEL_CONTEXT on a response

PRESENT

GATHER in flow steps

Multi-field collection

Flow gather field properties

GATHER block properties

CORRECTIONS

COMPLETE_WHEN

CALL…WITH…AS

WITH parameters

Localized WITH arguments

SET

CHECK

CLEAR

TRANSFORM

LOG

AWAIT_ATTACHMENT

SECURE_INPUT

Field properties

MESSAGE_KEY and BEHAVIOR

RESOLVE_SIP_DESTINATION

Branching and control flow

THEN / ON_FAIL

ON_RESULT

ON_RESULT branch properties

ON_SUCCESS / ON_FAIL

ON_INPUT

Digressions

Digression properties

Global digressions

Sub-intents

Sub-intent properties

Interactive actions

Action elements

Element types

Buttons

Select (dropdown)

Input fields

Action element properties

Form submission

ON_ACTION callbacks

ON_ACTION handler properties

Rich content

Rich content format properties

Voice configuration

Per-turn endpointing

Scoped barge-in

Scoped streaming

Step-level no-input (caller silence)

Step-level error handling

Step ON_ERROR handler properties

Complete example