> ## 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

> Configure DialNexa post-call analysis fields for text, selector, boolean, number, and DateTime extraction from completed calls.

DialNexa post-call analysis extracts structured fields from a completed call. Define the extraction fields here; review the extracted values per call in [Post-Call Analysis Results](/monitoring/post-call-analysis-results). Users can add, edit, delete, and reorder text, selector, boolean, number, and DateTime fields so Call History and exports show outcomes such as summary, call result, customer interest, age, qualification, callback time, or next step.

<img src="https://mintcdn.com/dialnexa/0efoAN-6So4r-6NC/images/documentation/screenshots/agent-post-call-analysis-panel.png?fit=max&auto=format&n=0efoAN-6So4r-6NC&q=85&s=c30894c6121164d5853c88d755cbb612" alt="DialNexa Post-Call Analysis settings panel showing a custom Demo Date and Time field with edit, delete, and add controls." style={{ width: '100%', maxWidth: '800px', margin: '8px 0 24px', border: '1px solid #e5e7eb', borderRadius: '6px' }} width="678" height="1498" data-path="images/documentation/screenshots/agent-post-call-analysis-panel.png" />

<Tip>
  If operations needs a column later, define the field before the campaign. Future-you has enough to do.
</Tip>

## 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                                             |
| DateTime | Callback, appointment, renewal, or follow-up timing. | `callback_datetime` returned as UTC ISO 8601, such as `2024-06-17T10:30:00Z` |

Use DateTime when another system or a workflow needs a schedulable time. In the field description, ask for the value in UTC ISO 8601 format so the extracted result can be parsed consistently.

<img src="https://mintcdn.com/dialnexa/HOnVBqIHk6o8-0eg/images/documentation/screenshots/agent-post-call-analysis-datetime-menu.png?fit=max&auto=format&n=HOnVBqIHk6o8-0eg&q=85&s=43a37b425f61366f7ff0e2639b5f1140" alt="DialNexa Post Call Analysis add menu showing Text, Selector, Boolean, Number, and Date and Time field types." style={{ width: '100%', maxWidth: '520px', margin: '8px 0 24px', border: '1px solid #e5e7eb', borderRadius: '6px' }} width="590" height="1294" data-path="images/documentation/screenshots/agent-post-call-analysis-datetime-menu.png" />

## Where Results Appear

Post-call fields become operational data after the call.

<CardGroup cols={2}>
  <Card title="Call detail custom section" icon="panel-right" href="/monitoring/post-call-analysis-results">
    Custom extracted values appear on the call detail page.
  </Card>

  <Card title="CSV exports" icon="download" href="/monitoring/exporting-call-data">
    Exports can include extracted fields for reporting.
  </Card>

  <Card title="Workflow decisions" icon="workflow" href="/workflows/lead-variables-and-call-attributes">
    Workflow paths can reason about call attributes when configured.
  </Card>

  <Card title="QA review" icon="flag" href="/monitoring/annotations-and-call-feedback">
    Annotations and transcript review can explain why a field was wrong.
  </Card>
</CardGroup>

## Post-Call Extraction LLM

The Post Call Analysis panel includes a model settings control for the LLM used by post-call extraction. This is separate from the live conversation model so teams can tune completed-call extraction without changing how the agent speaks during the call.

<img src="https://mintcdn.com/dialnexa/deSh6R4VHhcuER-T/images/documentation/screenshots/post-call-llm-settings.png?fit=max&auto=format&n=deSh6R4VHhcuER-T&q=85&s=7b600d6f9fe4a1774c281d6020205467" alt="DialNexa Post Call Analysis LLM settings popover showing GPT model choices for post-call extraction." style={{ width: '100%', maxWidth: '520px', margin: '8px 0 24px', border: '1px solid #e5e7eb', borderRadius: '6px' }} width="614" height="870" data-path="images/documentation/screenshots/post-call-llm-settings.png" />

| Setting                   | Behavior                                                                                                            |
| ------------------------- | ------------------------------------------------------------------------------------------------------------------- |
| Default                   | DialNexa selects GPT-4.1 when it is available.                                                                      |
| Allowed dashboard choices | GPT-5.4 Mini, GPT-5.4 Nano, GPT-4.1, GPT-4.1 Nano, and GPT-4o Mini.                                                 |
| Published versions        | Published versions can disable edits. Update a draft version before changing extraction fields or extraction model. |
| API field                 | Integrations can set `post_call_analysis_llm_id` when creating or updating agents.                                  |

Use a stronger extraction model when the transcript is long, the fields depend on reasoning across multiple turns, or selector values need careful evidence. Keep the live model and post-call extraction model aligned only when you want both tasks to share the same cost and behavior profile.

## Write Strong Extraction Fields

<Steps>
  <Step title="Name the field like a column">
    Use names that will make sense in exports.
  </Step>

  <Step title="Describe the evidence">
    Tell the extractor exactly what part of the conversation proves the value.
  </Step>

  <Step title="Use selector options for finite outcomes">
    Do not ask for free text when operations needs a clean report.
  </Step>

  <Step title="Use DateTime for schedulable callbacks">
    Ask for UTC ISO 8601 output when the caller gives a callback time, appointment time, or other follow-up date.
  </Step>

  <Step title="Test on real calls">
    Check whether the transcript contains the evidence needed to extract the field.
  </Step>
</Steps>

## Extraction Problems

<AccordionGroup>
  <Accordion title="Field is empty">
    The transcript may not contain the fact, or the description may be too vague.
  </Accordion>

  <Accordion title="Selector returns unexpected value">
    Use clearer allowed options and descriptions.
  </Accordion>

  <Accordion title="Boolean feels inconsistent">
    Define what counts as true and false.
  </Accordion>

  <Accordion title="Callback time cannot schedule a workflow">
    Use the DateTime field type and describe the expected UTC ISO 8601 output. Workflow Time nodes should point at a DateTime PCA field.
  </Accordion>

  <Accordion title="Editing is disabled">
    Published versions protect live settings. Edit a draft version.
  </Accordion>
</AccordionGroup>

## Related Reading

<CardGroup cols={2}>
  <Card title="Post-Call Analysis Results" icon="list-checks" href="/monitoring/post-call-analysis-results">
    Review extracted fields.
  </Card>

  <Card title="Exporting Call Data" icon="download" href="/monitoring/exporting-call-data">
    Export analysis columns.
  </Card>

  <Card title="Call Detail Page" icon="panel-right" href="/monitoring/call-detail-page">
    Inspect one call.
  </Card>
</CardGroup>
