> 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/sac-360/sac-360o-automations/sac-360o-automation-continuation-of-ongoing-service.md).

# SAC 360º Automation - Continuation of Ongoing Service

### With SprintHub, you ensure that a completed service interaction is automatically resumed as soon as the Lead sends a new message. This way, the status will not remain in "Waiting", allowing the agent to continue the service immediately and efficiently.

1. **Create an Automation:**

* Access your SAC via the **“Find Services”**. Or just type the name, and the function appears.
* Go to the Automations section.
* Start creating: Click on "Create Automation" using the "+" button.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXd8AKHHAu2T_ZNH2VcSuECufT2ZIbZ6WDXv8YY8Tl9rtfaRY6O-anyBIsNLbOFGcAQliyFNsYcIMngoxqH7OPqnaZTtx8pPUa_KtjlC7rGtwwEddisKr1FGgYQvQctp6N1VMfB4?key=us68CYkEMaA_wmUhYy2cM7HO" alt=""><figcaption></figcaption></figure>

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXeqyPVQ1owOeRZYlaoYhTi0GzQ2Lfciuyfp8MTM4OvSTquK5sNSOCeXusqizhJKCng2TTvngjJTi6lJQVnLxsl12qWYrFCuVbWILpS9iN-lTHdDoibuYsVJcoqxwYRBcls6MR2a?key=us68CYkEMaA_wmUhYy2cM7HO" alt=""><figcaption><p>List View</p></figcaption></figure>

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXc1ZAKO4WzdKW7gzgCOSpG0eubLOfMBDGqwegJgJx4zaSmLlsmDVJk4h5nwvvU3j6bjPyLCTsSDrY0-6uwiWJ9Kyx7EcpmUYHSuGxWqVKNarCx6yFcRB0In3gaESL4j-KfluD5qvA?key=us68CYkEMaA_wmUhYy2cM7HO" alt=""><figcaption><p>Kanban Mode</p></figcaption></figure>

2. **Configure and Save:**

* **Enter a Title:** Give the automation a descriptive name.
* **Configure a Trigger:** The trigger used will be “The Lead opens a new support request”.
* **Set up the Condition:** The condition used will be “Does the Lead have an open support request in the SAC?”

> But attention: without using triggers, it will be necessary to enable condition checks. These checks will occur at varying time intervals, which can range from minutes to hours, depending on the number of automations and leads in your instance.

* **Choose the Action:** “Start service”
* Configure the **Action**.
* **Describe** exactly what the action will do.
* **Save the Automation:** After configuring, save the automation.

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

**CONCLUSION**

Using the customer service return feature in SprintHub's SAC is a powerful strategy to optimize the customer experience and team efficiency. It allows interactions to be resumed smoothly and continuously, reducing waiting time and ensuring that no important contact is lost. With this, your team can offer faster, more personalized, and more satisfying service, strengthening customer relationships and promoting loyalty.


---

# 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/sac-360/sac-360o-automations/sac-360o-automation-continuation-of-ongoing-service.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.