> For the complete documentation index, see [llms.txt](https://help.blinger.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.blinger.io/documentation/tags/conversations.md).

# Conversations

#### Conversations Analytics displays the following:

**"Conversations" chart** displays the amount of conversations which were solved during a particular period of time selected by clicking "Filter".

**"First response time" chart** displays the time agents need to give the first response to the clients. 

**"Resolution time" chart** displays the time agents need to solve the conversations. The time is counted from the moment a conversation goes into "Unassigned" till the moment it goes into "Closed".

**"Messages" chart** displays the whole amount of messages sent by agents and groups. The messages in closed conversations are counted only.

**"Response time (excluding first response time)" chart** displays the time an agent spends on giving a response in an active conversation. 

**"Conversations by issues" chart** displays the issues with which the clients contact Customer Support Center. Click "Settings" to customise conversations issues.

{% hint style="info" %}

## **NB!**

**Conversation** is a messaging request from a client. It's considered active from the moment it goes into "Unassigned" till the moment it goes into "Closed". Conversation should include at least 1 client's and 1 agent's messages. Notes aren't included. 

**Is it possible to view analytics of working and non-working hours separately?** 

You can customise the parameters in "Group settings" to view analytics of working and non-working hours separately.

\
Click <img src="/files/-LZd2TYPvQoEPELQ7vEy" alt="" data-size="original"> to download csv-file with data analytics.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.blinger.io/documentation/tags/conversations.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.