> 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/common-questions/automation-reports/automation-reports-sac-360o-and-crm-in-sprinthub.md).

# Automation Reports - SAC 360º and CRM in SprintHub

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2FdiavJenClqAfY3tkgTWj%2Fundraw_Inspection_re_tbt7.png?alt=media&amp;token=26309349-d7fa-442f-a3f8-06e67e8a477b" alt=""><figcaption></figcaption></figure>

SprintHub offers a robust system for managing customer service automations, integrated with the CRM to provide a complete view of the customer lifecycle. One of the features is the ability to generate reports on these automations, allowing managers to monitor and optimize service performance.

### Running and Completed Automation View

By clicking the name of a specific automation within the panel of **Automation Statistics**, you will be redirected to a page where you can view all the customer service interactions that participate or participated in that automation. The view is divided into two main sections:

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2F4gZ3GwPfl1enMNGXHRXQ%2Fimage.png?alt=media&amp;token=0c34989e-ae79-4a02-b8eb-509e09f9a2cb" alt=""><figcaption></figcaption></figure>

1. **Interactions in Progress:**
   * The top part of the page displays a list of the interactions that are still running the automation.
   * You will see detailed information such as the interaction number, the lead name, the contact type (such as WhatsApp), the associated account, and the current status of the interaction.
2. **Completed Interactions:**
   * Just like the interactions in progress, those that have already been completed are also listed, making it easier to analyze performance and check leads that completed the entire automation process.

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2F6zJCteWUu9YsMuzBV2jp%2F1.png?alt=media&amp;token=6ae56b98-e448-4e55-96b5-72dd7e909a49" alt=""><figcaption></figcaption></figure>

#### Error Logs

Below the list of interactions, there is a section dedicated to the **Error Logs**logs. These logs are crucial for understanding what went wrong at a certain stage of the automation. The available information includes:

* **Lead:** The specific contact that encountered the problem.
* **Interaction:** The interaction number associated with the error.
* **Action:** The specific step or action within the automation where the error occurred.
* **Message:** A description of the error that was recorded.

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2FUMvqRgm5Us725WtY3xtX%2Fimage.png?alt=media&amp;token=527430a3-70da-45dc-a21b-b3b0723901b3" alt=""><figcaption></figcaption></figure>


---

# 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/common-questions/automation-reports/automation-reports-sac-360o-and-crm-in-sprinthub.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.