Back to Analytics OverviewThe Conversations page provides insights into AI Agent conversations and allows you to review performance and troubleshoot issues.
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.
ACTIONS: Download recordings and transcripts, and copy the following identifiers:
User ID
Session ID
Call Conversation ID
Agent Conversation ID
X External Call ID
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.
Use the search field on the top right 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.
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.
Select the conversations, click Export, or click the ⋮ icon under Actions.
Select Preview Events.
Select Download Events.
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.
A confirmation appears when the export completes.The system exports the following events and their timestamps for chat and voice conversations:
The Latency Metrics feature measures the duration of each stage in a voice interaction: ASR, bot processing, TTS, and end-to-end response time.
ASR Latency: Time between when the user stops speaking and when the ASR provider returns the full transcription.Formula: ASR Latency = User stops speaking → ASR returns full transcriptExample: User stops speaking at 10:00:05.000; ASR returns transcript at 10:00:05.450 → ASR Latency = 450 ms
Bot Latency: Time between when the Voice Gateway (VG) sends the transcription to the platform and when VG receives the full response.Formula: Bot Latency = VG sends transcript → VG receives bot responseExample: Transcript sent at 10:00:05.450; bot response received at 10:00:06.300 → Bot Latency = 850 ms
TTS Latency: Time between when VG sends the bot’s response text to the TTS provider and when VG receives the first byte of synthesized audio (Time to First Byte). Total TTS audio-generation time is not shown.Formula: TTS Latency = VG sends TTS request → VG receives first audio byteExample: TTS request sent at 10:00:06.300; first audio byte received at 10:00:06.700 → TTS Latency = 400 ms
End-to-End Latency: Total time between when the user stops speaking and when the first audio byte plays back to the user.Formula: End-to-End Latency = User stops speaking → First audio byte heardExample: User stops speaking at 10:00:05.000; first audio byte heard at 10:00:06.700 → End-to-End Latency = 1.7 seconds
Metric
Measures Time Between
Represents
Example
ASR Latency
User stops speaking → ASR full transcript
Speed of speech recognition
450 ms
Bot Latency
VG sends transcript → VG gets bot response
Bot processing and platform delays
850 ms
TTS Latency
VG sends TTS request → VG receives first audio byte
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:
Select a completed interaction to revise.
Select the DETAILS tab in the Insights to Logs window.
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.
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)
Transcript: Shows the transcript of the voice conversation, including supervisor whispers.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.
Max no-input attempts reached: When automation triggers the AI Agent behavior for exceeding maximum retries.
Customer speech during hold periods is not 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.
LLM Error Detected: An error message appears when real-time voice APIs in Agentic apps disconnect after receiving an error.Latency Metrics for Voice Conversations: Displays ASR, Bot, TTS, and End-to-End latency values.Details: Shows the following information.
Field
Description
Start
Conversation start time
End
Conversation end time
Agents
Name of the agent
Consulting agents
Name of the consulting agent
Joined Users
Names of users who joined
Queues
Queues that handled the call
Status
Conversation status (SmartStatus)
Mode
Mode of 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
Duration the conversation was snoozed
Campaign Name
Campaign name (applicable for campaigns)
Session-level tags
Session-level tags assigned to the conversation
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
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.
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.
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.
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).
Duration: The increment and countdown counters appear during playback. Total duration appears before playback begins.
Customer speech during hold periods is not recorded or displayed, regardless of who initiated the hold.
If Pause/Resume Call Recording is enabled, paused durations are not recorded.
A message appears on the Transcript tab when Call Recording Control is disabled in Agent Settings.Recording status messages:
State
Message
failed
Media generation failed due to a technical issue. Please contact your administrator.
media_unavailable
No audio recording found on the server. Please contact your administrator.
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.
partial_download_failed
Unable to fetch the recording. Please click the button below to retry.
partial_upload_failed
Unable to fetch the recording. Please click the button below to retry.
partial_failed
Unable to fetch the recording. Please click the button below to retry.
fetching_in_progress
Generating your call recording… This may take a few minutes. Please wait.
initial_fetch_failed
We couldn’t load the call recording. Please try again.
retry_failed
Still unable to fetch the recording. Please try again after 15 minutes.
24hr_retry_failed
We couldn’t generate the call recording due to a technical issue. Please contact your administrator for assistance.
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 has not 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 does not 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.
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.The top row displays the IP addresses of all endpoints involved in the communication.SIP Message FlowThe interface shows SIP signaling messages exchanged between endpoints:
INVITE – Direction: 50.19.12.248 to 172.31.11.64, Port: 5060 → 5060
The QoS tab provides detailed network metrics for call monitoring and troubleshooting.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.
The Agents tab provides a per-agent view of participation and call quality metrics for a specific interaction. It helps identify which agents joined, view their join and exit timestamps, understand how the call ended, and analyze call quality per agent.Each section represents one agent join event. The system creates a record only when an agent accepts a call invitation (inbound or consult) or joins the interaction, including supervisor join.The system does not create records for routing attempts, ringing duration, rejected invitations, or supervisor listen/whisper sessions. If an agent leaves and rejoins, the system creates multiple rows, one per join instance.Agent Details
Field
Description
Agent Name
Identifies the agent who participated in the interaction
Status
Indicates whether the agent left the interaction
Start Time
Shows when the agent accepted and joined the call
End Time
Shows when the agent exited the call
The time between Start and End reflects the agent’s actual call handling duration.Call Exit Details
Field
Description
Call Exit Reason
High-level termination status (for example, Terminated)
Call Exit Description
Specific termination reason (for example, Agent Hangup or Customer Hangup)