Skip to main content

Define conversation results

The Conversation result section defines, in YAML, the data the agent extracts from each conversation. This page covers the field schema and where collected values show up.

The Conversation result section defines, in YAML, which data the agent extracts from each conversation — names, contact details, intents, or any custom fields. The agent fills the fields from what the customer says; it does not ask for the data unless your task or workflow tells it to.

- field_description: The name of the human
field_name: HumanFullName
field_title: Name
field_type: str
kind: FormInfoField
- field_description: Human's contact phone number
field_name: HumanPhoneNumber
field_title: Phone
kind: FormInfoField
- field_name: Budget
field_description: When human speaks about budget
field_type: Literal['500', '1000', '2000']
kind: FormInfoField
ParameterPurpose
field_nameInternal field identifier used in configuration, logic, and integrations.
field_descriptionWhat the agent should collect — describe it the way customers phrase it.
field_titleOptional human-readable label shown in the interface and reports.
field_typeExpected value type, such as str, or Literal[...] for a fixed set of allowed values.
kindAlways FormInfoField.

Use a Literal type when the value must come from a fixed list — free-text answers vary and are harder to aggregate. The ? icon in the section header opens the formatting reference.

Collected values appear as session results in three places: the Parameters & results panel on the Sessions screen, the customer's profile in 360 View, and the Results tab in the Playground while you test.

This is the same data that Simple mode edits as toggles and custom fields on its Conversation Results tab — Advanced mode exposes the underlying YAML.

Was this article helpful?