> ## Documentation Index
> Fetch the complete documentation index at: https://dialnexa.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# DialNexa Post-Call Analysis Results
> Review DialNexa post-call analysis results, custom fields, extraction values, field types, summaries, sentiment, and exports.
DialNexa post-call analysis results are structured values extracted from a completed call. The extraction fields themselves are defined per agent in [Post-Call Analysis settings](/agent-settings/post-call-analysis); this page is where you review the extracted values. The call detail page can show custom fields such as text, selector, boolean, number, and DateTime outputs, while exports can turn those values into report columns.
Post-call analysis is how a messy conversation becomes a usable row in a report.
## Result Types
Field type controls how users should read the value.
| Type | Example result | How to review |
| -------- | ---------------------------------------- | ------------------------------------------------------------------------------------------ |
| TEXT | Call summary or reason for calling. | Check whether the text reflects transcript evidence. |
| SELECTOR | Resolved, Escalated, Follow-up Required. | Confirm it selected one allowed outcome. |
| BOOLEAN | customer\_interested true or false. | Confirm the rule for true and false is clear. |
| NUMBER | customer age or amount. | Check formatting and units. |
| DATETIME | `2026-06-30T10:30:00+05:30`. | Confirm the timezone and caller evidence match the expected appointment or follow-up time. |
## DateTime Display On Call Detail
DateTime fields are stored as ISO 8601 values with timezone information so automations and exports can process them consistently. On the call detail page, DialNexa can use the field type metadata to render DateTime values as a readable date and time with a calendar-style display.
Custom post-call fields follow the configured field order when that metadata is available. If a DateTime value looks wrong, review the agent timezone, field description, transcript evidence, and raw exported value before changing the extractor.
## Where Result Quality Comes From
Bad extraction can be caused upstream.
Clear field descriptions produce better extraction.
If the transcript missed the fact, extraction may miss it too.
The agent must ask for the data you want extracted.
Exports carry extracted values into external reporting.
## Why A Field Looks Wrong
The extractor cannot invent a value safely.
Rewrite the description around evidence and allowed output.
Check the version attached to the call before editing the current draft.
Some system fields such as sentiment are treated separately from custom extracted values.
The call detail page formats recognized DateTime fields for reading, while exports and automations should keep the ISO 8601 value with timezone information.
## Related Reading
Define fields.
Use fields in CSVs.
Understand stored output.