Chat Statistics
The Chat Statistics in Surbo Chat Live Agent Platform offers a detailed, interactive summary of all the chats handled by a user or team. Whether you're an Admin, Manager, Team Lead, or Agent, this page provides key insights about each chatβlike when it landed, who picked it, how long it lasted, whether it was transferred or reopened, and more.
This is your go-to module for analyzing individual chat sessions, understanding performance patterns, and optimizing how your support teams interact with customers.
Chat Statistics Reference Table
| Field | Description |
|---|---|
| π Channel Source Name | The platform/channel where the chat originated (e.g., WhatsApp, Messenger) |
| π’ Source Identifier | Business number or ID from which the chat was initiated |
| π οΈ Channel Name | Internal label assigned to the chat to track its journey |
| π± Customer Identifier | Mobile number of the customer |
| π Customer Name | Name of the customer who initiated the conversation |
| π§΅ Chat Category | Indicates if it's a 1-on-1 or a group chat |
| π€ User Name | The name of the person handling the chat (Agent, TL, Manager) |
| π£οΈ Chat Type | Chat format: Text, Audio, or Video |
| π Chat Medium | Origin of the chat: user-initiated, campaign-driven, or via Click-to-WhatsApp Ad |
| π Chat Timestamp | Date & time when the chat landed on the platform |
| β±οΈ Chat Duration | Total time spent between customer and agent |
| π Transfer | Indicates if the chat was transferred to another agent or team |
| β»οΈ Re-Open Chat | If the same chat was reopened within the 24-hour session window |
| π Status | Final status of the chat (see expanded explanations below π) |
| π¬ Replied | Whether the agent sent at least one message during the session |
| π Sentiment | Detected tone of the customer: Positive, Mixed, Negative, etc. |
| π Sentiment Score | A numerical score (1β10) derived from sentiment analysis |
Expanded: Chat Status
Understanding the Status field is crucial to analyzing the outcome of each chat. Here's a detailed breakdown:
These status tags help you pinpoint friction points in your customer support flowβwhether it's delayed responses, missed opportunities, or customer drop-offs.
| Status Type | Explanation |
|---|---|
| β Resolved | The chat was handled and closed successfully by the agent |
| β±οΈ Agent Timeout | The agent didnβt respond within the platformβs timeframe; session auto-ended |
| π« Customer Timeout | The customer became inactive, and the session was closed due to their silence |
| β Chat Declined | The chat (often a reopened one) was declined by the customer |
| π€ Agent No Response | The agent picked the chat but didnβt send any message before closing it |
| β Missed Chat | The chat remained in the queue or awaiting section and auto-closed |
Pro Tips for Smarter Usage
| Pro Tip |
|---|
| β Use channel filters to view chats from WhatsApp, Messenger, Line, or Telegram. |
| π The default view shows the past 1 week; update the date range to 15/30 days or customize manually. |
| π Monitor Re-Open Chats to check if issues are recurring or previously unresolved. |
| π§ Sort by Sentiment and Score to assess customer mood trends across agents. |
| β° Keep an eye on Agent Timeout & Missed Chats for optimizing response strategy. |
| π Export chats with detailed metadata for performance reports or audits. |
| π― Combine Chat Medium with Chat Status to analyze campaign quality. |
Quick Summary List
-
β Real-time access to chat logs and performance stats
-
π Filter by channel, team, or custom date range
-
π¬ Tracks response time, agent activity, and session outcomes
-
π Shows customer sentiment and chat quality
-
π€ Enables data export for reporting and team insights