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

# Conversations

[Back to Analytics Overview](https://koreai.mintlify.site/ai-for-service/analytics/overview.md#overview-dashboards)

The Conversations page provides insights into AI Agent conversations and allows you to review performance and troubleshoot issues.

## View Conversations

1. Go to **Analytics** > **Overview** > **Conversations**.

   ![Conversations Page](https://mintcdn.com/koreai/U056wBC5nDZm8eAE/ai-for-service/analytics/overview/images/interactions-page.png?fit=max\&auto=format\&n=U056wBC5nDZm8eAE\&q=85\&s=0d4b54827aebc4d53477780beff2fe75)

2. The following details appear in a table:

   * **CUSTOMER**: The contact who initiated the conversation.

     * Direction (icon): Inbound or Outbound.
     * Language (icon): Language of the conversation.
     * Channel (icon): Voice, Chat, or Email.

     Administrators can configure the system to hide customer email IDs and phone numbers in Conversations, the Details slider, and export files. The system displays the internal User ID instead. [Learn more](https://koreai.mintlify.site/ai-for-service/contact-center/configurations/settings/configuration-settings.md#obscure-customer-info-in-analytics—interactions).

   * **ACTIONS**: Download recordings and transcripts, and copy the following identifiers:

     * User ID
     * Session ID
     * Call Conversation ID
     * Agent Conversation ID
     * X External Call ID

     ![Agent Conversation ID](https://mintcdn.com/koreai/dWMoCj7n5mhu-urg/ai-for-service/analytics/overview/images/agent-conversation-id.png?fit=max\&auto=format\&n=dWMoCj7n5mhu-urg\&q=85\&s=dea7f14fb9e99d7bae64aa30cf0debeb)

   * **Support**: The agent who handled the conversation.

   * **Start Time**: Date and time the conversation was logged. Select the arrow icon to sort newest to oldest or oldest to newest.

   * **Duration**: Duration of the inbound conversation.

   * **Agents**: Profile pictures of agents who participated, in the order they joined. Hover to see agent names.

   * **Queues**: The last queue name, with +N for additional queues. Hover to see the order in which queues were entered.

   * **Skills**: One skill shown with +N for more. Hover to see all skills associated with the conversation.

   * **Status**: Conversation statuses include:
     * **In Progress**: An ongoing conversation, displayed immediately in the Conversations tab.
     * **Error**: A disruption to an ongoing conversation resulting in an error message, typically from integrated system failures.
     * **Completed (Drop Off)**: A voice call where there was no user response and the conversation ended.
     * **Completed (User Hangup)**: A voice call where the user ended the conversation.
     * **Completed (AI Agents Hangup)**: A voice call where the AI Agent completed the task and ended the call.
     * **Completed**: A chat conversation where the AI Agent completed the task and ended the session.

   * **CSAT**: Displays the CSAT survey score. A gray icon means the survey was triggered but no response was submitted.

   * **NPS**: Displays the NPS score. A gray icon means the survey was triggered but no response was submitted.

   * **Like/Dislike**: Displays the Like or Dislike selection. A highlighted icon means the user submitted a response. A gray icon means no response was submitted.

***

## Supervisor Actions

Supervisors can view ongoing conversations and intervene directly from the Conversations tab, similar to the Monitor tab.

1. Select **Conversations** under the **Overview** section of the Analytics panel.

2. Select **⋮** under ACTIONS, then select **Supervisor View**.

   ![Supervisor Actions](https://mintcdn.com/koreai/N4xuxqRvqrsh2OGV/ai-for-service/analytics/overview/images/supervisor-actions.png?fit=max\&auto=format\&n=N4xuxqRvqrsh2OGV\&q=85\&s=976a20779cfb244226a8d88911034f21)

3. You are redirected to the Conversations section on the Monitor tab.

   ![Supervisor Actions 1](https://mintcdn.com/koreai/N4xuxqRvqrsh2OGV/ai-for-service/analytics/overview/images/supervisor-actions-1.png?fit=max\&auto=format\&n=N4xuxqRvqrsh2OGV\&q=85\&s=c7057404e7722c1a60a25e2494e1659d)

4. Select an ongoing conversation. You can perform the following actions:

   * Join Conversation
   * Assign
   * Change Queue

   ![Supervisor Actions 2](https://mintcdn.com/koreai/N4xuxqRvqrsh2OGV/ai-for-service/analytics/overview/images/supervisor-actions-2.png?fit=max\&auto=format\&n=N4xuxqRvqrsh2OGV\&q=85\&s=70b3c3de4245e0d21565eba458f96409)

***

## Search Conversations

Use the search field on the upper right side of the Conversations tab to find specific conversations. The system supports keyword search across chats, call transcripts, agent notes, and disposition notes. Common words are ignored and results are ranked by relevance by default. You can sort by Start Time when needed.

### Recent Searches

The system stores up to the last ten search phrases for the current user and displays them in the dropdown. You can select a previous phrase or enter a new one. After each search, the system saves the phrase as the most recent entry, removing duplicates and updating position.

***

## Export and Download

You can download recordings, transcripts, latency reports, and events from the dashboard.

### Prerequisite

* To enable Download Latency Report, add the following Call Control Parameters: `notifySttLatency = true, vadEnable = true, vadVendor = silero`.

### Export Conversation Data and Transcripts

1. Select the conversations and select **Export**.

2. Select **Export Conversation Data**, **Export Transcripts**, or **Export Plain Text Transcript**.

   ![Export Options](https://mintcdn.com/koreai/yKBqibMB6tqZ1i_p/ai-for-service/analytics/overview/images/conversation-export-options.png?fit=max\&auto=format\&n=yKBqibMB6tqZ1i_p\&q=85\&s=9c4b5fdfda846282d9f4ad533ba033c2)

   Or select **Download Chat Transcript** or **Download Latency Report**. These download as .csv files.

   ![Download Options](https://mintcdn.com/koreai/yKBqibMB6tqZ1i_p/ai-for-service/analytics/overview/images/actions-tab-options.png?fit=max\&auto=format\&n=yKBqibMB6tqZ1i_p\&q=85\&s=45d00cf2ba183f57f278a3182d1f053a)

   > [!NOTE]
   >
   > * Export Transcripts exports transcript files as a compressed file named `transcripts-YYYY-MM-DD-HH24-mm-SS.zip`.
   > * You can select up to 25 conversations for export as transcripts. Conversations without a transcript include a blank transcript in the export.
   > * When permissions aren't granted or are disabled, download options are inactive, and an access restriction message appears on hover.

3. A status message appears at the start of the export. The file downloads on completion.

### Preview and Download Events

1. Select the conversations, select **Export**, or select the **⋮** icon under Actions.

2. Select **Preview Events**.

   ![Preview Events](https://mintcdn.com/koreai/-jZLiNTK8_PibgLO/ai-for-service/analytics/overview/images/preview-events.png?fit=max\&auto=format\&n=-jZLiNTK8_PibgLO\&q=85\&s=23a714ce16f726122f4c276c3fa7fe9b)

3. Select **Download Events**.

   > [!NOTE]
   >
   > * The Download Events option is unavailable for conversations older than 30 days.
   > * Events are recorded periodically, so the exported document may not always reflect the complete event history. For a comprehensive record, download events after the conversation has ended.

   ![Preview Events Page](https://mintcdn.com/koreai/-jZLiNTK8_PibgLO/ai-for-service/analytics/overview/images/preview-events-page.png?fit=max\&auto=format\&n=-jZLiNTK8_PibgLO\&q=85\&s=e75bbd682f8512af495f33c9af380370)

4. A confirmation appears when the export completes. The system exports the following events and their timestamps for chat and voice conversations:

   * Routing Initiation
   * Conversation Acceptance
   * Conversation Rejection
   * Conversation Transfer
   * Transfer Failures
   * Agent Join
   * Agent Left
   * Agent Consultation
   * Skill Change
   * Disposition Updates
   * After-Call Work (ACW)
   * Conversation Closure

***

## Latency Metrics (Beta)

The Latency Metrics feature measures the duration of each stage in a voice interaction. Metrics are displayed against user messages and bot messages separately in the Transcript tab.

**User Message Metrics**

The following metrics display against each user message:

| Metric | Description | Formula |
| :- | :- | :- |
| ASR Latency | Time between when the user stops speaking and when the ASR provider returns the complete transcription. | User stops speaking → ASR returns full transcript |
| Endpointing Latency | Time between when Voice Gateway receives the final ASR transcript and when it commits the turn. | Final transcript received → Turn committed by Voice Gateway |
| Turn Detection Latency | Combined latency for detecting and processing the user's turn. | ASR Latency + Endpointing Latency |
| Endpointing Reason | The rule that causes Voice Gateway to commit the turn. See Endpointing Reasons. | — |

Example (turn detection enabled):

User stops speaking at 10:00:05.000 → ASR returns transcript at 10:00:05.450 → Turn committed at 10:00:05.851

ASR Latency = 450 ms
Endpointing Latency = 401 ms
Turn Detection Latency = 851 ms

> [!NOTE]
>
> When turn detection isn't configured, Endpointing Latency is shown as 0 — Voice Gateway commits the turn immediately on receiving the Is Final event. The Endpointing Reason is displayed as Silence threshold reached with final speech.

**Bot Message Metrics**

The following metrics display against each bot message:

| Metric | Description | Formula |
| :- | :- | :- |
| Bot Latency | Time between when Voice Gateway sends the transcription to the platform and when it receives the full bot response. | VG sends transcript → VG receives bot response |
| TTS Latency | Time between when Voice Gateway sends the bot's response text to the TTS provider and when it receives the first byte of synthesized audio (Time to First Byte). | VG sends TTS request → VG receives first audio byte |
| End-to-End Latency | Total time between when the user stops speaking and when the first audio byte plays back to the user. | ASR Latency + Endpointing Latency + Bot Latency + TTFB |

At the bottom of each bot message, the following breakdown displays:

Includes user turn: ASR x ms + Endpointing y ms

Example:

Transcript sent at 10:00:05.851 → Bot response received at 10:00:06.701 → First audio byte received at 10:00:07.101
Bot Latency = 850 ms
TTS Latency = 400 ms
End-to-End Latency = 450 + 401 + 850 + 400 = 2,101 ms

**Latency Metrics Summary**

| Metric | Against | Measures time between | Example |
| :- | :- | :- | :- |
| ASR Latency | User message | User stops speaking → ASR full transcript | 450 ms |
| Endpointing Latency | User message | Is Final received → Turn committed | 401 ms |
| Turn Detection Latency | User message | User stops speaking → Turn committed | 851 ms |
| Bot Latency | Bot message | VG sends transcript → VG receives bot response | 850 ms |
| TTS Latency | Bot message | VG sends TTS request → VG receives first audio byte | 400 ms |
| End-to-End Latency | Bot message | User stops speaking → First audio byte heard | 2,101 ms |

**Endpointing Reasons**

The Endpointing Reason identifies the rule that caused Voice Gateway to commit the turn. It displays alongside the user message metrics.

| Reason | UI Label | Description |
| :- | :- | :- |
| (Turn detection disabled) | Silence threshold reached with final speech. | The silence threshold was reached, and a final speech result was available. |
| eouRelease:smart\_turn | Audio-based turn end detected. | The turn ended early based on voice analysis indicating that the caller had finished speaking. |
| eouRelease:text\_eou | Text-based turn end detected. | The turn ended early because the text model determined that the caller's sentence was complete. |
| audioFastCommit | Early turn end detected based on voice confidence. | The turn ended early because the voice model was highly confident the caller had finished speaking and a final speech result was available. |
| finalAfterSilence | Silence threshold reached but final speech received shortly afterward. | The silence threshold was reached before the final speech result arrived; the turn ended when the final result was received shortly afterward. |
| endpoint | Silence threshold reached with final speech. | The silence threshold was reached, and a final speech result was available. |
| endpointMaxNoFinal | Silence threshold reached; turn ended with interim speech since no final speech was received. | The maximum hold time was reached without a final speech result; the available interim speech was used to complete the turn. |
| silenceCeiling | Silence limit reached beyond threshold value, and no final speech is received. | The silence limit was reached without a reliable final speech result; the detected speech may be incomplete or unreliable. |

**Enabling Latency Metrics**

To enable the Latency Metrics download, add the call control parameter `notifySttLatency` and set it to true.

***

## Edit Dispositions from the Conversations Tab

Supervisors can edit or override disposition codes after a conversation ends. Agents assign dispositions during live sessions, but supervisors can review and revise them from the Conversations tab once the session is complete.

Key highlights:

* Improved auditing and compliance
* Accurate reporting and resolution tracking
* Reduced dependency on agents for post-call updates
* Agents receive a notification when a supervisor updates a disposition

Steps to edit dispositions:

1. Select a completed interaction to revise.

2. Select the **DETAILS** tab in the Insights to Logs window.

3. Select **Edit Disposition**.

   ![Edit Disposition](https://mintcdn.com/koreai/-jZLiNTK8_PibgLO/ai-for-service/analytics/overview/images/edit-disposition-button.png?fit=max\&auto=format\&n=-jZLiNTK8_PibgLO\&q=85\&s=8b21fe333922f571ee7513fae471777b)

4. Make the necessary changes and select **Save**.

   ![Save Disposition](https://mintcdn.com/koreai/-jZLiNTK8_PibgLO/ai-for-service/analytics/overview/images/edit-disposition-pop-up.png?fit=max\&auto=format\&n=-jZLiNTK8_PibgLO\&q=85\&s=2668afeb93c3912dbc75f61ff2903ed2)

5. Select **View Logs**.

   ![View Logs](https://mintcdn.com/koreai/N4xuxqRvqrsh2OGV/ai-for-service/analytics/overview/images/view-logs.png?fit=max\&auto=format\&n=N4xuxqRvqrsh2OGV\&q=85\&s=527e250f2c8455b4a1577ff007adafe1)

   The disposition logs appear.

   ![Disposition Log Details](https://mintcdn.com/koreai/-jZLiNTK8_PibgLO/ai-for-service/analytics/overview/images/disposition-log-details.png?fit=max\&auto=format\&n=-jZLiNTK8_PibgLO\&q=85\&s=9b0d83f28a2ef9455f3d8c2f7b03b368)

***

## Filters

You can create and save multiple filters on the Conversations tab to avoid re-entering your filter selections repeatedly.

### Create Filter

1. Select the **Filter** icon.

2. Select **New Filter**.

3. Select the **Filter By** criteria.

4. Select **Save & Apply**.

5. In the pop-up, enter a name for the filter and select **Save & Apply**.

#### SmartStatus

SmartStatus is a fine-grained, business-relevant version of conversation status. It detects events such as call handling, messaging activity, inactivity, or disconnections and updates the conversation status accordingly.

![Smart Status](https://mintcdn.com/koreai/N4xuxqRvqrsh2OGV/ai-for-service/analytics/overview/images/smart-status.png?fit=max\&auto=format\&n=N4xuxqRvqrsh2OGV\&q=85\&s=a57a1474906ad864e318644951fb844a)

In the Smart Status filter, Bot conversation timer triggered displays under Terminated. Select it to list calls that ended because the maximum bot call duration was reached. Dashboard counts include these calls under the same classification.

#### Filter for Custom Tags

You can filter conversations using custom tags.

1. Select the **Filter for Custom Tags (Beta)** checkbox. The following fields appear:

   1. Tag name
   2. Predicate dropdown (CONTAINS and DOES NOT CONTAIN)
   3. AND to create a new clause

   ![Create Filters 1](https://mintcdn.com/koreai/-jZLiNTK8_PibgLO/ai-for-service/analytics/overview/images/create-filters-1.png?fit=max\&auto=format\&n=-jZLiNTK8_PibgLO\&q=85\&s=1cf134a57105c5b902ba5b715af719c0)

2. Select values for the custom tag fields and select **AND** to add another clause.

3. Select values for the second clause and select **Apply**.

   ![Create Filters 2](https://mintcdn.com/koreai/-jZLiNTK8_PibgLO/ai-for-service/analytics/overview/images/create-filters-2.png?fit=max\&auto=format\&n=-jZLiNTK8_PibgLO\&q=85\&s=63c796a215292877ea6958a396a38803)

   A confirmation appears. Select **-** to delete a clause.

   > [!NOTE]
   >
   > You can add up to 5 clauses.

Conversations matching all selected clauses appear in the results.

### Edit Filter

1. Select the **Filters** tab. The saved filter name appears.
2. Select **Edit**.
3. Make the necessary changes and select **Save & Apply**.

A confirmation message appears and the filter is updated.

### Copy Filter

1. Select **Duplicate**.
2. In the **Rename Filter** window, enter a name and select **Save**.

A confirmation appears and a copy of the filter is created.

### Mark as Default

1. Select **Mark as Default**. A confirmation message appears and the filter is set as default.

### Delete Filter

1. Select **Delete**.
2. Select **Delete** on the confirmation message.

A confirmation appears and the filter is deleted.

***

## Insights to Logs

The Insights to Logs panel shows conversation details between the contact and the agent.

Select an interaction to view the panel. The following tabs appear:

* Transcript (formerly Chat History)
* Details
* User
* Identifiers

Icons beside the Insights to Logs header show:

* Direction (inbound or outbound)
* Language
* Sentiment (Positive, Neutral, etc.)
* Channel (Voice, Chat, or Email)

![Insights to Logs](https://mintcdn.com/koreai/-jZLiNTK8_PibgLO/ai-for-service/analytics/overview/images/insights-to-logs.png?fit=max\&auto=format\&n=-jZLiNTK8_PibgLO\&q=85\&s=3e91357dbfef60ceed8c63e4035b04b0)

**Transcript**: Shows the transcript of the voice conversation, including supervisor whispers.

![Transcript Tab](https://mintcdn.com/koreai/N4xuxqRvqrsh2OGV/ai-for-service/analytics/overview/images/transcripts.png?fit=max\&auto=format\&n=N4xuxqRvqrsh2OGV\&q=85\&s=2c23dfa9027a8ff101944405cecbc835)

The Transcript tab also shows call transfer stages:

* **User transferred to Agent**: When Automation transfers the voice call to an agent.

* **User transferred to Automation**: When the agent transfers the voice call back to Automation.

  ![Transfer Stages](https://mintcdn.com/koreai/N4xuxqRvqrsh2OGV/ai-for-service/analytics/overview/images/transfer-stage.png?fit=max\&auto=format\&n=N4xuxqRvqrsh2OGV\&q=85\&s=126877d51d6203802e8d7fe28da7e5df)

* **Max no-input attempts reached**: When automation triggers the AI Agent behavior for exceeding maximum retries.

  ![Max No-Input Attempts Reached](https://mintcdn.com/koreai/N4xuxqRvqrsh2OGV/ai-for-service/analytics/overview/images/transcript-insights-to-logs.png?fit=max\&auto=format\&n=N4xuxqRvqrsh2OGV\&q=85\&s=cbd6741a6f57fb5db0ffe8f16a5075e7)

> [!NOTE]
>
> * Customer speech during hold periods isn't recorded or displayed in transcripts, regardless of who initiated the hold.
> * To redact PII in the transcript, select **De-identify PII data while presenting it to the user** from the entity node.

For email conversations, the Transcript tab displays:

* Subject at the beginning of the transcript.
* Each email entry with a View Details pop-up.
* The pop-up shows From, To, CC, and BCC fields.

  ![Email Transcript](https://mintcdn.com/koreai/-jZLiNTK8_PibgLO/ai-for-service/analytics/overview/images/email-transcript.png?fit=max\&auto=format\&n=-jZLiNTK8_PibgLO\&q=85\&s=b041833646a63e26f28638dce3997dc2)

Network interruption event:

Connection lost with Agent `<Agent Name>`: Timestamp and error type: SIP drop, WebRTC ICE failure, Agent heartbeat timeout, or Unknown.

**LLM Error Detected**: An error message appears when real-time voice APIs in Agentic apps disconnect after receiving an error.

![LLM Error](https://mintcdn.com/koreai/-jZLiNTK8_PibgLO/ai-for-service/analytics/overview/images/llm-error.png?fit=max\&auto=format\&n=-jZLiNTK8_PibgLO\&q=85\&s=be6b335b3446cdaa2a7da48f103ca79a)

**Latency Metrics for Voice Conversations**: Displays ASR, Bot, TTS, and End-to-End latency values.

![Latency Metrics](https://mintcdn.com/koreai/-jZLiNTK8_PibgLO/ai-for-service/analytics/overview/images/latency-metrics.png?fit=max\&auto=format\&n=-jZLiNTK8_PibgLO\&q=85\&s=91bf9652256b04f38877330077120312)

**Details**: Shows the following information.

| Field | Description |
| :- | :- |
| `Start` | Conversation start time. |
| `End` | Conversation end time. |
| `Agents` | All agents who participated in the call, including any agent added after a network interruption re-route. |
| `Consulting agents` | Name of the consulting agent. |
| `Joined Users` | Names of users who joined. |
| `Queues` | Queues that handled the call. |
| `Status` | Conversation status. |
| `Mode` | Mode of the conversation. |
| `Smart Status` | Detailed conversation status. |
| `Reason` | Reason for the Smart Status. |
| `Disconnecting Reason` | Event that ended the conversation. |
| `CSAT` | CSAT survey score and feedback. |
| `Disposition` | Dispositions assigned. |
| `Notes` | Notes added to the conversation (view only). |
| `Snooze Count` | Number of times the conversation was snoozed. |
| `Snooze Duration` | The duration for which the conversation was snoozed. |
| `Campaign Name` | Campaign name (applicable for campaigns). |
| `Session-level tags` | Session-level tags assigned to the conversation. |

Calls ended by the maximum bot call duration

When a call ends because the maximum bot call duration is reached, the Details tab shows these values:

`Status`: Completed
`Mode`: Bot conversation timer triggered
`Smart Status`: Terminated
`Reason`: Bot conversation timer triggered
`Disconnecting Reason`: botHangUp

Calls that end for any other reason keep their existing values. These include calls ended by the caller, a human agent, Voice Gateway, or a queue timeout.

Highlighted Notes:

Highlighted notes and their highlight state are available in the Conversation Details view. Notes highlighted in the current conversation appear with a yellow indicator. Notes highlighted in a previous conversation appear with a grey indicator.

![Details Tab](https://mintcdn.com/koreai/QPWmKyGMskaQTQCb/ai-for-service/analytics/overview/images/log-details-tab.png?fit=max\&auto=format\&n=QPWmKyGMskaQTQCb\&q=85\&s=b96eed8f90bb2f850ac1025d0cb8d435)

**User**: Shows the following information.

| Field | Description |
| :- | :- |
| `Customer Phone` | Customer's phone number |
| `Customer Name` | Customer's name |
| `Customer Email` | Customer's email address |
| `Channel User ID` | User ID of the conversation channel |
| `User ID` | Agent's user ID |
| `User-level tags` | User-level tags assigned to the conversation |

![User Tab](https://mintcdn.com/koreai/N4xuxqRvqrsh2OGV/ai-for-service/analytics/overview/images/user-insights-to-logs.png?fit=max\&auto=format\&n=N4xuxqRvqrsh2OGV\&q=85\&s=488af3c01695e70fff2aabf3bb4faae4)

**Identifiers**: Shows the following information.

| Field | Description |
| :- | :- |
| `Call ID` | The call ID (for voice calls) |
| `Session ID` | The session ID |
| `Channel User ID` | User ID of the conversation channel |
| `Call Conversation ID` | Conversation ID (for voice calls) |
| `Agent Conversation ID` | Agent conversation ID |
| `User ID` | Agent's user ID |
| `Campaign Instance ID` | Campaign instance ID (for campaigns) |

Select **Copy All** to copy all identifier details including Start Time, End Time, Caller ID, Session ID, Channel User ID, Call Conversation ID, Agent Conversation ID, User ID, Caller, and Callee.

**Delete an Attachment**

Users with the Attachment Deletion permission can delete individual attachments from a conversation. The platform removes only the selected attachment. The conversation, thread, session, and other attachments aren't affected.

A deleted attachment no longer appears in the attachment list and can't be retrieved or downloaded.

Steps to delete an attachment:

1. Open the conversation.

2. Select ⋮ and then select **Delete**.

   ![Delete Attachment](https://mintcdn.com/koreai/Afc8Lw-4Zf5WefEn/ai-for-service/analytics/overview/images/delete-attachment.png?fit=max\&auto=format\&n=Afc8Lw-4Zf5WefEn\&q=85\&s=34375c71ada6eb0c28fc0513b7929e75)

3. Check the file name and file ID, and confirm the deletion.

The attachment is deleted from the list, and a system message displays in the conversation thread. The message includes the file name where available. It remains in the thread after the attachment is removed and isn't attributed to the customer or to the user who deleted the attachment. Each deletion adds its own message to the thread.

> [!NOTE]
>
> Users without the Attachment Deletion permission don't see the Delete action. Automated attachment deletion continues to work as before.

### Call Recording

The Call Recording feature plays past conversations between a contact and an agent from the Chat History section in the Insights to Logs panel. Recordings are captured automatically and are useful for quality analysis and auditing.

Configure the following settings:

* **Play Audio**: Select the Play icon to play the audio waveform.

* **Playback Speed**: Select the speed drop-down to change playback speed.

  ![Increase Playback Speed](https://mintcdn.com/koreai/-jZLiNTK8_PibgLO/ai-for-service/analytics/overview/images/increase-playback-speed.png?fit=max\&auto=format\&n=-jZLiNTK8_PibgLO\&q=85\&s=43c6d958572a5de568f999f9a726a1b9)

* **Volume**: Adjust the slider to increase or decrease volume.

* **Mute**: Select Mute to silence the audio.

* **Rewind**: Select the Backward icon to rewind 10 seconds.

* **Forward**: Select the Forward icon to fast-forward 10 seconds.

* **Download**: Select the Download icon to download the recording as a single file or separate files.

> [!NOTE]
>
> * A delay may occur before call recordings are processed and displayed for an interaction.
> * The retention period for voice call recordings can be configured in Data Retention Period settings.
> * When the configured retention period ends, recordings are permanently deleted.
> * Customers who opt in receive an email 7 days before deletion and a confirmation email after deletion.
> * After deletion, users see: "Recording not available. It may have been deleted as per your data retention policy."
> * All actions, including retention configuration and recording deletions, are logged in the Admin Console.

* **Download as a single file**: Downloads all files in the conversation as a single file.
* **Download as separate files**: Lets you select individual files to download.

The downloaded file format is .flac across all operating systems (Windows, macOS, and Linux).

![Download as separate files](https://mintcdn.com/koreai/-jZLiNTK8_PibgLO/ai-for-service/analytics/overview/images/file-format.png?fit=max\&auto=format\&n=-jZLiNTK8_PibgLO\&q=85\&s=93ac0b7fa00eb58e7c546525491116be)

* **Duration**: The increment and countdown counters appear during playback. Total duration appears before playback begins.

  ![Duration](https://mintcdn.com/koreai/-jZLiNTK8_PibgLO/ai-for-service/analytics/overview/images/duration.png?fit=max\&auto=format\&n=-jZLiNTK8_PibgLO\&q=85\&s=ecd3011c533bfcaebdea6f762080378c)

  > [!NOTE]
  >
  > * Customer speech during hold periods isn't recorded or displayed, regardless of who initiated the hold.
  > * If Pause/Resume Call Recording is enabled, paused durations aren't recorded.

A message appears on the Transcript tab when Call Recording Control is disabled in Agent Settings.

![No Recording Available](https://mintcdn.com/koreai/-jZLiNTK8_PibgLO/ai-for-service/analytics/overview/images/recording-disabled.png?fit=max\&auto=format\&n=-jZLiNTK8_PibgLO\&q=85\&s=3041cb0c77a949c193434f1d4e611c0a)

**Recording status messages**

| State | Message |
| :- | :- |
| `call_in_progress` | Media unavailable while the call is in progress. Please recheck once the call has ended. |
| `media_in_progress` | Media generation is in progress. Please wait for a few minutes. |
| `media_generation_failed` | Media generation failed due to a technical issue. |
| `media_conversion_failed` | Unable to fetch the recording. We'll automatically retry within 24 hours, or you can click 'Retry' to try again now. If the issue persists, please try again after 15 minutes. |
| `partial_download_failed` | Unable to fetch the recording. We'll automatically retry within 24 hours, or you can click 'Retry' to try again now. If the issue persists, please try again after 15 minutes. |
| `partial_upload_failed` | Unable to fetch the recording. We'll automatically retry within 24 hours, or you can click 'Retry' to try again now. If the issue persists, please try again after 15 minutes. |
| `failed` | Media generation failed due to a technical issue. |
| `media_unavailable_short_duration` | Recording unavailable. No recording was generated because the captured audio was less than 2 seconds long. |
| `recording_disabled` | Media unavailable. Recording is disabled for this interaction. |

> [!NOTE]
>
> Ensure that the audio recording duration exceeds 2 seconds. Recordings with a duration of 2 seconds or less aren't available on the platform.
>
> Why call duration and recording duration may differ ?
>
> Call duration and recording duration are measured independently:
>
> * Call duration measures the time from when the call connects until it disconnects.
> * Recording duration measures only the period during which the recording service actively captures audio.
>
> The recording may start slightly after the call connects because the recording service requires initialization. Similarly, recording may stop before or after the call disconnects. Transfers, recording pauses and resumes, and recording-service processing can also contribute to duration differences.
>
> Therefore, a slight difference between call duration and recording duration is expected.

### Screen Recording

**Recording Storage**: Recordings are stored in an AWS S3 bucket in WebM format at 10-15 fps, up to 720p resolution, with high compression, and approximately 2 MB per minute.

Supervisors can download screen recordings, which become available approximately 10 minutes after call completion.

![Screen Recording Download](https://mintcdn.com/koreai/cu4B-YNFAocKhI_H/ai-for-service/analytics/overview/images/screen-recording-download.png?fit=max\&auto=format\&n=cu4B-YNFAocKhI_H\&q=85\&s=d939f1f54bf6fc677f897358647c0386)

| UI Text | Description |
| :- | :- |
| Loading Screen Recording | Recording is currently being fetched or initialized. |
| Generating screen recording, please wait.. | Recording is being processed and will be available soon. |
| Screen recording is available for this interaction. | Recording has been successfully generated and is ready to download. |
| Screen recording unavailable. Agent needs to install the desktop application to enable it. | Recording couldn't be captured because the agent hasn't installed the required desktop app. |
| Screen recording unavailable due to a technical issue. Please contact support. | An unexpected error occurred during recording. Contact support for resolution. |

> [!NOTE]
>
> The system uses the voice call recording retention policy; supervisors can access all recordings, while agents can access only their own recordings.

### Conversation Time Display Format

Administrators can configure Standard Timestamps or Duration Markers for call recordings. [Learn more](https://koreai.mintlify.site/ai-for-service/app-settings/advanced-settings/system-settings#conversation-time-display-format).

The system displays recordings based on the selected option.

**Standard Timestamps**: The system displays transcripts with exact date and time (for example, Fri Jun 14 2026, 4:52:31 PM) to support precise tracking.

![Standard Timestamps](https://mintcdn.com/koreai/iznC8GHkhOKnM4fV/ai-for-service/analytics/overview/images/call-recording-duration.png?fit=max\&auto=format\&n=iznC8GHkhOKnM4fV\&q=85\&s=35aa9641db5ec14ac915041096d751e1)

**Duration Markers**: The system displays elapsed time (for example, 00:01) to enable quick navigation and improve contextual understanding.

![Duration Markers](https://mintcdn.com/koreai/iznC8GHkhOKnM4fV/ai-for-service/analytics/overview/images/duration-timestamp.png?fit=max\&auto=format\&n=iznC8GHkhOKnM4fV\&q=85\&s=1b49af8af253ffbb686bedef129710c5)

### Troubleshooting

**Why can't I see my call recording?**

After every voice call, the system automatically tries to fetch the call recording from the recording server. The recording is usually available within 10 minutes. Delays or temporary issues may prevent it from appearing immediately.

**Status messages and what to do:**

| Status message | What it means | What you can do |
| :- | :- | :- |
| Generating your call recording... This may take a few minutes. | The recording server is processing the call audio. | No action needed — wait 10 minutes and refresh the page. |
| We couldn't load the call recording. Please try again. | There was a temporary issue fetching the recording. | Select **Retry** to try again. |
| Still unable to fetch the recording. Please try again after 15 minutes. | The system retried but couldn't retrieve the recording. | Wait 15 minutes and select **Retry** again. |
| We couldn't generate the call recording due to a technical issue. Please contact your administrator for assistance. | Multiple attempts including automated background jobs failed. | Contact your administrator or support team. |

**Behind the scenes:** The platform automatically attempts to fetch the recording 10 minutes after the call ends. If the recording is unavailable, users can manually retry. The system also retries automatically after 24 hours. Background jobs continue periodic attempts regardless of manual retries.

**Common reasons for delay or failure:**

* Temporary network or connectivity issues between Kore's system and the recording server.
* High server load delaying recording generation.
* The recording file hasn't been finalized or is still being processed.
* A system error or missing call metadata prevents retrieval.

**Tips:**

* Wait at least 10 minutes after the call ends before expecting the recording.
* Use **Retry** if the recording doesn't appear.
* If the issue persists beyond 24 hours, contact your administrator or raise a support ticket with the **Call ID**, **Timestamp**, and **Caller Number**.

If your call recording is still unavailable after following these steps, Contact support or your system administrator with your call details.

***

## Diagnostics

Access Diagnostics from the top-right corner of Insights to Logs.

> [!NOTE]
>
> This option is available only for voice conversations.

![Diagnostics](https://mintcdn.com/koreai/-jZLiNTK8_PibgLO/ai-for-service/analytics/overview/images/diagnostics.png?fit=max\&auto=format\&n=-jZLiNTK8_PibgLO\&q=85\&s=685a43709bcdfc5761e914f133eb3e03)

### Flow

The Flow tab provides a detailed timeline of call signaling and media flow between endpoints. It displays the sequence of SIP messages and RTCP packets exchanged during a call, allowing agents and supervisors to track the complete communication flow and troubleshoot connection issues.

![Flow Tab](https://mintcdn.com/koreai/-jZLiNTK8_PibgLO/ai-for-service/analytics/overview/images/flow-tab.png?fit=max\&auto=format\&n=-jZLiNTK8_PibgLO\&q=85\&s=f50d679e28062cfae2ffe3e226c44a25)

The top row displays the IP addresses of all endpoints involved in the communication.

**SIP Message Flow**

The interface shows SIP signaling messages exchanged between endpoints:

1. **INVITE** - Direction: 50.19.12.248 to 172.31.11.64, Port: 5060 → 5060
2. **100 (Trying)** - Direction: 172.31.11.64 to 50.19.12.248, Port: 5060 ← 5060
3. **200 (OK)** - Direction: 172.31.11.64 to 50.19.12.248, Port: 5060 ← 5060
4. **ACK** - Direction: 50.19.12.248 to 172.31.11.64, Port: 5060 → 5060

The interface also shows RTCP media packets exchanged between endpoints:

1. **RTCP (First packet)** - Direction: 172.31.11.62 to 172.31.11.64, Port: 5060 → 5060
2. **RTCP (Second packet)** - Direction: 172.31.11.62 to 172.31.11.64, Port: 5060 → 5060

**How to use the Flow tab:**

1. **Track Call Setup**: Follow the INVITE, 100 Trying, 200 OK, and ACK sequence to verify proper call establishment.
2. **Analyze Response Times**: Use timestamps to identify delays in message processing.
3. **Monitor Media Flow**: Review RTCP packets to confirm media is flowing properly.
4. **Identify Issues**: Look for missing messages or unexpected responses indicating connection problems.
5. **Export Data**: Use the export options to save the communication flow for further analysis.

### QoS (Quality of Service)

The QoS tab provides detailed network metrics for call monitoring and troubleshooting.

![QoS Tab](https://mintcdn.com/koreai/-jZLiNTK8_PibgLO/ai-for-service/analytics/overview/images/qos-tab.png?fit=max\&auto=format\&n=-jZLiNTK8_PibgLO\&q=85\&s=63cab4b8578c0c8fa5d09212d815afc3)

**Packets**

| Metric | Description |
| :- | :- |
| `Min. Packets` | Minimum number of packets transmitted (320) |
| `Avg. Packets` | Average number of packets transmitted (249.25) |
| `Max. Packets` | Maximum number of packets transmitted (602) |

**Octets**

| Metric | Description |
| :- | :- |
| `Min. Octets` | Minimum number of octets/bytes transmitted (238047) |
| `Avg. Octets` | Average number of octets/bytes transmitted (238047) |
| `Max. Octets` | Maximum number of octets/bytes transmitted (802234) |

**Highest\_Seq\_No**

| Metric | Description |
| :- | :- |
| `Min. Highest_Seq_No` | Minimum sequence number (2) |
| `Avg. Highest_Seq_No` | Average sequence number (249625) |
| `Max. Highest_Seq_No` | Maximum sequence number (435756) |

**IA (Inter Arrival) Jitter**

| Metric | Description |
| :- | :- |
| `Min. IA Jitter` | Minimum inter-arrival jitter (0) |
| `Avg. IA Jitter` | Average inter-arrival jitter (0) |
| `Max. IA Jitter` | Maximum inter-arrival jitter (4) |

**LSR (Last Sender Report)**

| Metric | Description |
| :- | :- |
| `Min. LSR` | Minimum last sender report (0) |
| `Avg. LSR` | Average last sender report (3445503.34) |
| `Max. LSR` | Maximum last sender report (3445503.34) |

**MOS (Mean Opinion Score)**

| Metric | Description |
| :- | :- |
| `Min. MOS` | Minimum Mean Opinion Score (4.34) |
| `Avg. MOS` | Average Mean Opinion Score (2.32) |
| `Max. MOS` | Maximum Mean Opinion Score (5.74) |

**Packets\_Lost**

| Metric | Description |
| :- | :- |
| `Min. Packets_Lost` | Minimum number of lost packets (0) |
| `Avg. Packets_Lost` | Average number of lost packets (0) |
| `Max. Packets_Lost` | Maximum number of lost packets (1) |

The interface displays IP connection information in expandable rows showing source and destination IP addresses. The bottom bar chart visualizes call metrics over time, with timestamps on the X-axis and metric values from 0 to 100 on the Y-axis.

### Agent Participation and Call Diagnostics

The Agents tab provides a per-agent view of participation and call quality metrics for a specific interaction.

It helps to:

* Identify which agents joined the interaction
* View join and exit timestamps
* Understand how the call ended
* Analyze call quality per agent

  ![Agents Tab](https://mintcdn.com/koreai/WTT72SOeQtn-33zP/ai-for-service/analytics/overview/images/agent-diagnostics.png?fit=max\&auto=format\&n=WTT72SOeQtn-33zP\&q=85\&s=4bd54732b4649b43b3cc07edd56584b6)

**What Each Section Represents**

Each section represents a single agent join event.

The system creates a record only when an agent:

* Accepts a call invitation (inbound or consult)
* Joins the interaction (including supervisor join)

A record isn't created for:

* Routing attempts
* Ringing duration
* Rejected invitations
* Supervisor listen/whisper sessions

If an agent leaves and rejoins, multiple rows appear-one per join instance.

**Field Descriptions**

**Agent Details**

* Agent Name-The participating agent
* Status-Indicates whether the agent has left the interaction
* Start Time-When the agent accepted and joined the call
* End Time-When the agent exited the call

The time between Start and End reflects the agent's actual handling duration.

**Call Exit Information**

* Call Exit Reason-High-level termination status (for example, Terminated).
* Call Exit Description-Specific reason (for example, Agent Hangup, Customer Hangup).

These fields help determine how the agent session ended.

**Call Quality Metrics (Per Agent Session)**

Quality metrics are calculated separately for each agent's participation instance:

* **MOS (Min, Max, Avg)**-Indicates perceived audio quality (1 = poor, 5 = excellent).
* **Jitter (Min, Max, Avg)**-Measures variation in packet timing (higher values may affect audio clarity).
* **Packets Lost (Min, Max, Avg)**-Indicates lost audio packets during the session.

These metrics reflect only the agent's session duration, not the entire call.

> [!NOTE]
>
> * The view reflects actual joined sessions only, not routing attempts.
> * If an agent appears multiple times, it indicates multiple join instances.

### Network Interruption Re-routing

When a call is re-routed, the Agents tab lists the original agent and the new agent as separate rows with individual timestamps and call quality metrics.

| Agent | Call Exit Reason |
| :- | :- |
| Original agent | Network Interruption |
| New agent | Standard exit reason |

### Export

You can export the following reports from the Diagnostics panel:

* Export PCAP
* Export TEXT

![Export Reports](https://mintcdn.com/koreai/-jZLiNTK8_PibgLO/ai-for-service/analytics/overview/images/export.png?fit=max\&auto=format\&n=-jZLiNTK8_PibgLO\&q=85\&s=ca70392b6a53f4ed8ed3c45aab6631a4)

***


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.