> 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/analyze/custom-reports-and-dashboards/reports-common-questions/reports-support/reports-sac-360.md).

# Reports - SAC 360

<figure><img src="/files/9df61b8e308dd390c05b4bcff50ca933e00c137d" alt=""><figcaption></figcaption></figure>

Custom reports are essential tools for teams that want to monitor specific metrics and make data-driven decisions. In SprintHub, you can create reports that exactly meet your operation's needs by combining advanced filters, graphical visualizations, and custom conditions.

#### **Steps to Create Custom Reports in SprintHub**

**1. Access the Reports module and click on new.**

<figure><img src="/files/04a4a1a402aac4b971feeb1c39d8323e3f61aa64" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/b637dd1b6cad58f7450a81af12ca0a513c930dfd" alt=""><figcaption></figcaption></figure>

**1. Choose the Report Type**

The first step is to define the type of report you want to create. In the example shown, we chose the **SAC 360**, focusing on created tickets and sent messages. This type is ideal for monitoring interactions and measuring customer service efficiency.

<figure><img src="/files/f108d1aacd127d296c60f3725c3cab967c9d3e71" alt=""><figcaption></figcaption></figure>

**2. Set Specific Conditions**

Add conditions to refine the data you want to analyze. In the example, we configured a filter to include only tickets created this month. This functionality allows you to focus on periods or metrics relevant to your analysis.

<figure><img src="/files/ff3038c5afde24928434c32592b7f0c0a23b0ddb" alt=""><figcaption></figcaption></figure>

**3. Select the Graphical Visualization**

Data can be displayed in different chart formats:

* **Bar:** Comparison between categories or owners.
* **Line:** Temporal evolution of metrics.
* **Table:** Numerical breakdown.
* **Pie:** Best graphical overview.

<figure><img src="/files/e9ed2ad33dbbda5e2ab2cff8e50cedafb7b1989a" alt=""><figcaption></figcaption></figure>

In the example, we used a stacked bar chart by owners to show the distribution of tickets in the month of November.

**4. Interpret the Data**

The generated visualization offers a clear analysis:

* **System (32 tickets):** Most of the tickets were processed automatically.
* **No owner (8 tickets):** Cases without direct allocation.
* **User (8 tickets):** Manual tickets handled by a specific employee.

This can be changed if necessary for better chart visualization.

<figure><img src="/files/afccff10b08dbe3a20dbaf99b0dd889893742d91" alt=""><figcaption></figcaption></figure>

#### **Conclusion**

Custom reports in SprintHub are a powerful tool to monitor and optimize processes. With precise filters and clear visualizations, your team can make informed decisions, identify areas for improvement, and achieve exceptional results. Explore the possibilities and turn data into strategies!


---

# 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/analyze/custom-reports-and-dashboards/reports-common-questions/reports-support/reports-sac-360.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.