Post-Call Analysis Data Types and Allowed Values

Last updated: August 10, 2026

Choose Text, Number, or Boolean when you create a Post-Call Analysis prompt. The data type controls the expected output and cannot be changed after the prompt is created.

Supported Data Types

Data type

Use for

Example instruction

Example output

Text

Categories, summaries, names, or extracted details

Return one qualification category.

Qualified

Number

Scores, counts, quantities, or amounts

Score buying intent from 1 to 10.

8

Boolean

A strict true-or-false decision

Return true if the visitor asked for pricing.

true

Dates and timeframes are not separate data types. Capture them as Text unless your downstream workflow explicitly expects a numeric value.

Use Permitted Values with Text

Text prompts can include permitted values. Use them when the result must come from a fixed list for filtering, routing, or CRM mapping.

Example values for Qualification Status:

  • Qualified

  • Not Qualified

  • Unknown

Permitted values are not available for Number or Boolean prompts. For those types, define the expected numeric range or true/false condition in the instruction.

Write Type-Specific Instructions

Every instruction should identify the context to evaluate, the required output, and the missing-data behavior.

  • Text: Return one permitted value based on @Conversation Data. Return Unknown when evidence is insufficient.

  • Number: Return an integer from 1 to 10 based on buying-intent signals in @Conversation Data. Return 0 when no signal is present.

  • Boolean: Return true only when the visitor explicitly asks to schedule a meeting; otherwise return false.

Use Add Context or type @ to reference the available Conversation or Visitor data scopes.

Creation Rules

  • A prompt name is required and can contain up to 40 characters.

  • The instruction is required.

  • Prompt names must be unique for the agent.

  • The prompt's data type is fixed after creation.

  • The workspace response controls the maximum active prompts; the current client default is 10.

Verify the Output

  1. Save the prompt and confirm it appears in Post Call Analysis.

  2. Run a controlled conversation that should produce a known result.

  3. End the conversation and review the extracted value.

  4. Confirm the output matches the selected data type and any permitted values.

  5. Repeat with missing or ambiguous input to verify the fallback behavior.

Related Articles