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

# Analyze Completed Calls

> Access the Call Inspector to analyze transcripts, audio recordings, LLM interactions, tool executions, and performance metrics for any completed call.

Analyze completed calls in detail. The Call Inspector shows transcripts, audio recordings, timeline events, LLM prompts/responses, tool executions, and latency breakdowns for every conversation.

**What you'll learn:** Accessing the inspector, understanding sections, and navigating to detailed analysis.

<Note>
  Screenshots may differ from current UI version.
</Note>

***

## Access the Call Inspector

<Tabs>
  <Tab title="From Calls page">
    1. Go to **Calls** in the sidebar
    2. Select the **Past Calls** tab
    3. Find your call in the list
    4. Click the **Inspect** button
    5. Inspector opens in a new tab
  </Tab>

  <Tab title="From Dashboard">
    1. View the **Recent Calls** section on your dashboard
    2. Click any completed call row
    3. Inspector opens in a new tab
  </Tab>

  <Tab title="From Agent details">
    1. Go to **Agents** → Select your agent
    2. Scroll to the call history section
    3. Click **Inspect** for any completed call
  </Tab>

  <Tab title="From API">
    <Accordion title="API example: Get inspector URL">
      ```javascript theme={"theme":{"light":"github-light","dark":"github-dark"}}
      // Get inspector URL from call results
      const results = await fetch('https://blackbox.dasha.ai/api/v1/callresults/search', {
        method: 'POST',
        headers: {
          'Authorization': 'Bearer YOUR_API_KEY',
          'Content-Type': 'application/json'
        },
        body: JSON.stringify({
          callIds: ['your-call-id']
        })
      }).then(r => r.json());

      console.log('Inspector URL:', results.results[0].inspectorUrl);
      ```
    </Accordion>
  </Tab>
</Tabs>

**The Call Inspector is only available for completed calls.** Calls in Pending, Queued, or Running status don't have inspector data until they complete.

***

## Inspector sections

| Section        | Contents                          | Use case              | Learn more                                           |
| -------------- | --------------------------------- | --------------------- | ---------------------------------------------------- |
| **Overview**   | Call metadata, status, duration   | Quick context         | Below                                                |
| **Transcript** | Full conversation with timestamps | Conversation review   | —                                                    |
| **Audio**      | Recording playback                | Voice quality         | [Common Issues](/docs/troubleshooting/common-issues) |
| **LLM**        | Prompts, responses, tokens        | Model debugging       | [Common Issues](/docs/troubleshooting/common-issues) |
| **Tools**      | Function calls and responses      | Integration debugging | [Common Issues](/docs/troubleshooting/common-issues) |
| **Timeline**   | Chronological events              | Latency analysis      | —                                                    |

***

## Call overview

The inspector header displays key call metadata at a glance.

### Header information

| Field         | Description                    | API field         |
| ------------- | ------------------------------ | ----------------- |
| **Call ID**   | Unique identifier (UUID)       | `callId`          |
| **Status**    | Completed, Failed, or Canceled | `callStatus`      |
| **Agent**     | Agent ID and name              | `agentId`         |
| **Duration**  | Total conversation length      | `durationSeconds` |
| **Endpoint**  | Phone number or "web"          | `endpoint`        |
| **Call Type** | Connection type                | `callType`        |

### Call type values

| Type           | API value       | Description         |
| -------------- | --------------- | ------------------- |
| Inbound phone  | `InboundAudio`  | Incoming phone call |
| Outbound phone | `OutboundAudio` | Outgoing phone call |
| Web voice      | `WebCall`       | Browser WebRTC call |
| Web chat       | `Chat`          | Text conversation   |

### Timestamps

| Timestamp     | Meaning                     |
| ------------- | --------------------------- |
| **Created**   | When the call was scheduled |
| **Started**   | When the conversation began |
| **Completed** | When the call ended         |

### Custom data

Any `additionalData` passed during call creation appears as formatted JSON:

<Accordion title="Example: Call overview with custom data">
  ```json theme={"theme":{"light":"github-light","dark":"github-dark"}}
  {
    "callId": "660e8400-e29b-41d4-a716-446655440001",
    "status": "Completed",
    "duration": "00:03:45",
    "additionalData": {
      "customerId": "cust_789",
      "orderNumber": "ORD-12345"
    }
  }
  ```
</Accordion>

***

## Quick analysis

### Check conversation quality

1. Open the **Transcript** section
2. Scan for red flags: repetition, off-topic responses, user frustration
3. Listen to audio for voice quality issues
4. Review LLM logs if responses seem wrong

→ [Common Issues](/docs/troubleshooting/common-issues)

### Check performance

1. Open the **Timeline** section
2. Look at latency breakdown: STT, LLM, TTS
3. Identify the slowest component
4. Compare against targets (under 2s total)

→ [Common Issues](/docs/troubleshooting/common-issues)

### Debug failed calls

1. Check **Status** in the header
2. Look for error messages in system events
3. Review LLM logs for API errors
4. Check tool executions for failures

→ [Common Issues](/docs/troubleshooting/common-issues)

***

## Best practices

### During testing

* Review 5-10 test calls before enabling an agent for production
* Verify all conversation paths work as expected
* Check that tool executions succeed
* Confirm latencies are within acceptable ranges

### In production

* Sample 5-10% of calls randomly for quality review
* Review all failed calls within 24 hours
* Track performance trends over time
* Monitor tool success rates

### Data privacy

* Redact PII before sharing transcripts externally
* Comply with call recording consent laws in your jurisdiction
* Implement data retention policies
* Secure access to recordings with proper authentication

***

## What's next

<CardGroup cols={2}>
  <Card title="Call History" icon="clock-rotate-left" href="/docs/monitor/call-history">
    View and filter past calls
  </Card>

  <Card title="Troubleshooting" icon="bug" href="/docs/troubleshooting/common-issues">
    Common issues and solutions
  </Card>

  <Card title="Common Issues" icon="circle-exclamation" href="/docs/troubleshooting/common-issues">
    Solutions for frequent problems
  </Card>

  <Card title="Concurrency Monitoring" icon="chart-bar" href="/docs/monitor/concurrency-monitoring">
    Monitor active calls and capacity
  </Card>
</CardGroup>