
Supported Field Types
Choose the type that matches the value you need.| Type | Best for | Example |
|---|---|---|
| Text | Free-form summaries or notes. | call_summary |
| Selector | One value from a known set. | call_outcome: Resolved, Escalated, Follow-up Required |
| Boolean | True or false outcomes. | customer_interested |
| Number | Numeric values. | customer_age or payment amount |
Where Results Appear
Post-call fields become operational data after the call.Call detail custom section
Custom extracted values appear on the call detail page.
CSV exports
Exports can include extracted fields for reporting.
Workflow decisions
Workflow paths can reason about call attributes when configured.
QA review
Annotations and transcript review can explain why a field was wrong.
Write Strong Extraction Fields
Use selector options for finite outcomes
Do not ask for free text when operations needs a clean report.
Extraction Problems
Field is empty
Field is empty
The transcript may not contain the fact, or the description may be too vague.
Selector returns unexpected value
Selector returns unexpected value
Use clearer allowed options and descriptions.
Boolean feels inconsistent
Boolean feels inconsistent
Define what counts as true and false.
Editing is disabled
Editing is disabled
Published versions protect live settings. Edit a draft version.
Related Reading
Post-Call Analysis Results
Review extracted fields.
Exporting Call Data
Export analysis columns.
Call Detail Page
Inspect one call.