Reporting options available in LiveChat

LiveChat offers a wide range of chat and tickets reports. Use them to fine-tune your implementation. The reports will help you spot areas which can be optimized and more efficient.

These reports include:

• Last 7 days report
• Chat reports (Total chats, Chat sources, Chat ratings, Chat Duration, Availability)
• First and average response time reports
• Queue reports (Queued visitors, Queue waiting times, Queue abandonment)
• Goals report
• Staffing prediction report
• Incoming tickets report (New tickets, Ticket sources)
• Ticket response and resolution time reports
• Tickets satisfaction report
• Chat surveys report

There are also a couple of report-related features:

• Advanced reporting functions
• Exporting report data
• Rest API documentation

Last 7 days report

This report gives you an overview of your LiveChat activities from the last 7 days. You can use it as a reference point when trying to gauge the effectiveness of your support. Learn more…

Chats reports

Detailed information about your chats. These reports will tell you how many chat you get, where those chats come from, how long they take, how happy your customers are with the service and when is your LiveChat available. Learn more…

First and average response time reports

Information about the speed with witch your agents respond to customers. You can track how long it takes the first reply in a chat and how long in general it takes to get a reply. Learn more…

Queue reports

These three reports will tell you how long your average queue is and how many visitors enter and leave the queue. Useful when trying to find out if you need to expand your customer service. Learn more…

Goals report

This report will tell you how much profit you got from your chats. You can set the goals to monitor how much sales you got or check if chat contributed to any other desirable effect. Learn more…

Staffing prediction report

Enterprise and Enterprise Plus users can utilize this report to see how many agents will be needed to answer all chats. The report is based on historical data about the number of chats previously received. Learn more…

Incoming tickets reports

These reports will tell you how many and from where you get tickets. Learn more…

Ticket response and resolution times reports

These two reports tell you how long your customer have to wait for a first response and the resolution of a ticket. Learn more…

Ticket satisfaction report

Report that shows you how pleased are your customers with the resolution of their tickets. Learn more…

Chat surveys report

If you have any chat surveys set up, this report will tell you what kind of answers you get in your pre-chat and post chat surveys. Learn more…

Advanced reporting functions

All reports come with a set of additional features that will help you get precise information on your customers service. The results can be filtered for a particular case type or displayed for a specific time period only. Learn more…

Exporting report data

There are two ways you can use to get detailed reporting data from LiveChat.

You can find the Save as CSV under most reports. This option allows you to save the data to a CSV file which you can later open in your Excel.

Another way of extracting data from LiveChat is the Export option available for Enterprise and Enterprise Plus users. Using the Export feature, you can export or schedule a custom report. You can choose which area (Chats, Surveys, Queue abandonment, Goals and Tickets) and time-frame it should cover. You can also choose a file format: CSV, TSV or TSV (Excel).

The report will be sent to the specified email after you press the Email report button. The report can be set to recur every day, week or month.

Below, you can find a list of all the information you can get through exportable reports.

The data from Chats report (records for individual chats):

• Conference ID
• Chat creation date (and timezone)
• Chat start date (and timezone)
• Chat start URL (on what page the chat started)
• Referrer
• Chat duration (in seconds)
• Queue duration (in seconds)
• Visitor’s LiveChat ID
• Visitor’s name
• Visitor’s IP
• Last operator’s ID (the agent that chatted with the visitor previously)
• Skill
• Rate
• Agent’s name
• Agent’s ID
• Agent’s timezone
• Pre-chat survey information
• Post-chat survey information
• Greeting URL (on what page the greeting was displayed)
• Greeting action (the condition that triggered the greeting)
• Goal name
• Goal credit
• Goal date
• Tags
• Custom variable name
• Custom variable value
• Integration variable name
• Integration variable value
• First response time (in seconds)
• Average response time (in seconds)

Information from the Queue abandonment report:

• Conference ID
• Queue start time (and timezone)
• Queue duration (in seconds)
• Queue start URL
• Skill
• Visitor’s LiveChat ID
• Visitor’s name
• Visitor’s IP
• Pre-chat survey information
• Custom variable name
• Custom variable value
• Integration variable name
• Integration variable value

Information you can get by exporting the Goals report:

• Goal ID
• Goal name
• Conference ID
• Chat start date (and timezone)
• Goal achievement date (and timezone)
• Agent’s ID
• Skill
• URL (where was the goal triggered)
• Order ID (additional information that can be added to the goal via API)
• Order description (additional information that can be added to the goal via API)
• Order price (additional information that can be added to the goal via API)
• Order currency (additional information that can be added to the goal via API)
• Custom variable name
• Custom variable value

The Tickets report will give you the following information when extracted:

• Ticket ID
• Ticket creation date (and timezone)
• Requester name
• Requester email
• Skill
• Rate
• Assignee’s name
• Assignee’s ID
• Status
• Subject
• Source
• Source URL
• First response date (and timezone)
• Used tags

Rest API documentation

You can create custom reports by pulling LiveChat data using our Rest API. The API is fully documented, which will make the task easy. Simply create a request and save the results to a file that can be later on interpreted using Excel.

If you are not familiar with using APIs, we have an introductory article ready.