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

# Review calls and chats

> Investigate calls and chats with Retell AI Conductor. Filter conversations, inspect transcripts and tool calls, and compare failures to find agent improvements.

Ask Conductor to find and investigate calls or chats, compare their outcomes, and suggest agent improvements. You can describe the conversations you want or select them directly from history.

## When to use it

Use Conductor when a conversation failed, a customer did not get an answer, or you want to understand a pattern across several sessions.

For example: "Review chats where the customer’s question went unanswered and suggest improvements."

## Find and review conversations

<Steps>
  <Step title="Choose the conversations">
    Open **Call History** or **Chat History**, click **Select**, and check the rows. Open Conductor to see the selected conversations as context chips. You can also use **Add context** (+), provide a session ID, or describe a set of conversations.

    <Frame caption="Select the history rows you want Conductor to investigate.">
      <img src="https://mintcdn.com/retellai/hUHAB8rIIpPsqz8F/images/conductor/conductor-history-multi-select.png?fit=max&auto=format&n=hUHAB8rIIpPsqz8F&q=85&s=3916891c6d4525de82e288a5c4f2cf21" alt="Call History with two checked rows and a 2 selected count." style={{ maxHeight: 560 }} width="900" height="242" data-path="images/conductor/conductor-history-multi-select.png" />
    </Frame>
  </Step>

  <Step title="Describe the problem">
    Ask what went wrong or what the selected conversations have in common. Include the outcome you expected, such as confirming a booking or answering a delivery question.
  </Step>

  <Step title="Inspect the evidence">
    Ask Conductor to examine transcripts, outcomes, analysis, tool calls, or node transitions. Use inline call or chat links in the reply to open individual session details.
  </Step>
</Steps>

<Frame caption="Two selected calls appear as context for a question about shared patterns.">
  <img src="https://mintcdn.com/retellai/hUHAB8rIIpPsqz8F/images/conductor/conductor-history-context.png?fit=max&auto=format&n=hUHAB8rIIpPsqz8F&q=85&s=d08da59423751b2ed0c2ef16ec376f29" alt="Conductor message box with two call context chips above the draft question What do these calls have in common?" style={{ maxHeight: 560 }} width="564" height="164" data-path="images/conductor/conductor-history-context.png" />
</Frame>

For the selection steps, see [Select calls and chats from history](/conductor/overview#select-calls-and-chats-from-history).

## Open filtered results

Ask, "Show unsuccessful calls from last week," or "Find unsuccessful chats for this agent." Conductor can return a navigation card that opens **Call History** or **Chat History** with the requested filters. Check the filters after opening the results.

See [Call and chat history](/features/session-history) for the available filters and session details.

## Turn findings into improvements

Ask Conductor to propose a targeted fix, then [review the agent changes](/conductor/build-and-refine#review-and-apply-changes). For example: "Update the agent to explain the next step when the booking function returns no available slots."

Use [Testing](/conductor/test-and-improve) to check the change before deploying it. If the issue comes from a QA evaluation, [inspect the QA result](/conductor/ai-qa) alongside the transcript.