> ## Documentation Index
> Fetch the complete documentation index at: https://www.bolna.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Call Summary

> The summary field keeps working with no code changes, now sourced from the Call Summary extraction.

<Note>
  **`summary` → No change required — 18 September 2026.** `summary` continues to work, sourced from the Call Summary extraction.
</Note>

The Call Summary extraction runs on every call and populates the flat top-level `summary` key in webhook payloads, replacing the legacy summarisation task as the source.

## No integration change

Keep reading `summary` as you do today. The field stays a string at the top level of the execution, and its CSV column name is unchanged.

## Before and after

<CodeGroup>
  ```json Before: legacy summarisation task theme={"system"}
  {
    "summary": "The customer asked to move their Tuesday appointment to Thursday and confirmed 3pm works."
  }
  ```

  ```json After: same field, new source theme={"system"}
  {
    "summary": "The customer asked to move their Tuesday appointment to Thursday and confirmed 3pm works."
  }
  ```
</CodeGroup>

Wording may differ from the legacy task for an identical call, because the prompt structure differs. Diff the two over a few days of live calls if `summary` text feeds anything downstream, such as a ticket body, a CRM note, or a report someone reads.

<Warning>
  **Calls with no user speech, from 18 September.** From 18 September 2026, on calls where the customer never speaks (voicemail, an immediate hangup, dead air), `summary` will return the string `No User Turn Detected`. Anything persisting `summary` into a record a human will read should check for it first. See [Calls with no user speech](/docs/migrating-to-extractions/overview#calls-with-no-user-speech).
</Warning>

## Removing the legacy task

This is not a dashboard toggle, and `PATCH /agent/{id}` will not do it. The task lives in the agent's `tasks` array, so only a full `PUT /v2/agent/{agent_id}` can drop it.

Email [support@bolna.ai](mailto:support@bolna.ai) and we will remove it, or send the full agent config yourself if you already manage agents that way. Leaving it in place is also fine, since it stops populating on 18 September either way.

## Other features

<CardGroup cols={3}>
  <Card title="Extraction" icon="list-check" href="/docs/migrating-to-extractions/extraction">
    `extracted_data` · flat keys
  </Card>

  <Card title="Custom Analytics" icon="sliders" href="/docs/migrating-to-extractions/custom-analytics">
    `custom_extractions`
  </Card>

  <Card title="Agent Extraction" icon="robot" href="/docs/migrating-to-extractions/agent-extraction">
    `agent_extraction`
  </Card>
</CardGroup>

## Next Steps

<CardGroup cols={3}>
  <Card title="Using Extractions" icon="list-check" href="/docs/prompting/using-extractions">
    Configure extractions in the dashboard
  </Card>

  <Card title="Dispositions API" icon="code" href="/docs/api-reference/dispositions/overview">
    Manage extractions programmatically
  </Card>

  <Card title="Webhooks" icon="webhook" href="/docs/post-call/polling-call-status-webhooks">
    Receive extraction data in real-time
  </Card>
</CardGroup>