> For the complete documentation index, see [llms.txt](https://docs.dapta.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dapta.ai/ai-voice-agents/analyze-your-calls/post-call-analysis-call-analysis-flow.md).
# Post Call Analysis – Call Analysis Flow
This section allows you to configure how calls made by the AI agent will be analyzed using the flows previously created in Flow Studio.
{% hint style="info" %}
If your agent shows **After-call destinations** on the **Call Analysis** tab, choose the flow there as a **Dapta flow** destination instead. See [Destinations](/ai-voice-agents/analyze-your-calls/post-call-analysis-destinations.md).
{% endhint %}
#### Select Call Analysis Flow
Click on “Select Call Analysis Flow”
You will only see flows that meet the specific criteria for call analysis. If your flow doesn’t appear in the list, it’s because it doesn’t meet the following conditions:
* The flow must have a “Trigger” type that receives all parameters through the body of the request.
* The flow must respond with text, since LLM models can only process text-based responses.
* Only one analysis flow can be selected in this feature.
Once the flow is selected, you’ll see the flow’s URL and API Key already filled in under the “Call Analysis Flow” field.
⚠️ Warning:
If you change the name of a flow, you must update the corresponding webhook URL.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.dapta.ai/ai-voice-agents/analyze-your-calls/post-call-analysis-call-analysis-flow.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
