Skip to main content
Reporting fields tell an Agent which structured outcomes to produce after each conversation. Use them for dispositions, qualification results, appointment outcomes, escalation reasons, or other information that should be searchable and measurable.

​
Add reporting fields

  1. Open the Agent editor.
  2. Select Reporting.
  3. Add a field with a stable key, a user-facing label, and clear instructions.
  4. Choose the value type: True / False, Fixed choices, Number, or Text.
  5. Save the staged Agent and test conversations that should produce each expected outcome.
Use fixed choices when a field has a known set of valid outcomes. Use free-form text only when the answer cannot be represented reliably by a boolean, number, or controlled list.

​
Design fields for reliable reporting

  • Give each field one purpose.
  • Describe when the Agent should set the field and what evidence it should use.
  • Keep keys stable after dashboards, exports, or integrations begin using them.
  • Test negative and uncertain cases, not only the successful path.
  • Add a metric from a reporting field when you want to track the outcome over time.
For example, a lead-qualification workflow might define:
  • disposition as fixed choices such as qualified, follow_up, and not_a_fit
  • appointment_scheduled as True / False
  • estimated_value as a Number
  • follow_up_summary as Text
Reported values appear with conversation logs and can feed metrics and downstream integrations.
Reading reporting data through the API? See Logs, conversations, and reporting.