> For the complete documentation index, see [llms.txt](https://docs.concurrence.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.concurrence.com/developer-guide/platform-api/safety/call-trace-analysis.md).

# Call Trace Analysis

Deep call understanding with emotional arcs, key decision moments, coaching recommendations, and signal-response alignment.

Call trace analysis explains why a call unfolded as it did through emotional dynamics, key decisions, coaching recommendations, counterfactuals, and interaction patterns. [Call intelligence](/developer-guide/platform-api/safety/analytics.md#call-intelligence) provides operational scores; trace analysis provides the deeper narrative.

Analysis starts on demand. The first detail request checks for a stored result and can schedule a best-effort analysis run when the call exists but no result is available. Poll while the status is `pending`. `unavailable` means the analytical read was temporarily unavailable. The list operation returns stored analyses and does not start missing analyses.

Both operations require `viewer+` access and are workspace-scoped.

## List Trace Analyses

{% openapi src="<https://platform.api-us.concurrence.com/v1/openapi.json>" path="/v1/{workspace\_id}/calls/traces" method="get" %}
<https://platform.api-us.concurrence.com/v1/openapi.json>
{% endopenapi %}

## Get Trace Analysis

The call identifier can be a call SID or call entity ID.

{% openapi src="<https://platform.api-us.concurrence.com/v1/openapi.json>" path="/v1/{workspace\_id}/calls/{call\_id}/trace-analysis" method="get" %}
<https://platform.api-us.concurrence.com/v1/openapi.json>
{% endopenapi %}


---

# 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.concurrence.com/developer-guide/platform-api/safety/call-trace-analysis.md?ask=<question>&goal=<user_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.