> For the complete documentation index, see [llms.txt](https://docs.sprinthub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinthub.com/en/topics/general/contacts/leads-common-questions/contacts-communication-statistics.md).

# Contacts - Communication Statistics

At SprintHub, you have access to a powerful resource for analyzing and managing communication with your Contacts and Leads. Through communication statistics, it is possible to identify patterns that help optimize your service and sales approaches.

**What can be viewed?**

With this feature, you can track important data about your interactions, such as:

* Best days and times to contact: identify when the Lead is most active and likely to respond;
* Volume of sent and received messages: know whether the initiative for the conversation comes more from your team or the Lead;
* Average response time: compare the response time of the user and the Lead to understand engagement dynamics;
* Most used types of messages: find out whether your communication is mostly text-based, with files, links, images, etc.

This information helps make strategic decisions, such as adjusting send times, personalizing approaches, and even reviewing service processes.

**Why is this important?**

Analyzing these metrics provides greater communication efficiency, improves response rates, and enables more assertive and personalized service. By understanding the behavior of your Leads, your sales or support team can focus efforts on the most effective times and formats.

Check the steps below to carry out this procedure:

1. Access the "Leads" feature:\
   Through “Find Services.” Or just type the name, and the feature appears.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXcircEDMMPvDkloNoMkEC3grZmocWfvMZgrqgmwwuN3rU2Ni3XwcNIAWqNB1VPk_mVj9IT1EvbXLGtzIxx7vC51nKN60VuOQr4J__jQimFVdlRkxH9P_-grt7SrB_WcBLX67hD8iQ?key=ecuvIfryJ3BCLgBWmmaUXg" alt=""><figcaption></figcaption></figure>

{% embed url="<https://youtu.be/n7SGtG8GMoU>" %}

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXeOMKH67VkByeC2ehxKob0C4H7z-fnOwYcH-fFGt1p2YsEK7m5-Fky7Yi2IuEngyFkoG6FAyiaw5JRN3LQT_lrfsJfE9p3C81ycFuiV10POjvyk_UfqLFQ87IEnKWfiZO8CaoGEWQ?key=ecuvIfryJ3BCLgBWmmaUXg" alt=""><figcaption></figcaption></figure>

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXf24Db3AyAhK5vQtFx3CuSkblGIa9URM8-VWWBCSHBo3SNJoS-uZWPrVk9k33CJ1QFSF_yqP-03sdHfAmPJRjYhDAq-coApfVjho5tpqJJQebkAduLcCKWKjjEm6y_CVnNMA5x-Fg?key=ecuvIfryJ3BCLgBWmmaUXg" alt=""><figcaption></figcaption></figure>

**CONCLUSION:**&#x20;

Managing and analyzing communication statistics with your Leads in SprintHub is an effective way to **increase the team's productivity and improve the results of your sales interactions.** By understanding contact behavior — such as peak engagement times, response time, and message type — you can adapt your strategies to achieve more efficient, personalized communication with a higher chance of conversion.


---

# 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://docs.sprinthub.com/en/topics/general/contacts/leads-common-questions/contacts-communication-statistics.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.